Send Davinci-linux-open-source mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-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 Davinci-linux-open-source digest..."
Today's Topics:
1. Re: How to know the mmc or memory stick card insert status
(John Wu)
2. RE: ti davinci 644x sdio stack port for dm355
(Subbrathnam, Swaminathan)
3. DM355 - Using GPIO pin for interrupt: Strange problem (Viet Hoang)
4. Re: Error in formating SDHC 8G card in DM6446?? (Goung)
----------------------------------------------------------------------
Message: 1
Date: Fri, 23 May 2008 09:41:12 +0800
From: John Wu <[EMAIL PROTECTED]>
Subject: Re: How to know the mmc or memory stick card insert status
To: Albert Burbea <[EMAIL PROTECTED]>
Cc: "[email protected]"
<[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain
Hi,Albert
what detail do you want?
On Thu, 2008-05-22 at 17:07 +0200, Albert Burbea wrote:
hi guys
can you please detail?
Albert
On Thu, May 22, 2008 at 9:28 AM, John Wu <[EMAIL PROTECTED]> wrote:
Hi Kumar,
Thanks.
On Wed, 2008-05-21 at 17:46 +0530, Kumar, Purushotam wrote:
> Hi
>
> There is no register in the case of DM6446 for detecting
whether card is mmc or memory stick.
> MMC card insertion/removal has been detected currently in
the driver using timer functionality.
> CMD13 has been sent periodically for checking status of card
from controller driver. This command will fail if memory stick
has been inserted and there are similarly different set
commands are present for detecting memory stick.
>
> Regards,
> Purushotam
>
>
> > -----Original Message-----
> > From:
[EMAIL PROTECTED]
[mailto:davinci-linux-open-source-
> > [EMAIL PROTECTED] On Behalf Of John Wu
> > Sent: Wednesday, May 21, 2008 9:26 AM
> > To: [email protected]
> > Subject: How to know the mmc or memory stick card insert
status
> >
> > Hi all,
> > I work on dm6446. I must know whether the card is inserted
and know the
> > card is mmc or memory stick. There are some registers have
such
> > information in dm320, but seems there are no these
registers in dm6446.
> >
> > Regards!
> >
> > _______________________________________________
> > Davinci-linux-open-source mailing list
> > [email protected]
> >
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
--
Albert Burbea
Harishonim 8
Ramat Gan 52502, Israel
Tel/Fax + 972-3-7526016
Mobile: +972-52-3541842
------------------------------
Message: 2
Date: Fri, 23 May 2008 07:16:27 +0530
From: "Subbrathnam, Swaminathan" <[EMAIL PROTECTED]>
Subject: RE: ti davinci 644x sdio stack port for dm355
To: nash b <[EMAIL PROTECTED]>,
"[email protected]"
<[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
Nash,
Pl. verify whether the clk for the MMC/SD module is turned on. Normally
the clk related API are initialized in the "arch/arm/mach-davinci/clk.c"
file. Make sure that you have a referrence for the MMC/SD module in that
file.
It seems from the crash during the MMC/SD driver init the clk_get API is
not getting the required clk pointer for the MMC/SD module and we are
trying to clk_use () a NULL pointer causing the crash that you have
attached.
Pl. add the MMC/SD clk referrence in the clk.c.
regards
swami
________________________________
From: [EMAIL PROTECTED]
[EMAIL PROTECTED] On Behalf Of nash
b [EMAIL PROTECTED]
Sent: Friday, May 23, 2008 5:01 AM
To: [email protected]
Subject: ti davinci 644x sdio stack port for dm355
I tried to port the davinci 644x sdio stack to dm355 in an effort to
evaluate the performance compared to the mmc/sd support inbuilt in the
demo kernel provided by ti with dm355. I built the sdio drivers as modules
as suggested in the documentation. The kernel and the modules did build
without any errors, although i get errors trying to insert the
sdio_davinci_hcd.ko module.
I did disable the inbuilt mmc support before building the kernel. Is there
any other things you can suggest that i should be looking at for the port?
Thanks in advance...
[EMAIL PROTECTED]:/opt/sdio# insmod sdio_lib.ko
SDIO Library load
[EMAIL PROTECTED]:/opt/sdio# insmod sdio_busdriver.ko
[EMAIL PROTECTED]:/opt/sdio#
[EMAIL PROTECTED]:/opt/sdio# insmod sdio_davinci_hcd.ko
Unable to handle kernel NULL pointer dereference at virtual address
00000012
pgd = c58c0000
[00000012] *pgd=85888031, *pte=00000000, *ppte=00000000
Internal error: Oops: 17 [#1]
Modules linked in: sdio_davinci_hcd sdio_busdriver sdio_lib
CPU: 0
PC is at __clk_use+0xc/0x20
LR is at clk_use+0x34/0x60
pc : [<c0044718>] lr : [<c0044840>] Not tainted
sp : c591bdc8 ip : c591bdd8 fp : c591bdd4
r10: 00000000 r9 : 0000001a r8 : 00000000
r7 : 00000000 r6 : 0000001b r5 : a0000013 r4 : c591a000
r3 : 00000001 r2 : 0000004d r1 : c591a000 r0 : fffffffe
Flags: NzCv IRQs off FIQs on Mode SVC_32 Segment user
Control: 5317F Table: 858C0000 DAC: 00000015
Process insmod (pid: 1112, stack limit = 0xc591a1a0)
Stack: (0xc591bdc8 to 0xc591c000)
bdc0: c591bdf4 c591bdd8 c0044840 c004471c 0000001b
fffffffe
bde0: c5915c00 0000001b c591be44 c591bdf8 bf01270c c004481c c0fc9e60
bf012fdf
be00: c0051ca0 c0fc9e60 c5915c00 bf0158c0 00000000 bf015598 bf0155b8
4b87ad6e
be20: c5915c00 bf015970 00000000 bf015598 bf0155b8 00000000 c591be7c
c591be48
be40: bf01211c bf0126d4 00000000 c013f190 c0fc9a40 00000000 bf0155b8
bf0158c0
be60: c02f5150 bf0158c0 c591a000 00000001 c591be9c c591be80 c015237c
bf011e3c
be80: c591be9c bf0158d4 bf0155b8 c02f51b0 c591beb4 c591bea0 c01758e0
c01522d0
bea0: bf015904 bf0155b8 c591bed4 c591beb8 c0175960 c017589c c591bed4
bf0155b8
bec0: bf00f240 bf0155b8 c591befc c591bed8 c0175b18 c0175910 c0178610
bf0155b8
bee0: bf00f240 bf0155dc 00000000 bf0158c0 c591bf1c c591bf00 c0174a94
c0175acc
bf00: bf0155b8 c0fc9f60 bf0155b8 bf00f56c c591bf34 c591bf20 c0151674
c0174a1c
bf20: 00000000 c0fc9f60 c591bf5c c591bf38 bf00b398 c01515e4 bf0155a4
c02ec308
bf40: c591a000 c02ec2f8 00000000 00000002 c591bf74 c591bf60 bf017064
bf00b1cc
bf60: c02ec308 bf015a40 c591bfa4 c591bf78 c006de74 bf017010 c591bfa4
00008f08
bf80: 00012018 00000003 00000080 c00362f4 c591a000 00900080 00000000
c591bfa8
bfa0: c0035b60 c006dcb4 00008f08 00012018 00012018 00005d29 00012008
00004000
bfc0: 00008f08 00012018 00000003 befffc9c 00008000 00000000 00012008
00000000
bfe0: 400d0740 befffc8c 00008dbc 400d074c 60000010 00012018 00000000
fffb73ff
Backtrace:
[<c004470c>] (__clk_use+0x0/0x20) from [<c0044840>] (clk_use+0x34/0x60)
[<c004480c>] (clk_use+0x0/0x60) from [<bf01270c>] (InitDavinci+0x48/0x2dc
[sdio_davinci_hcd])
r6 = 0000001B r5 = C5915C00 r4 = FFFFFFFE
[<bf0126c4>] (InitDavinci+0x0/0x2dc [sdio_davinci_hcd]) from [<bf01211c>]
(Probe+0x2f0/0x48c [sdio_davinci_hcd])
[<bf011e2c>] (Probe+0x0/0x48c [sdio_davinci_hcd]) from [<c015237c>]
(pnp_device_probe+0xbc/0xe8)
[<c01522c0>] (pnp_device_probe+0x0/0xe8) from [<c01758e0>]
(driver_probe_device+0x54/0x74)
r6 = C02F51B0 r5 = BF0155B8 r4 = BF0158D4
[<c017588c>] (driver_probe_device+0x0/0x74) from [<c0175960>]
(device_attach+0x60/0xa4)
r5 = BF0155B8 r4 = BF015904
[<c0175900>] (device_attach+0x0/0xa4) from [<c0175b18>]
(bus_add_device+0x5c/0x10c)
r6 = BF0155B8 r5 = BF00F240 r4 = BF0155B8
[<c0175abc>] (bus_add_device+0x0/0x10c) from [<c0174a94>]
(device_add+0x88/0x11c)
r8 = BF0158C0 r7 = 00000000 r6 = BF0155DC r5 = BF00F240
r4 = BF0155B8
[<c0174a0c>] (device_add+0x0/0x11c) from [<c0151674>]
(__pnp_add_device+0xa0/0xc8)
r7 = BF00F56C r6 = BF0155B8 r5 = C0FC9F60 r4 = BF0155B8
[<c01515d4>] (__pnp_add_device+0x0/0xc8) from [<bf00b398>]
(SDIO_BusAddOSDevice+0x1dc/0x2b0 [sdio_busdriver])
r5 = C0FC9F60 r4 = 00000000
[<bf00b1bc>] (SDIO_BusAddOSDevice+0x0/0x2b0 [sdio_busdriver]) from
[<bf017064>] (sdio_local_hcd_init+0x64/0xec [sdio_davinci_hcd])
[<bf017000>] (sdio_local_hcd_init+0x0/0xec [sdio_davinci_hcd]) from
[<c006de74>] (sys_init_module+0x1d0/0x3e0)
r4 = BF015A40
[<c006dca4>] (sys_init_module+0x0/0x3e0) from [<c0035b60>]
(ret_fast_syscall+0x0/0x2c)
Code: e89da800 e1a0c00d e92dd800 e24cb004 (e5d03014)
<6>note: insmod[1112] exited with preempt_count 1
BUG: scheduling while atomic: insmod/0x00000001/1112
caller is do_exit+0xd3c/0xda0
Segmentation fault
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20080523/f65f9ba0/attachment-0001.htm
------------------------------
Message: 3
Date: Thu, 22 May 2008 21:13:45 -0700 (PDT)
From: Viet Hoang <[EMAIL PROTECTED]>
Subject: DM355 - Using GPIO pin for interrupt: Strange problem
To: davinci-linux-open-source
<[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=utf-8
Hi all,
So, I am still using DM355's GPIO6 for interrupt
(http://linux.omap.com/pipermail/davinci-linux-open-source/2008-March/005530.html).
The old problem is still there and I use software to reject the raising
edge.
But now, I meet a strange problem, when the board is powered on, the
GPIO6 interrupt works well. But after about 3-4 minutes, it stops
receiving interrupt signal, regardless of the GPIO6 interrupt function is
being used or not (after the board is powered on). With a scope, I can see
the interrupt signal is still operating, but by adding a printk in
irq_hanle function, I see that the board no longer runs to that function.
Has any one have a similar experience? I would be very appreciated if
you could share the way you fixed it.
Viet Hoang.
Send instant messages to your online friends http://uk.messenger.yahoo.com
------------------------------
Message: 4
Date: Fri, 23 May 2008 15:45:35 +0800
From: Goung <[EMAIL PROTECTED]>
Subject: Re: Error in formating SDHC 8G card in DM6446??
To: "Rajashekhara, Sudhakar" <[EMAIL PROTECTED]>
Cc: "[email protected]"
<[email protected]>
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text/plain; charset="iso-8859-1"
HI,Sudhakar
Thanks for your immediate response.
Until now, the method seems work fine in format SDHC 8G attach a
parameter by block number .
But when i using format , i get a warning: (This can be ignored?)
# mkfs.vfat -F32 /dev/mmcblk0p1 8008371
mkfs.vfat 2.11 (12 Mar 2005)
Warning: block count mismatch: found 1048576 but assuming
8008371.
I think i should write a detecting code before using formating ,because
sometimes i don't know what kind of cards were inserted.
I feel this step is a little redundancy , could we just format without
other
parameters ??
I guess maybe it's caused by some functions in sdio_memory ????
anyway, thanks very much for your answer.
2008/5/22 Rajashekhara, Sudhakar <[EMAIL PROTECTED]>:
Goung,
While running mkdosfs passing the number of blocks as an argument should
solve your problem. The number of blocks can be obtained by running the
fdisk command (4th column). The sample output of fdisk command when run
on
hda is shown below.
[EMAIL PROTECTED]:~# fdisk /dev/hda
The number of cylinders for this disk is set to 4864.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/hda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 4377 35158221 83 Linux
/dev/hda2 4378 4864 3911827+ c W95 FAT32 (LBA)
Regards, Sudhakar
________________________________________
From: [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] On Behalf Of
Goung
Sent: Thursday, May 22, 2008 11:59 AM
To: [email protected]
Subject: Error in formating SDHC 8G card in DM6446??
Hi,
I am using Linux version 2.6.10_mvl401-davinci_evm and already using
patch
045 from TI.
It work fine in 2G SD card whit FAT32 or other file systems,
but when i format SDHC 8G using FAT 32, it gets some troubles:
The size is wrong , the message as follow:
# ./mkdosfs -F 32 /dev/mmcblk0
mkdosfs 2.11 (12 Mar 2005)
# df -m
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/mmcblk0 1022 0 1022 0% /mnt/sd
And then i test read/write operation in /mnt/sd, it encounter the follow
messages:
#cp /mnt/sd/test.img /mnt/sd/test1.img (test.img size is 10MB)
cp: Read error: Input/output error
But when i using format in desktop (fedora core 6 in desktop) by usb card
reader,
the size is correct.
#./mkdosfs -F 32 /dev/sda1
# df -m
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/mmcblk0 7807 0 7807 0% /mnt/sd
and then i test read/write operation in /mnt/sd, everything is ok.
I guess it may be wrong in MBR when format, but i don't know how to fix
this problem.
Any help will be very appreciated
Thanks very much for your answer.
----------------------------------------------------- test log
--------------------------------------------------
---using ext2 in 8G SDHC card --------
#lsmod
Module Size Used by Tainted: PF
sdio_memory_fd 28032 0 - Live 0xbf03c000
sdio_davinci_hcd 27388 0 - Live 0xbf034000
sdio_busdriver 88528 2 sdio_memory_fd,sdio_davinci_hcd, Live 0xbf01d000
sdio_lib 11232 3 sdio_memory_fd,sdio_davinci_hcd,sdio_busdriver, Live
0xbf019000
dsplinkk 68632 0 - Live 0xbf007000
cmemk 12476 0 - Live 0xbf002000
dspon 1376 0 - Live 0xbf000000
#mkfs.ext2 /dev/mmcblk0p1
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
1001920 inodes, 2002092 blocks
100104 blocks (5.00%) reserved for the super user
First data block=0
62 block groups
32768 blocks per group, 32768 fragments per group
16160 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Writing inode tables: 0/62 1/62 2/62 3/62 4/62
5/62 6/62 7/62 8/62 9/62 10/62 11/62
12/62
13/62 14/62 15/62 16/62 17/62 18/62 19/62
20/62 21/62 22/62 23/62 24/62 25/62 26/62
27/62
28/62 29/62 30/62 31/62 32/62 33/62 34/62
35/62 36/62 37/62 38/62 39/62 40/62 41/62
42/62
43/62 44/62 45/62 46/62 47/62 48/62 49/62
50/62 51/62 52/62 53/62 54/62 55/62 56/62
57/62
58/62 59/62 60/62 61/62 done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 24 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
#mount /dev/mmcblk0p1 /mnt/sd
#mount |grep sd
/dev/mmcblk0p1 on /mnt/sd type ext2 (rw,nogrpid)
#df -m | grep sd
/dev/mmcblk0p1 7698 0 7307 0% /mnt/sd
#cp /tmp/ftp_temp/test.img /mnt/sd
#cp /mnt/sd/test.img /mnt/sd/test2.img
#df -m | grep sd
/dev/mmcblk0p1 7698 36 7271 0% /mnt/sd
Everythings is ok .
---------------------------------------using FAT32 in 8G SDHC card
--------------------------------------
#./mkdosfs -F32 /dev/mmcblk0p1
mkdosfs 2.11 (12 Mar 2005)
#mount /dev/mmcblk0p1 /mnt/sd
#mount | grep sd
/dev/mmcblk0p1 on /mnt/sd type vfat (rw,nodiratime,fmask=0033,dmask=0033)
#df -m |grep sd
/dev/mmcblk0p1 1022 0 1022 0% /mnt/sd
#cp /tmp/ftp_temp/test.img /mnt/sd
#cp /mnt/sd/test.img /mnt/sd/tes2.img
The size of mount in sd folder is wrong with 1022 (0.99G).
--
Best Regards,
Goung.
--
Best Regards,
Goung.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20080523/ab64aa2c/attachment.htm
------------------------------
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
End of Davinci-linux-open-source Digest, Vol 29, Issue 84
*********************************************************
Email Scanned for Virus & Dengerous Content.
