Linux-omap-open-source Digest, Vol 23, Issue 61
Hi All
I am using montavista linux on omap 5912 ,i am using memcpy for data transfer.i have one question if during data transfer through memcpy external interrupt or any other higher priority DMA channel interrupt comes ,How driver can manage data corruption ,My device connected in memcpy processing is configured with 16 bit bus and other device is 32 bit.
thanks
Amit
[email protected] wrote:
Send Linux-omap-open-source mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
or, via email, send a message with subject or body 'help' to [email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-omap-open-source digest..."
Today's Topics:
1. Re: [PATCH] Fix USB host on 1510/5910? (Jonathan McDowell)
2. palmte lcd warnings (Komal Shah)
3. Re: [PATCH] fix MMC response types (Carlos Aguiar)
4. Re: palmte lcd warnings (andrzej zaborowski)
5. About dct4x4 transform on 55x dsp,who can provide a good way? (=?gb2312?B?zfWxprHy?=)
6. Stack pointer register accesing problem with monta- vista linux 2.4 on OMAP 730 (chandrashekhar singh)
----------------------------------------------------------------------
Message: 1
Date: Tue, 28 Mar 2006 20:05:19 +0100
From: Jonathan McDowell
Subject: Re: [PATCH] Fix USB host on 1510/5910?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Quoted 7 lines · Jonathan McDowell
I'm not quite sure if this is necessary or not. I've found I need it to get USB working correctly on the Amstrad E3, which is an OMAP5910. From my reading of
ohci-omap.cusb_dc_ckis requested for the 1510 as well, and if it can't be obtained an error is returned.Does anyone have USB working correctly on a 1510/5910 with latest git without something like the below?
Scratch that for the moment. I'm now getting:
ohci ohci: Unlink after no-IRQ? Controller is probably using the wrong IRQ.
even with this patch, whereas it worked fine for 2.6.15-omap1.
I'd still like to know if anyone's having success with a 1510/5910 and latest git though, as I've had someone else tell me they were seeing similar problems on a platform that wasn't the E3 (unfortunately it was on IRC and I don't have their details. :( ).
J.
Signature · 50 lines
[ noodles is almost a national pastime in japan ] [ http://www.blackcatnetworks.co.uk/ - IPv6 enabled ADSL/dialup/colo ] ------------------------------ Message: 2 Date: Tue, 28 Mar 2006 12:29:06 -0800 (PST) From: Komal Shah Subject: palmte lcd warnings To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=iso-8859-1 Build warning from lcd panel source - latest omap-git tree. ... -c -o drivers/video/omap/lcd_palmte.o drivers/video/omap/lcd_palmte.c drivers/video/omap/lcd_palmte.c:86: warning: initialization from incompatible pointer type drivers/video/omap/lcd_palmte.c:87: warning: initialization from incompatible pointer type drivers/video/omap/lcd_palmte.c:88: warning: initialization from incompatible pointer type drivers/video/omap/lcd_palmte.c:89: warning: initialization from incompatible pointer type drivers/video/omap/lcd_palmte.c:90: warning: initialization from incompatible pointer type .... ---Komal Shah http://komalshah.blogspot.com/ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------ Message: 3 Date: Tue, 28 Mar 2006 16:59:18 -0400 From: Carlos Aguiar Subject: Re: [PATCH] fix MMC response types To: [email protected] Cc: omap-linux Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8"
Quoted 74 lines · ext andrzej zaborowski
Quoted 33 lines · Carlos Aguiar
Quoted 17 lines · ext andrzej zaborowski
Previously the MMC/SD protocol layer didn't provide command and response types to
mmc_omap_start_command(). In 2.6.16 it does and the hack that tries to find the correct command/response types based on flags is no longer needed.
This matters particularly for response types because for command types this hack worked fine, while it failed to give correct response type for some SD commands such as CMD3 (in most cases this caused no big problems because the size of the response matched). Regards,
Andrzej
--
balrog 2oo6Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258Quoted 10 lines
------------------------------------------------------------------------
_______________________________________________
Linux-omap-open-source mailing list
[email protected]
http://linux.omap.com/mailman/listinfo/linux-omap-open-sourceHi Andrzej and folks,
Quoted 10 lines
Attached to this mail follow my propose of fixing MMC responde types in
mmc_omap_start_command().This is based on the patches of the thread '[RFC] mmc: add OMAP driver' that I sent to LKML mailing-list in order to have integrated the MMC OMAP driver on the mainline kernel.
Comments and suggestions are welcome.
It looks fine except you forgot about the response type 6. With the current version of
mmc_omap_start_command()the hack assumes response type 1 in place of 6 which merely causes the MMC/SD host controller to misinterpret the status flags in the response from the card, but the size of the response matches. However with your patch it would assume no response at all which would most probably cause breakage.Quoted 4 lines
BR,
Carlos.
Quoted 14 lines
--
Carlos Eduardo
Software Engineer
Nokia Institute of Technology - INdT
Embedded Linux Laboratory - 10LE
Phone: +55 92 2126-1079
Mobile: +55 92 8127-1797
E-mail: [email protected]
Quoted 9 lines
Regards,
Andrew
--
balrog 2oo6Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
Hi Andrew and folks,
The response type 6 was included. Thanks for your observation.
BR,
Carlos.
Signature · 27 lines
Carlos Eduardo Software Engineer Nokia Institute of Technology - INdT Embedded Linux Laboratory - 10LE Phone: +55 92 2126-1079 Mobile: +55 92 8127-1797 E-mail: [email protected] -------------- next part -------------- A non-text attachment was scrubbed... Name: mmc_omap_rsp.patch Type: text/x-patch Size: 2159 bytes Desc: not available Url : http://linux.omap.com/pipermail/linux-omap-open-source/attachments/20060328/27111ece/mmc_omap_rsp-0001.bin ------------------------------ Message: 4 Date: Wed, 29 Mar 2006 01:16:09 +0200 From: "andrzej zaborowski" Subject: Re: palmte lcd warnings To: "Komal Shah" Cc: [email protected] Message-ID: Content-Type: text/plain; charset="utf-8"
Quoted 19 lines · Komal Shah
Build warning from lcd panel source - latest omap-git tree.
...
-c -odrivers/video/omap/lcd_palmte.odrivers/video/omap/lcd_palmte.cdrivers/video/omap/lcd_palmte.c:86: warning: initialization from incompatible pointer typedrivers/video/omap/lcd_palmte.c:87: warning: initialization from incompatible pointer typedrivers/video/omap/lcd_palmte.c:88: warning: initialization from incompatible pointer typedrivers/video/omap/lcd_palmte.c:89: warning: initialization from incompatible pointer typedrivers/video/omap/lcd_palmte.c:90: warning: initialization from incompatible pointer type
....---Komal Shah
http://komalshah.blogspot.com/
Quoted 9 lines
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
_______________________________________________
Linux-omap-open-source mailing list [email protected]
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
Please find the fix attached. Tested to build and to work. Regards,
--
balrog 2oo6
Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lcd_palmte-warnings.patch
Type: application/octet-stream
Size: 1196 bytes
Desc: not available
Url : http://linux.omap.com/pipermail/linux-omap-open-source/attachments/20060329/5394a5bf/lcd_palmte-warnings-0001.obj
------------------------------
Message: 5
Date: Wed, 29 Mar 2006 10:19:49 +0800
From: =?gb2312?B?zfWxprHy?=
Subject: About dct4x4 transform on 55x dsp,who can provide a good way? To:
Message-ID: <001301c652d7$4235b4a0$9d0aa8c0@yfwangbaobin>
Content-Type: text/plain; charset="gb2312"
hi:
i want to get dct4x4 transform in 55x dsp. And I get some useful information from the document " TMS320C55x Hardware Extensions for Image/Video Applications Programmer¡¯s Reference".------you can get it from internet easily. the document explain how to get dct8x8 transform result step by step.i have tested it !right.
In page 2-5 , it tell me some information about how to get dct4x4 tranforme result.but it is
so obscurity that i can't understand how to use it!!
who can give me hands! thanks.
b.w.b
------------------------------
Message: 6
Date: Wed, 29 Mar 2006 12:04:02 +0900
From: "chandrashekhar singh"
Subject: Stack pointer register accesing problem with monta- vista linux 2.4 on OMAP 730
To:
Message-ID: <001e01c652dd$a25cab30$5811a80a@cpsingh>
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Dear all,
I'm facing a very strange problem with Monta-Vista linux 2.4 which is running on OMAP 730.
I have some assembler code which uses stack pointer register to load or store the intermediate value of variables. The source code work well on linux 2.6 running on OMAP 2420 but when I execute it on Monta-Vista linux 2.4 running on OMAP 730 it gives 'segmentation fault'.
I've noticed that problem lies in stack pointer register as when i tries to access stack pointer register directaly it gives segmentation fault. Following snippet does not work on Monta-vista linux 2.4 running on OMAP 730 but work well on Linux 2.6 running on OMAP2420.
.set FRAMEPROC_ASM_STACK, 48
FRAMEPROC_DUMMY:
stmdb sp!, {r4-r11, lr}
sub sp, sp, #FRAMEPROC_ASM_STACK
mov r5, #5
str r5, [sp, #12]
add sp, sp, #FRAMEPROC_ASM_STACK
ldmia sp!, {r4-r11, pc}
The have modified the assembler code as follows and tested it on both target then it works well on both target. I'm not getting why ?
.set FRAMEPROC_ASM_STACK, 48
FRAMEPROC_DUMMY:
stmdb sp!, {r4-r11, lr}
sub sp, sp, #FRAMEPROC_ASM_STACK
mov r14, sp
mov r5, #5
str r5, [r14,#12]
@str r5, [sp, #12]
add sp, sp, #FRAMEPROC_ASM_STACK
ldmia sp!, {r4-r11, pc}
Though I've got temporary solution but my assembler source code is quite big and it is very difficult to rewrite it as i dont have free register in actual source to map the stack pointer register to another register.
Can any body put some light as why it happening on Monta-vista linux ???
Thanks in advance
chandrasheskhar
[email protected]
----- Original Message -----
From:
To:
Sent: Wednesday, March 29, 2006 3:00 AM
Subject: Linux-omap-open-source Digest, Vol 23, Issue 60
Quoted 386 lines
Send Linux-omap-open-source mailing list submissions to [email protected]
To subscribe or unsubscribe via the World Wide Web, visi
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
or, via email, send a message with subject or body 'help' to [email protected]You can reach the person managing the list at
[email protected]When replying, please edit your Subject line so it is more specific than "Re: Contents of Linux-omap-open-source digest..."
Today's Topics:
1. About to tag 2.6.16-omap1 & current patch status (Tony Lindgren)
2. RE: U-boot 1.1.4 compilation problem (Giron, Jeremy)
3. RE: DSP Gateway for OMAP5912 ([email protected])
4. [PATCH] Fix USB host on 1510/5910? (Jonathan McDowell)----------------------------------------------------------------------
Message: 1
Date: Tue, 28 Mar 2006 07:35:02 -0800
From: Tony Lindgren
Subject: About to tag 2.6.16-omap1 & current patch status
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-asciiHi all,
We're about to ready to tag 2.6.16-omap1. Let's do some testing and try to get few issues fixed. Currently there's at least the MMC issue with I2C powered sockets that we should fix before tagging 2.6.16-omap1.
Please report any issues that should be fixed for 2.6.16-omap1 to this thread.
Also following is a summary of the currently applied and pending patches.
Applied patches
Komal Shah [PATCH] OMAP: KEYPAD: sem2mutex conversion
Komal Shah [PATCH] OMAP: Menelaus: sem2mutex conversion Komal Shah [PATCH] OMAP: FB: sem2mutex conversion
Komal Shah [PATCH] OMAP: retu-rtc: sem2mutex conversion Komal Shah [PATCH] retu-user: sem2mutex conversion
Komal Shah [PATCH] OMAP: tahvo usb: sem2mutex conversion Komal Shah [PATCH] OMAP:tahvo_user: sem2mutex conversion Komal Shah [PATCH] OMAP: OSS: sem2mutex conversion
Komal Shah [PATCH] OMAP2: Fix H4 keypad
Komal Shah [PATCH] OMAP1: camera core : Use platform driver structure Komal Shah [PATCH] Fix OV9640 sensor and add h4 sensor power functions Jonathan McDowell [PATCH] Add support for Amstrad Delta (E3) VideophonePending patches for post 2.6.16-omap1
Komal Shah [PATCH] OMAP2 MCSPI Use resources
Hiroshi DOYU [patch 1/5] MMC BUGFIX TRIVIAL STUFFS
Richard Woodruff [PATCH] : Fix annoying 'too much work for irq72' serial Richard Woodruff [PATCH] OMAP2: timer+irq fix up
David Cohen [PATCH] omap24xxcamera
Carlos Aguiar [PATCH] fix MMC response types
Komal Shah [PATCH] OMAP2: ov9640 updates for H4
Komal Shah [PATCH] omap24xx camera cleanup
Komal Shah [PATCH] CBUS: various cleanups
Komal Shah [PATCH] OMAP: MMC: Moveset_powerto platform data Komal Shah [PATCH] OMAP: FB: Use blocking notifier apisRegards,
Tony
------------------------------
Message: 2
Date: Tue, 28 Mar 2006 08:47:31 -0700
From: "Giron, Jeremy"
Subject: RE: U-boot 1.1.4 compilation problem
To: "Hiroki Kaminaga"
Cc: [email protected]
Message-ID:Content-Type: text/plain; charset=us-ascii
Hiroki,
Yes, you are correct. I'm not sure how it worked without it.It should mimic
omap1510imm.h:#define
PHYS_FLASH_10x00000000/* Flash Bank #1 */#define
CFG_FLASH_BASEPHYS_FLASH_1
<...>
#defineCFG_MAX_FLASH_BANKS2 /* max number of memory banks */ #definePHYS_FLASH_SIZE0x01000000/* 16MB */
#definePHYS_FLASH_SECT_SIZE(128*1024) /* Size of a sector (128kB) */
#defineCFG_MAX_FLASH_SECT(128) /* max number of sectors on one chip */
#defineCFG_ENV_ADDR(CFG_FLASH_BASE+PHYS_FLASH_SECT_SIZE) #defineCFG_MONITOR_BASECFG_FLASH_BASE/* Monitor at beginning of flash */
#defineCFG_MONITOR_LENPHYS_FLASH_SECT_SIZE/* Reserve 1 sector */
#defineCFG_FLASH_BANKS_LIST{CFG_FLASH_BASE,CFG_FLASH_BASE+PHYS_FLASH_SIZE}Result:
OMAP5912 OSK # flinfoBank # 1: CFI conformant FLASH (16 x 16) Size: 16 MB in 128 Sectors
Erase timeout 16384 ms, write timeout 2 ms, buffer write timeout 2048 ms, buffe
r size 32Sector Start Addresses:
00000000 (RO) 00020000 (RO) 00040000 00060000 00080000
000A0000 000C0000 000E0000 00100000 00120000
<...>
00F00000 00F20000 00F40000 00F60000 00F8000000FA0000 00FC0000 00FE0000
Bank # 2: CFI conformant FLASH (16 x 16) Size: 16 MB in 128 Sectors
Erase timeout 16384 ms, write timeout 2 ms, buffer write timeout 2048 ms, buffe
r size 32Sector Start Addresses:
01000000 01020000 01040000 01060000 01080000
010A0000 010C0000 010E0000 01100000 01120000
<...>
01F00000 01F20000 01F40000 01F60000 01F8000001FA0000 01FC0000 01FE0000
Best regards,
Jeremy-----Original Message-----
From: Hiroki Kaminaga [mailto:[email protected]]
Sent: Sunday, March 26, 2006 11:48 PM
To: Giron, Jeremy
Cc: [email protected]; [email protected]; [email protected]
Subject: Re: U-boot 1.1.4 compilation problemHi,
sorry for late reply,
Quoted 3 lines
It is also necessary to change
CFG_MAX_FLASH_BANKSto 2 (from 1). Otherwise the CFI driver will only detect a single 16MB bank, rather than the full 16MBx2 = 32MB.Umm, that's right. Also if you change to 2, you also need to set
CFG_FLASH_BANKS_LISTtoo?Best Regards,
(Hiroki Kaminaga)
t
--------------------------------
Message: 3
Date: Wed, 29 Mar 2006 01:32:19 +0900
From:
Subject: RE: DSP Gateway for OMAP5912
To: ,Message-ID:
<[email protected]>
Content-Type: text/plain; charset="US-ASCII"Hi,
I'm using Linux 2.6.12 + OMAP patch from www.muru.com with DSP Gateway 3.3 on OSK5912. But I have not seen such problem so far... Did you try the other sample program (e.g.
task_test?, hellotimer, etc.)?BR,
Kiyotaka-----Original Message-----
From:
linux-omap-open-source-bounces+kiyotaka.takahashi=nokia.com@linux.omap.c om [mailto:linux-omap-open-source-bounces+kiyotaka.takahashi=nokia.com@linu x.omap.com] On Behalf Of ext naga rajan
Sent: Tuesday, March 28, 2006 7:37 PM
To: [email protected]
Subject: DSP Gateway for OMAP5912Hi all,
I like to proceed with DSP gateway for DSP applications development. I like to know the exact kernel, DSP gateway version and the
exact patches for kernel 2.6 series and for DSP gateway.I tried with kernel
2.6.12 and DSP gateway 3.3. While executing the application, I m getting the
following error# dspctl start demo_console.outloading demo_console.out...
dspgw_task: adr =0x00c440, size= 36
dspgw_version: adr =0x000000, size= 8 ... ignored.Unable to handle kernel paging request at virtual address e0010000pgd =
c1d30000[
e0010000] *pgd=00000000Internal error: Oops: 805 [#1] Modules linked in: CPU: 0PC is at .cfu_0fupi+0x10/0x50
LR is at
intmem_write+0x8c/0xdcpc : [] lr : [] Not taintedsp :
c1cf7ed8ip : 00000000 fp :c1cf7f1cr10:
e0010000r9 :c024c6dcr8 :c1cf7f74r7 : 00000008 r6 : 00000008 r5 : 00000008 r4 :
be913d5cr3 : 00000000 r2 : 00000004 r1 :
be913d60r0 :e0010000Flags: nzCv IRQs on FIQs on Mode
SVC_32Segment userControl: 5317F Table: 11D30000 DAC: 00000015
Process dspctl (pid: 723, stack limit =
0xc1cf6194)Stack: (0xc1cf7ed8 to 0xc1cf8000)7ec0:
e0010000
000000087ee0:
be913d5c00000008 00000008 00000008c003ca0400028000 00000000c1cf7f747f00:
be913d5c00000008e0010000c02ea760c1cf7f48c1cf7f20c003cbb0c003c9887f20: 00000008 00000000
be913d5cc02ea760c1cf600000000000c1cf7f74c1cf7f707f40:
c1cf7f4cc00851fcc003cb40c02ea784fffffff7c02ea760c1cf7f74000100007f60:
4014bafcc1cf7fa4c1cf7f74c0085338c008514800010000 00000000 000000007f80:
be913eb44001df400000c57000000004c0022e04c1cf600000000000c1cf7fa87fa0:
c0022c80c00852f8be913eb4c0029c1800000005be913d5c00000008be913d5c7fc0:
be913eb44001df400000c570000000034014e1d0000089f04014bafcbe913db87fe0: 00000000
be913d5400003f64400ec83060000010 00000005 00000000 00000000Backtrace:[] (
intmem_write+0x0/0xdc) from []
(dsp_mem_write+0x80/0xb4)[] (
dsp_mem_write+0x0/0xb4) from []
(vfs_write+0xc4/0x13c)[] (
vfs_write+0x0/0x13c) from []
(sys_write+0x50/0x74)[] (
sys_write+0x0/0x74) from []
(ret_fast_syscall+0x0/0x2c)r9 = C1CF6000 r8 = C0022E04 r7 = 00000004 r6 = 0000C570
r5 = 4001DF40 r4 = BE913EB4
Code: e2522004 4282c004 4a000026 e4b13004 (e4803004)Segmentation fault
I tried with patches mentioned in the
source forge.net. If you have succeeded this problem,I like to know the details such as kernel.DSP gateway and patches you used. Please help me in
this regard.Thanks in advance,
B.Nagarajan,
SANDS.
_______________________________________________
Linux-omap-open-source mailing list
[email protected]
http://linux.omap.com/mailman/listinfo/linux-omap-open-source------------------------------
Message: 4
Date: Tue, 28 Mar 2006 17:44:03 +0100
From: Jonathan McDowell
Subject: [PATCH] Fix USB host on 1510/5910?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-asciiI'm not quite sure if this is necessary or not. I've found I need it to get USB working correctly on the Amstrad E3, which is an OMAP5910. From my reading of
ohci-omap.cusb_dc_ckis requested for the 1510 as well, and if it can't be obtained an error is returned.Does anyone have USB working correctly on a 1510/5910 with latest git without something like the below?
Signed-off-by Jonathan McDowell-----
arch/arm/mach-omap1/clock.h +1
-2@@ -633,7 +633,7 @@ static struct clk usb_dc_ck = { .name = "usb_dc_ck",/* Direct from ULPD, no parent */ .rate = 48000000, - .flags = CLOCK_IN_OMAP16XX | RATE_FIXED, + .flags = CLOCK_IN_OMAP1510 | CLOCK_IN_OMAP16XX | RATE_FIXED, .enable_reg = (void __iomem *)SOFT_REQ_REG, .enable_bit = 4, .enable = &omap1_clk_enable_generic, -----
Quoted 16 lines
J.
Signature · 10 lines
------------------------------ _______________________________________________ Linux-omap-open-source mailing list [email protected] http://linux.omap.com/mailman/listinfo/linux-omap-open-source End of Linux-omap-open-source Digest, Vol 23, Issue 60 ******************************************************
------------------------------
_______________________________________________
Linux-omap-open-source mailing list
[email protected]
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
End of Linux-omap-open-source Digest, Vol 23, Issue 61
******************************************************
---------------------------------
Jiyo cricket on Yahoo! India cricket
Yahoo! Messenger Mobile Stay in touch with your buddies all the time.