* Re: Testing Infrastructure for SD/MMC Commands [not found] <CANYdXnoZK3OoWOnJhyq645GofnsXuk7tJm09Wv8=Y+gLujPSkQ@mail.gmail.com> @ 2011-08-16 9:26 ` Shashidhar Hiremath 2011-08-16 16:03 ` J Freyensee ` (2 more replies) 0 siblings, 3 replies; 5+ messages in thread From: Shashidhar Hiremath @ 2011-08-16 9:26 UTC (permalink / raw) To: cjb, Will Newton, Jae hoon Chung, James Hogan, kyungmin.park; +Cc: linux-mmc adding mmc mailing list On Tue, Aug 16, 2011 at 11:12 AM, Shashidhar Hiremath <shashidharh@vayavyalabs.com> wrote: > Hi All, > i am planning to come up with a module that would help for testing > the SD/MMC controller to see if supports the particular command. > > For example ,Through this module , we will be able to see if a > particular command has been accepted by the device and whether device > has responded in the expected manner or not by checking its response. > > Can I get some points on how useful this infrastructure would be ,and > any inputs on what else to cover under this ? > -- regards, Shashidhar Hiremath ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Testing Infrastructure for SD/MMC Commands 2011-08-16 9:26 ` Testing Infrastructure for SD/MMC Commands Shashidhar Hiremath @ 2011-08-16 16:03 ` J Freyensee 2011-08-16 16:11 ` Chris Ball 2011-08-17 13:51 ` seedshope 2 siblings, 0 replies; 5+ messages in thread From: J Freyensee @ 2011-08-16 16:03 UTC (permalink / raw) To: Shashidhar Hiremath Cc: cjb, Will Newton, Jae hoon Chung, James Hogan, kyungmin.park, linux-mmc On 08/16/2011 02:26 AM, Shashidhar Hiremath wrote: > adding mmc mailing list > > On Tue, Aug 16, 2011 at 11:12 AM, Shashidhar Hiremath > <shashidharh@vayavyalabs.com> wrote: >> Hi All, >> i am planning to come up with a module that would help for testing >> the SD/MMC controller to see if supports the particular command. >> >> For example ,Through this module , we will be able to see if a >> particular command has been accepted by the device and whether device >> has responded in the expected manner or not by checking its response. >> >> Can I get some points on how useful this infrastructure would be ,and >> any inputs on what else to cover under this ? >> > It sounds like you are looking to design a functional model, a module that utilizes some type of design spec or standard to verify if the design implementation works according to the design-spec/standard, correct? If true, my first question would be, what document will you be basing this module on? It probably could be useful- the more testing on something the better. But I think the first step is you need to define what document/spec/standard this module is going to follow, then how this module is going to be designed and used, then go from there. > > -- J (James/Jay) Freyensee Storage Technology Group Intel Corporation ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Testing Infrastructure for SD/MMC Commands 2011-08-16 9:26 ` Testing Infrastructure for SD/MMC Commands Shashidhar Hiremath 2011-08-16 16:03 ` J Freyensee @ 2011-08-16 16:11 ` Chris Ball 2011-08-17 13:51 ` seedshope 2 siblings, 0 replies; 5+ messages in thread From: Chris Ball @ 2011-08-16 16:11 UTC (permalink / raw) To: Shashidhar Hiremath Cc: Will Newton, Jae hoon Chung, James Hogan, kyungmin.park, linux-mmc Hi Shashidhar, On Tue, Aug 16 2011, Shashidhar Hiremath wrote: > i am planning to come up with a module that would help for testing > the SD/MMC controller to see if supports the particular command. > > For example ,Through this module , we will be able to see if a > particular command has been accepted by the device and whether device > has responded in the expected manner or not by checking its response. > > Can I get some points on how useful this infrastructure would be ,and > any inputs on what else to cover under this ? You could consider using John Calixto's CMD passthrough ioctl for this, and writing your tests in userspace: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=cb87ea28ed9e75a41eb456bfcb547b4e6f10e750 It would be great to include your finished tool in a testsuite, both for testing card commands and for testing the ioctl functionality itself. :) Thanks! - Chris. -- Chris Ball <cjb@laptop.org> <http://printf.net/> One Laptop Per Child ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Testing Infrastructure for SD/MMC Commands 2011-08-16 9:26 ` Testing Infrastructure for SD/MMC Commands Shashidhar Hiremath 2011-08-16 16:03 ` J Freyensee 2011-08-16 16:11 ` Chris Ball @ 2011-08-17 13:51 ` seedshope 2011-08-17 14:11 ` about MicroSD transport issue for the current mainline kernel seedshope 2 siblings, 1 reply; 5+ messages in thread From: seedshope @ 2011-08-17 13:51 UTC (permalink / raw) To: linux-mmc; +Cc: bobo Hi All, I uses potevio MicroSD 512M to test the SD/MMC driver in current master kernel. I found some issue: 1. The issue (1) After I insert the microSD,Why The SD card probe finish(The parrition and device has already register). But The more and more data transport between card and host? Who can told me the function of this data.(The log information as following). (2) The MicroSD can be probe successful. But The error information display on the processor of multi-block data transfer. Any advices are welcome! 2. Kernel configure: CONFIG_MMC = y CONFIG_MMC_DEBUG = y CONFIG_MMC_BLOCK = y CONFIG_MMC_SDHCI = y CONFIG_MMC_SDHCI_PCI = y 3. Debug information: mmc0: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 20 width 0 timing 0 mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0 mmc0: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0 mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0 mmc0: req failed (CMD5): -110, retrying... mmc0: req failed (CMD5): -110, retrying... mmc0: req failed (CMD5): -110, retrying... mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0 mmc0: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0 mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0 mmc0: clock 400000Hz busmode 2 powermode 2 cs 0 Vdd 20 width 0 timing 0 mmc0: clock 400000Hz busmode 2 powermode 2 cs 0 Vdd 20 width 0 timing 2 mmc0: clock 50000000Hz busmode 2 powermode 2 cs 0 Vdd 20 width 0 timing 2 mmc0: clock 50000000Hz busmode 2 powermode 2 cs 0 Vdd 20 width 2 timing 2 mmc0: new high speed SD card at address 0002 mmcblk0: mmc0:0002 N/A 484 MiB mmcblk0: p1 mmcblk0: retrying using single block read mmcblk0: error -84 transferring data, sector 57, nr 71, card status 0x900 end_request: I/O error, dev mmcblk0, sector 57 mmcblk0: error -84 transferring data, sector 61, nr 67, card status 0x900 end_request: I/O error, dev mmcblk0, sector 61 quiet_error: 15 callbacks suppressed Buffer I/O error on device mmcblk0, logical block 7 mmcblk0: error -84 transferring data, sector 65, nr 63, card status 0x900 end_request: I/O error, dev mmcblk0, sector 65 mmcblk0: error -84 transferring data, sector 69, nr 59, card status 0x900 end_request: I/O error, dev mmcblk0, sector 69 mmcblk0: error -84 transferring data, sector 71, nr 57, card status 0x900 end_request: I/O error, dev mmcblk0, sector 71 Buffer I/O error on device mmcblk0, logical block 8 mmcblk0: error -84 transferring data, sector 73, nr 55, card status 0x900 end_request: I/O error, dev mmcblk0, sector 73 mmcblk0: error -84 transferring data, sector 77, nr 51, card status 0x900 end_request: I/O error, dev mmcblk0, sector 77 Buffer I/O error on device mmcblk0, logical block 9 mmcblk0: error -84 transferring data, sector 87, nr 41, card status 0x900 end_request: I/O error, dev mmcblk0, sector 87 Buffer I/O error on device mmcblk0, logical block 10 mmcblk0: error -84 transferring data, sector 127, nr 1, card status 0x900 end_request: I/O error, dev mmcblk0, sector 127 Buffer I/O error on device mmcblk0, logical block 15 mmcblk0: retrying using single block read mmcblk0: error -84 transferring data, sector 143, nr 113, card status 0x900 end_request: I/O error, dev mmcblk0, sector 143 Buffer I/O error on device mmcblk0, logical block 17 mmcblk0: error -84 transferring data, sector 151, nr 105, card status 0x900 end_request: I/O error, dev mmcblk0, sector 151 Buffer I/O error on device mmcblk0, logical block 18 mmcblk0: error -84 transferring data, sector 161, nr 95, card status 0x900 end_request: I/O error, dev mmcblk0, sector 161 mmcblk0: error -84 transferring data, sector 215, nr 41, card status 0x900 end_request: I/O error, dev mmcblk0, sector 215 Buffer I/O error on device mmcblk0, logical block 26 mmcblk0: error -84 transferring data, sector 217, nr 39, card status 0x900 end_request: I/O error, dev mmcblk0, sector 217 mmcblk0: retrying using single block read mmcblk0: error -84 transferring data, sector 57, nr 7, card status 0x900 end_request: I/O error, dev mmcblk0, sector 57 mmcblk0: retrying using single block read mmcblk0: error -84 transferring data, sector 535, nr 9, card status 0x900 end_request: I/O error, dev mmcblk0, sector 535 mmcblk0: retrying using single block read mmcblk0: error -84 transferring data, sector 535, nr 1, card status 0x900 end_request: I/O error, dev mmcblk0, sector 535 mmcblk0: retrying using single block read mmcblk0: retrying using single block read mmcblk0: error -84 transferring data, sector 193, nr 116, card status 0x900 end_request: I/O error, dev mmcblk0, sector 193 mmcblk0: error -84 transferring data, sector 215, nr 94, card status 0x900 end_request: I/O error, dev mmcblk0, sector 215 mmcblk0: error -84 transferring data, sector 217, nr 92, card status 0x900 end_request: I/O error, dev mmcblk0, sector 217 mmcblk0: error -84 transferring data, sector 279, nr 30, card status 0x900 end_request: I/O error, dev mmcblk0, sector 279 mmcblk0: error -84 transferring data, sector 289, nr 20, card status 0x900 end_request: I/O error, dev mmcblk0, sector 289 mmcblk0: retrying using single block read mmcblk0: error -84 transferring data, sector 57, nr 124, card status 0x900 end_request: I/O error, dev mmcblk0, sector 57 mmcblk0: error -84 transferring data, sector 61, nr 120, card status 0x900 end_request: I/O error, dev mmcblk0, sector 61 mmcblk0: error -84 transferring data, sector 65, nr 116, card status 0x900 end_request: I/O error, dev mmcblk0, sector 65 mmcblk0: error -84 transferring data, sector 71, nr 110, card status 0x900 end_request: I/O error, dev mmcblk0, sector 71 mmcblk0: error -84 transferring data, sector 75, nr 106, card status 0x900 end_request: I/O error, dev mmcblk0, sector 75 mmcblk0: error -84 transferring data, sector 77, nr 104, card status 0x900 end_request: I/O error, dev mmcblk0, sector 77 mmcblk0: error -84 transferring data, sector 79, nr 102, card status 0x900 end_request: I/O error, dev mmcblk0, sector 79 mmcblk0: error -84 transferring data, sector 81, nr 100, card status 0x900 end_request: I/O error, dev mmcblk0, sector 81 mmcblk0: error -84 transferring data, sector 85, nr 96, card status 0x900 end_request: I/O error, dev mmcblk0, sector 85 mmcblk0: error -84 transferring data, sector 87, nr 94, card status 0x900 end_request: I/O error, dev mmcblk0, sector 87 mmcblk0: error -84 transferring data, sector 103, nr 78, card status 0x900 end_request: I/O error, dev mmcblk0, sector 103 mmcblk0: error -84 transferring data, sector 127, nr 54, card status 0x900 end_request: I/O error, dev mmcblk0, sector 127 mmcblk0: error -84 transferring data, sector 143, nr 38, card status 0x900 end_request: I/O error, dev mmcblk0, sector 143 mmcblk0: error -84 transferring data, sector 151, nr 30, card status 0x900 end_request: I/O error, dev mmcblk0, sector 151 mmcblk0: error -84 transferring data, sector 161, nr 20, card status 0x900 end_request: I/O error, dev mmcblk0, sector 161 mmcblk0: error -84 transferring data, sector 177, nr 4, card status 0x900 end_request: I/O error, dev mmcblk0, sector 177 mmcblk0: error -84 transferring data, sector 57, nr 1, card status 0x900 end_request: I/O error, dev mmcblk0, sector 57 Thanks hongbo ^ permalink raw reply [flat|nested] 5+ messages in thread
* about MicroSD transport issue for the current mainline kernel 2011-08-17 13:51 ` seedshope @ 2011-08-17 14:11 ` seedshope 0 siblings, 0 replies; 5+ messages in thread From: seedshope @ 2011-08-17 14:11 UTC (permalink / raw) To: linux-mmc On 08/17/2011 09:51 PM, seedshope wrote: > Hi All, > > I uses potevio MicroSD 512M to test the SD/MMC driver in current master > kernel. I found some issue: > > 1. The issue > (1) After I insert the microSD,Why The SD card probe finish(The > parrition and device has already register). But The more and more data > transport between card and host? Who can told me the function of this > data.(The log information as following). > > (2) The MicroSD can be probe successful. But The error information > display on the processor of multi-block data transfer. > > Any advices are welcome! > > > 2. Kernel configure: > CONFIG_MMC = y > CONFIG_MMC_DEBUG = y > CONFIG_MMC_BLOCK = y > CONFIG_MMC_SDHCI = y > CONFIG_MMC_SDHCI_PCI = y > > 3. Debug information: > mmc0: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 20 width 0 timing 0 > mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0 > mmc0: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0 > mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0 > mmc0: req failed (CMD5): -110, retrying... > mmc0: req failed (CMD5): -110, retrying... > mmc0: req failed (CMD5): -110, retrying... > mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0 > mmc0: clock 400000Hz busmode 1 powermode 2 cs 1 Vdd 20 width 0 timing 0 > mmc0: clock 400000Hz busmode 1 powermode 2 cs 0 Vdd 20 width 0 timing 0 > mmc0: clock 400000Hz busmode 2 powermode 2 cs 0 Vdd 20 width 0 timing 0 > mmc0: clock 400000Hz busmode 2 powermode 2 cs 0 Vdd 20 width 0 timing 2 > mmc0: clock 50000000Hz busmode 2 powermode 2 cs 0 Vdd 20 width 0 timing 2 > mmc0: clock 50000000Hz busmode 2 powermode 2 cs 0 Vdd 20 width 2 timing 2 > mmc0: new high speed SD card at address 0002 > mmcblk0: mmc0:0002 N/A 484 MiB > mmcblk0: p1 > mmcblk0: retrying using single block read > mmcblk0: error -84 transferring data, sector 57, nr 71, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 57 > mmcblk0: error -84 transferring data, sector 61, nr 67, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 61 > quiet_error: 15 callbacks suppressed > Buffer I/O error on device mmcblk0, logical block 7 > mmcblk0: error -84 transferring data, sector 65, nr 63, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 65 > mmcblk0: error -84 transferring data, sector 69, nr 59, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 69 > mmcblk0: error -84 transferring data, sector 71, nr 57, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 71 > Buffer I/O error on device mmcblk0, logical block 8 > mmcblk0: error -84 transferring data, sector 73, nr 55, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 73 > mmcblk0: error -84 transferring data, sector 77, nr 51, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 77 > Buffer I/O error on device mmcblk0, logical block 9 > mmcblk0: error -84 transferring data, sector 87, nr 41, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 87 > Buffer I/O error on device mmcblk0, logical block 10 > mmcblk0: error -84 transferring data, sector 127, nr 1, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 127 > Buffer I/O error on device mmcblk0, logical block 15 > mmcblk0: retrying using single block read > mmcblk0: error -84 transferring data, sector 143, nr 113, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 143 > Buffer I/O error on device mmcblk0, logical block 17 > mmcblk0: error -84 transferring data, sector 151, nr 105, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 151 > Buffer I/O error on device mmcblk0, logical block 18 > mmcblk0: error -84 transferring data, sector 161, nr 95, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 161 > mmcblk0: error -84 transferring data, sector 215, nr 41, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 215 > Buffer I/O error on device mmcblk0, logical block 26 > mmcblk0: error -84 transferring data, sector 217, nr 39, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 217 > mmcblk0: retrying using single block read > mmcblk0: error -84 transferring data, sector 57, nr 7, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 57 > mmcblk0: retrying using single block read > mmcblk0: error -84 transferring data, sector 535, nr 9, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 535 > mmcblk0: retrying using single block read > mmcblk0: error -84 transferring data, sector 535, nr 1, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 535 > mmcblk0: retrying using single block read > mmcblk0: retrying using single block read > mmcblk0: error -84 transferring data, sector 193, nr 116, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 193 > mmcblk0: error -84 transferring data, sector 215, nr 94, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 215 > mmcblk0: error -84 transferring data, sector 217, nr 92, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 217 > mmcblk0: error -84 transferring data, sector 279, nr 30, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 279 > mmcblk0: error -84 transferring data, sector 289, nr 20, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 289 > mmcblk0: retrying using single block read > mmcblk0: error -84 transferring data, sector 57, nr 124, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 57 > mmcblk0: error -84 transferring data, sector 61, nr 120, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 61 > mmcblk0: error -84 transferring data, sector 65, nr 116, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 65 > mmcblk0: error -84 transferring data, sector 71, nr 110, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 71 > mmcblk0: error -84 transferring data, sector 75, nr 106, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 75 > mmcblk0: error -84 transferring data, sector 77, nr 104, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 77 > mmcblk0: error -84 transferring data, sector 79, nr 102, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 79 > mmcblk0: error -84 transferring data, sector 81, nr 100, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 81 > mmcblk0: error -84 transferring data, sector 85, nr 96, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 85 > mmcblk0: error -84 transferring data, sector 87, nr 94, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 87 > mmcblk0: error -84 transferring data, sector 103, nr 78, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 103 > mmcblk0: error -84 transferring data, sector 127, nr 54, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 127 > mmcblk0: error -84 transferring data, sector 143, nr 38, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 143 > mmcblk0: error -84 transferring data, sector 151, nr 30, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 151 > mmcblk0: error -84 transferring data, sector 161, nr 20, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 161 > mmcblk0: error -84 transferring data, sector 177, nr 4, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 177 > mmcblk0: error -84 transferring data, sector 57, nr 1, card status 0x900 > end_request: I/O error, dev mmcblk0, sector 57 > > > Thanks > hongbo ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2011-08-17 14:11 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CANYdXnoZK3OoWOnJhyq645GofnsXuk7tJm09Wv8=Y+gLujPSkQ@mail.gmail.com>
2011-08-16 9:26 ` Testing Infrastructure for SD/MMC Commands Shashidhar Hiremath
2011-08-16 16:03 ` J Freyensee
2011-08-16 16:11 ` Chris Ball
2011-08-17 13:51 ` seedshope
2011-08-17 14:11 ` about MicroSD transport issue for the current mainline kernel seedshope
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.