RE: [PATCH] Disable the non working eMMC on Zoom2/3
> -Original Message- > From: zhangfei gao [mailto:zhangfei@gmail.com] > Sent: Thursday, June 24, 2010 4:26 PM > To: Ghorai, Sukumar > Cc: Chikkature Rajashekar, Madhusudhan; Tony Lindgren; Menon, Nishanth; > linux-omap@vger.kernel.org; linux-...@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > On Tue, Jun 22, 2010 at 7:43 PM, Ghorai, Sukumar wrote: > > > > > >> -Original Message- > >> From: zhangfei gao [mailto:zhangfei@gmail.com] > >> Sent: Tuesday, June 22, 2010 4:51 PM > >> To: Chikkature Rajashekar, Madhusudhan > >> Cc: Tony Lindgren; Menon, Nishanth; Ghorai, Sukumar; linux- > >> o...@vger.kernel.org; linux-...@vger.kernel.org > >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > >> > >> On Sat, May 8, 2010 at 5:25 AM, Madhusudhan wrote: > >> > > >> > > >> >> -Original Message- > >> >> From: Tony Lindgren [mailto:t...@atomide.com] > >> >> Sent: Thursday, May 06, 2010 10:31 AM > >> >> To: Madhusudhan > >> >> Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > >> >> linux-...@vger.kernel.org > >> >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > >> >> > >> >> * Madhusudhan [100505 18:31]: > >> >> > > >> >> > > >> >> > > -Original Message- > >> >> > > From: Tony Lindgren [mailto:t...@atomide.com] > >> >> > > >> >> > > And what about this "Simulate multi mmc card as one big" patch? > >> >> > > > >> >> > Did not get you, what patch are you referring to? > >> >> > >> >> Oops sorry forgot the link: > >> >> > >> >> https://patchwork.kernel.org/patch/87944/ > >> >> > >> > This will not help. I don't know the history of the patch but what > this > >> is > >> > intended for is to support multiple MMC cards connected to a single > >> > controller. But on the Zoom the eMMC we are talking about is > connected > >> to > >> > MMC2. > >> > > >> > Regards, > >> > Madhu > >> > > >> >> Tony > >> > > >> > -- > >> > To unsubscribe from this list: send the line "unsubscribe linux-mmc" > in > >> > the body of a message to majord...@vger.kernel.org > >> > More majordomo info at http://vger.kernel.org/majordomo-info.html > >> > > >> > >> Hi, Guys > >> > >> Just wander whether 16G Micron eMMC works on your platform. > >> I also have such issue, 16G Micron emmc can not work with read and > >> write, with data timeout. > >> While 8G Micron eMMC workable. > >> Do you have the same issue? > > > > [Ghorai] we have 16G eMMC in ZOOM3 and 3630-SDP and its working fine. > Let me know what board you are using. > > mmc1: new high speed MMC card at address 0001 > > PM: Adding info for mmc:mmc1:0001 > > mmcblk0: mmc1:0001 STM16G 14.8 GiB > > PM: Adding info for No Bus:mmcblk0 > > mmcblk0: p1 p2 > >> > >> Thanks > > > > Hi, Ghorai > > Thanks for your valueable info. > We also enabled Micron 16G eMMC, two issues stuck us before. > 1. The bus_width should be inited otherwise read ext_csd would be fail. > 2. The emmc may stay in boot partition and kernel should switch to > user partition, where filesystem is located. [Ghorai] 1. If my understanding is not wrong, then the same problem exists in external MMC card too. 2. So, can you share your eMMC log, just to check if I have any clue! Or let me know how I can reproduce the issue. > > Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Disable the non working eMMC on Zoom2/3
On Tue, Jun 22, 2010 at 7:43 PM, Ghorai, Sukumar wrote: > > >> -Original Message- >> From: zhangfei gao [mailto:zhangfei@gmail.com] >> Sent: Tuesday, June 22, 2010 4:51 PM >> To: Chikkature Rajashekar, Madhusudhan >> Cc: Tony Lindgren; Menon, Nishanth; Ghorai, Sukumar; linux- >> o...@vger.kernel.org; linux-...@vger.kernel.org >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 >> >> On Sat, May 8, 2010 at 5:25 AM, Madhusudhan wrote: >> > >> > >> >> -Original Message- >> >> From: Tony Lindgren [mailto:t...@atomide.com] >> >> Sent: Thursday, May 06, 2010 10:31 AM >> >> To: Madhusudhan >> >> Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; >> >> linux-...@vger.kernel.org >> >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 >> >> >> >> * Madhusudhan [100505 18:31]: >> >> > >> >> > >> >> > > -Original Message- >> >> > > From: Tony Lindgren [mailto:t...@atomide.com] >> >> > >> >> > > And what about this "Simulate multi mmc card as one big" patch? >> >> > > >> >> > Did not get you, what patch are you referring to? >> >> >> >> Oops sorry forgot the link: >> >> >> >> https://patchwork.kernel.org/patch/87944/ >> >> >> > This will not help. I don't know the history of the patch but what this >> is >> > intended for is to support multiple MMC cards connected to a single >> > controller. But on the Zoom the eMMC we are talking about is connected >> to >> > MMC2. >> > >> > Regards, >> > Madhu >> > >> >> Tony >> > >> > -- >> > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in >> > the body of a message to majord...@vger.kernel.org >> > More majordomo info at http://vger.kernel.org/majordomo-info.html >> > >> >> Hi, Guys >> >> Just wander whether 16G Micron eMMC works on your platform. >> I also have such issue, 16G Micron emmc can not work with read and >> write, with data timeout. >> While 8G Micron eMMC workable. >> Do you have the same issue? > > [Ghorai] we have 16G eMMC in ZOOM3 and 3630-SDP and its working fine. Let me > know what board you are using. > mmc1: new high speed MMC card at address 0001 > PM: Adding info for mmc:mmc1:0001 > mmcblk0: mmc1:0001 STM16G 14.8 GiB > PM: Adding info for No Bus:mmcblk0 > mmcblk0: p1 p2 >> >> Thanks > Hi, Ghorai Thanks for your valueable info. We also enabled Micron 16G eMMC, two issues stuck us before. 1. The bus_width should be inited otherwise read ext_csd would be fail. 2. The emmc may stay in boot partition and kernel should switch to user partition, where filesystem is located. Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH] Disable the non working eMMC on Zoom2/3
> -Original Message- > From: zhangfei gao [mailto:zhangfei@gmail.com] > Sent: Tuesday, June 22, 2010 4:51 PM > To: Chikkature Rajashekar, Madhusudhan > Cc: Tony Lindgren; Menon, Nishanth; Ghorai, Sukumar; linux- > o...@vger.kernel.org; linux-...@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > On Sat, May 8, 2010 at 5:25 AM, Madhusudhan wrote: > > > > > >> -Original Message- > >> From: Tony Lindgren [mailto:t...@atomide.com] > >> Sent: Thursday, May 06, 2010 10:31 AM > >> To: Madhusudhan > >> Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > >> linux-...@vger.kernel.org > >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > >> > >> * Madhusudhan [100505 18:31]: > >> > > >> > > >> > > -Original Message- > >> > > From: Tony Lindgren [mailto:t...@atomide.com] > >> > > >> > > And what about this "Simulate multi mmc card as one big" patch? > >> > > > >> > Did not get you, what patch are you referring to? > >> > >> Oops sorry forgot the link: > >> > >> https://patchwork.kernel.org/patch/87944/ > >> > > This will not help. I don't know the history of the patch but what this > is > > intended for is to support multiple MMC cards connected to a single > > controller. But on the Zoom the eMMC we are talking about is connected > to > > MMC2. > > > > Regards, > > Madhu > > > >> Tony > > > > -- > > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in > > the body of a message to majord...@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > > Hi, Guys > > Just wander whether 16G Micron eMMC works on your platform. > I also have such issue, 16G Micron emmc can not work with read and > write, with data timeout. > While 8G Micron eMMC workable. > Do you have the same issue? [Ghorai] we have 16G eMMC in ZOOM3 and 3630-SDP and its working fine. Let me know what board you are using. mmc1: new high speed MMC card at address 0001 PM: Adding info for mmc:mmc1:0001 mmcblk0: mmc1:0001 STM16G 14.8 GiB PM: Adding info for No Bus:mmcblk0 mmcblk0: p1 p2 > > Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Disable the non working eMMC on Zoom2/3
On Sat, May 8, 2010 at 5:25 AM, Madhusudhan wrote: > > >> -Original Message- >> From: Tony Lindgren [mailto:t...@atomide.com] >> Sent: Thursday, May 06, 2010 10:31 AM >> To: Madhusudhan >> Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; >> linux-...@vger.kernel.org >> Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 >> >> * Madhusudhan [100505 18:31]: >> > >> > >> > > -Original Message- >> > > From: Tony Lindgren [mailto:t...@atomide.com] >> > >> > > And what about this "Simulate multi mmc card as one big" patch? >> > > >> > Did not get you, what patch are you referring to? >> >> Oops sorry forgot the link: >> >> https://patchwork.kernel.org/patch/87944/ >> > This will not help. I don't know the history of the patch but what this is > intended for is to support multiple MMC cards connected to a single > controller. But on the Zoom the eMMC we are talking about is connected to > MMC2. > > Regards, > Madhu > >> Tony > > -- > To unsubscribe from this list: send the line "unsubscribe linux-mmc" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Hi, Guys Just wander whether 16G Micron eMMC works on your platform. I also have such issue, 16G Micron emmc can not work with read and write, with data timeout. While 8G Micron eMMC workable. Do you have the same issue? Thanks -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH] Disable the non working eMMC on Zoom2/3
> -Original Message- > From: Tony Lindgren [mailto:t...@atomide.com] > Sent: Thursday, May 06, 2010 10:31 AM > To: Madhusudhan > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > linux-...@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > * Madhusudhan [100505 18:31]: > > > > > > > -Original Message- > > > From: Tony Lindgren [mailto:t...@atomide.com] > > > > > And what about this "Simulate multi mmc card as one big" patch? > > > > > Did not get you, what patch are you referring to? > > Oops sorry forgot the link: > > https://patchwork.kernel.org/patch/87944/ > This will not help. I don't know the history of the patch but what this is intended for is to support multiple MMC cards connected to a single controller. But on the Zoom the eMMC we are talking about is connected to MMC2. Regards, Madhu > Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Disable the non working eMMC on Zoom2/3
* Madhusudhan [100505 18:31]: > > > > -Original Message- > > From: Tony Lindgren [mailto:t...@atomide.com] > > > And what about this "Simulate multi mmc card as one big" patch? > > > Did not get you, what patch are you referring to? Oops sorry forgot the link: https://patchwork.kernel.org/patch/87944/ Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH] Disable the non working eMMC on Zoom2/3
> -Original Message- > From: Tony Lindgren [mailto:t...@atomide.com] > Sent: Wednesday, May 05, 2010 1:27 PM > To: Madhusudhan > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > linux-...@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > * Madhusudhan [100430 09:52]: > > > > > > > > > > > > > > > Hmm, finally got around looking into this again. Looks like the > mmc > > > > > > is now working on my zoom3 with the current Linus' tree at > commit > > > > > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something > that > > > > > > we had in omap-fixes fixed this. Or maybe some fix for > drivers/mmc? > > > > > > > > > > > > This is with the debug_ll patch applied: > > > > > > > > > > > > https://patchwork.kernel.org/patch/87532/ > > > > > > > > > > For the microSD card, turns out the card I used was flakey. So > > > > > that should explain some of the problems. I'm almost certain > > > > > I tried with two different cards earlier though. In any case, > > > > > let's assume the problem is only the eMMC. > > > > > > > > > Sorry, I did not get a complete picture. Your earlier email said > that > > > with > > > > Linus tree eMMC on your Zoom3 is working. Is that correct? > > > > > > Nope, now the microSD is working, eMMC is not working. > > > > > > > IMHO, an omap level fix can not solve the problem with eMMC because > as I > > > can > > > > see from the log you provided above that a 16G device is detected as > 1G. > > > > This is certainly due to the issue I mentioned earlier. > > > > > > OK > > > > This means that some production boards still have this issue with eMMC. > So > > my patch disables the support for MMC2 on zoom boards. Would you > consider > > that? > > But is it also broken on zoom2? > Yes. > And what about this "Simulate multi mmc card as one big" patch? > Did not get you, what patch are you referring to? Regards, Madhu > Regards, > > Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Disable the non working eMMC on Zoom2/3
* Madhusudhan [100430 09:52]: > > > > > > > > > > > Hmm, finally got around looking into this again. Looks like the mmc > > > > > is now working on my zoom3 with the current Linus' tree at commit > > > > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that > > > > > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? > > > > > > > > > > This is with the debug_ll patch applied: > > > > > > > > > > https://patchwork.kernel.org/patch/87532/ > > > > > > > > For the microSD card, turns out the card I used was flakey. So > > > > that should explain some of the problems. I'm almost certain > > > > I tried with two different cards earlier though. In any case, > > > > let's assume the problem is only the eMMC. > > > > > > > Sorry, I did not get a complete picture. Your earlier email said that > > with > > > Linus tree eMMC on your Zoom3 is working. Is that correct? > > > > Nope, now the microSD is working, eMMC is not working. > > > > > IMHO, an omap level fix can not solve the problem with eMMC because as I > > can > > > see from the log you provided above that a 16G device is detected as 1G. > > > This is certainly due to the issue I mentioned earlier. > > > > OK > > This means that some production boards still have this issue with eMMC. So > my patch disables the support for MMC2 on zoom boards. Would you consider > that? But is it also broken on zoom2? And what about this "Simulate multi mmc card as one big" patch? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH] Disable the non working eMMC on Zoom2/3
> > > > > > > Hmm, finally got around looking into this again. Looks like the mmc > > > > is now working on my zoom3 with the current Linus' tree at commit > > > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that > > > > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? > > > > > > > > This is with the debug_ll patch applied: > > > > > > > > https://patchwork.kernel.org/patch/87532/ > > > > > > For the microSD card, turns out the card I used was flakey. So > > > that should explain some of the problems. I'm almost certain > > > I tried with two different cards earlier though. In any case, > > > let's assume the problem is only the eMMC. > > > > > Sorry, I did not get a complete picture. Your earlier email said that > with > > Linus tree eMMC on your Zoom3 is working. Is that correct? > > Nope, now the microSD is working, eMMC is not working. > > > IMHO, an omap level fix can not solve the problem with eMMC because as I > can > > see from the log you provided above that a 16G device is detected as 1G. > > This is certainly due to the issue I mentioned earlier. > > OK This means that some production boards still have this issue with eMMC. So my patch disables the support for MMC2 on zoom boards. Would you consider that? Regards, Madhu > > Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Disable the non working eMMC on Zoom2/3
* Madhusudhan [100428 12:30]: > > > > -Original Message- > > From: Tony Lindgren [mailto:t...@atomide.com] > > Sent: Wednesday, April 28, 2010 2:23 PM > > To: Madhusudhan > > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > > linux-...@vger.kernel.org > > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > > > * Tony Lindgren [100427 11:16]: > > > * Madhusudhan [100408 10:07]: > > > > > > > > > > > > Tony, do you care to just look up the serial number of your board? > > > > > > > > > > Sorry for the delay in replying, I've been travelling for a few > > weeks > > > > > and been in meetings quite a bit. Anyways, it's a 1013037 REV A > > board, > > > > > which seems to be production in the table above. > > > > > > > > > > > > > That means we can not assume all production units have a working eMMC. > > > > Would you mind sharing your bootup log? When this device is detected > > > > something like below is a clear issue. > > > > > > > > mmcblk1: mmc1:0001 STM16G 1.00 GiB > > > > mmcblk1: p1 p2 > > > > For the eMMC I seem to have that: > > > > [0.978363] mmc1: new high speed MMC card at address 0001 > > [0.984344] mmcblk1: mmc1:0001 STM16G 1.00 GiB > > [0.989105] mmcblk1: unknown partition table > > ... > > > > zoom:~# fdisk -l /dev/mmcblk1 > > [ 120.306396] mmcblk1: retrying using single block read > > [ 120.503692] mmcblk1: retrying using single block read > > [ 120.683593] mmcblk1: error -110 transferring data, sector 2097144, nr > > 8, card status 0x900 > > [ 120.691894] end_request: I/O error, dev mmcblk1, sector 2097144 > > [ 120.872680] mmcblk1: error -110 transferring data, sector 2097145, nr > > 7, card status 0x900 > > ... > > > > > Hmm, finally got around looking into this again. Looks like the mmc > > > is now working on my zoom3 with the current Linus' tree at commit > > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that > > > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? > > > > > > This is with the debug_ll patch applied: > > > > > > https://patchwork.kernel.org/patch/87532/ > > > > For the microSD card, turns out the card I used was flakey. So > > that should explain some of the problems. I'm almost certain > > I tried with two different cards earlier though. In any case, > > let's assume the problem is only the eMMC. > > > Sorry, I did not get a complete picture. Your earlier email said that with > Linus tree eMMC on your Zoom3 is working. Is that correct? Nope, now the microSD is working, eMMC is not working. > IMHO, an omap level fix can not solve the problem with eMMC because as I can > see from the log you provided above that a 16G device is detected as 1G. > This is certainly due to the issue I mentioned earlier. OK Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH] Disable the non working eMMC on Zoom2/3
> -Original Message- > From: Tony Lindgren [mailto:t...@atomide.com] > Sent: Wednesday, April 28, 2010 2:23 PM > To: Madhusudhan > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > linux-...@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > * Tony Lindgren [100427 11:16]: > > * Madhusudhan [100408 10:07]: > > > > > > > > > > Tony, do you care to just look up the serial number of your board? > > > > > > > > Sorry for the delay in replying, I've been travelling for a few > weeks > > > > and been in meetings quite a bit. Anyways, it's a 1013037 REV A > board, > > > > which seems to be production in the table above. > > > > > > > > > > That means we can not assume all production units have a working eMMC. > > > Would you mind sharing your bootup log? When this device is detected > > > something like below is a clear issue. > > > > > > mmcblk1: mmc1:0001 STM16G 1.00 GiB > > > mmcblk1: p1 p2 > > For the eMMC I seem to have that: > > [0.978363] mmc1: new high speed MMC card at address 0001 > [0.984344] mmcblk1: mmc1:0001 STM16G 1.00 GiB > [0.989105] mmcblk1: unknown partition table > ... > > zoom:~# fdisk -l /dev/mmcblk1 > [ 120.306396] mmcblk1: retrying using single block read > [ 120.503692] mmcblk1: retrying using single block read > [ 120.683593] mmcblk1: error -110 transferring data, sector 2097144, nr > 8, card status 0x900 > [ 120.691894] end_request: I/O error, dev mmcblk1, sector 2097144 > [ 120.872680] mmcblk1: error -110 transferring data, sector 2097145, nr > 7, card status 0x900 > ... > > > Hmm, finally got around looking into this again. Looks like the mmc > > is now working on my zoom3 with the current Linus' tree at commit > > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that > > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? > > > > This is with the debug_ll patch applied: > > > > https://patchwork.kernel.org/patch/87532/ > > For the microSD card, turns out the card I used was flakey. So > that should explain some of the problems. I'm almost certain > I tried with two different cards earlier though. In any case, > let's assume the problem is only the eMMC. > Sorry, I did not get a complete picture. Your earlier email said that with Linus tree eMMC on your Zoom3 is working. Is that correct? IMHO, an omap level fix can not solve the problem with eMMC because as I can see from the log you provided above that a 16G device is detected as 1G. This is certainly due to the issue I mentioned earlier. Regards, Madhu > Regards, > > Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Disable the non working eMMC on Zoom2/3
* Tony Lindgren [100427 11:16]: > * Madhusudhan [100408 10:07]: > > > > > > > > Tony, do you care to just look up the serial number of your board? > > > > > > Sorry for the delay in replying, I've been travelling for a few weeks > > > and been in meetings quite a bit. Anyways, it's a 1013037 REV A board, > > > which seems to be production in the table above. > > > > > > > That means we can not assume all production units have a working eMMC. > > Would you mind sharing your bootup log? When this device is detected > > something like below is a clear issue. > > > > mmcblk1: mmc1:0001 STM16G 1.00 GiB > > mmcblk1: p1 p2 For the eMMC I seem to have that: [0.978363] mmc1: new high speed MMC card at address 0001 [0.984344] mmcblk1: mmc1:0001 STM16G 1.00 GiB [0.989105] mmcblk1: unknown partition table ... zoom:~# fdisk -l /dev/mmcblk1 [ 120.306396] mmcblk1: retrying using single block read [ 120.503692] mmcblk1: retrying using single block read [ 120.683593] mmcblk1: error -110 transferring data, sector 2097144, nr 8, card status 0x900 [ 120.691894] end_request: I/O error, dev mmcblk1, sector 2097144 [ 120.872680] mmcblk1: error -110 transferring data, sector 2097145, nr 7, card status 0x900 ... > Hmm, finally got around looking into this again. Looks like the mmc > is now working on my zoom3 with the current Linus' tree at commit > 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that > we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? > > This is with the debug_ll patch applied: > > https://patchwork.kernel.org/patch/87532/ For the microSD card, turns out the card I used was flakey. So that should explain some of the problems. I'm almost certain I tried with two different cards earlier though. In any case, let's assume the problem is only the eMMC. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Disable the non working eMMC on Zoom2/3
* Madhusudhan [100408 10:07]: > > > > > > Tony, do you care to just look up the serial number of your board? > > > > Sorry for the delay in replying, I've been travelling for a few weeks > > and been in meetings quite a bit. Anyways, it's a 1013037 REV A board, > > which seems to be production in the table above. > > > > That means we can not assume all production units have a working eMMC. > Would you mind sharing your bootup log? When this device is detected > something like below is a clear issue. > > mmcblk1: mmc1:0001 STM16G 1.00 GiB > mmcblk1: p1 p2 Hmm, finally got around looking into this again. Looks like the mmc is now working on my zoom3 with the current Linus' tree at commit 7c6bd2010fced38444c9fd658f4c6ce61bd185bf. So I guess something that we had in omap-fixes fixed this. Or maybe some fix for drivers/mmc? This is with the debug_ll patch applied: https://patchwork.kernel.org/patch/87532/ Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH] Disable the non working eMMC on Zoom2/3
> -Original Message- > From: Tony Lindgren [mailto:t...@atomide.com] > Sent: Wednesday, April 07, 2010 6:50 AM > To: Madhusudhan > Cc: 'Nishanth Menon'; 'Ghorai, Sukumar'; linux-omap@vger.kernel.org; > linux-...@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > * Madhusudhan [100401 15:54]: > > > > > > Ref [1] I believe tony has the brand new zoom board - I think your > > > assumption here might be flawed.. > > > > > > > Wait, I just looked up the serial number on the board. The one I was > using > > is a pilot version where this problem exists. > > > > I happen to get an other board which is production unit with ser # > 1013089 > > Rev B. The eMMC on this board has no issue. It reports the EXT_CSD Rev 2 > > which is correct and works fine. > > > > http://omappedia.org/wiki/Zoom_Resources > > > > There is a table here which could help. > > > > Tony, do you care to just look up the serial number of your board? > > Sorry for the delay in replying, I've been travelling for a few weeks > and been in meetings quite a bit. Anyways, it's a 1013037 REV A board, > which seems to be production in the table above. > That means we can not assume all production units have a working eMMC. Would you mind sharing your bootup log? When this device is detected something like below is a clear issue. mmcblk1: mmc1:0001 STM16G 1.00 GiB mmcblk1: p1 p2 Regards, Madhu > > But again there are several boards out there which could have this > > non-working eMMC. So what do we do?? It does not make sense to keep > > something enabled which does not work. > > There's arm kernel parameter for ATAG_REVISION that can be passed from > bootloader and then the board-*.c code can initialize things accordingly > based on the board revision. > > Regards, > > Tony > > > > > [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2 > > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Disable the non working eMMC on Zoom2/3
* Madhusudhan [100401 15:54]: > > Ref [1] I believe tony has the brand new zoom board - I think your > > assumption here might be flawed.. > > > > Wait, I just looked up the serial number on the board. The one I was using > is a pilot version where this problem exists. > > I happen to get an other board which is production unit with ser # 1013089 > Rev B. The eMMC on this board has no issue. It reports the EXT_CSD Rev 2 > which is correct and works fine. > > http://omappedia.org/wiki/Zoom_Resources > > There is a table here which could help. > > Tony, do you care to just look up the serial number of your board? Sorry for the delay in replying, I've been travelling for a few weeks and been in meetings quite a bit. Anyways, it's a 1013037 REV A board, which seems to be production in the table above. > But again there are several boards out there which could have this > non-working eMMC. So what do we do?? It does not make sense to keep > something enabled which does not work. There's arm kernel parameter for ATAG_REVISION that can be passed from bootloader and then the board-*.c code can initialize things accordingly based on the board revision. Regards, Tony > > [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2 > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH] Disable the non working eMMC on Zoom2/3
> -Original Message- > From: Nishanth Menon [mailto:n...@ti.com] > Sent: Thursday, April 01, 2010 4:59 PM > To: Ghorai, Sukumar > Cc: Chikkature Rajashekar, Madhusudhan; t...@atomide.com; linux- > o...@vger.kernel.org; linux-...@vger.kernel.org > Subject: Re: [PATCH] Disable the non working eMMC on Zoom2/3 > > Ghorai, Sukumar had written, on 04/01/2010 01:34 PM, the following: > > >>>> -Original Message- > >>>> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > >>>> ow...@vger.kernel.org] On Behalf Of Chikkature Rajashekar, > Madhusudhan > >>>> Sent: 2010-04-01 05:56 > >>>> To: t...@atomide.com > >>>> Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org > >>>> Subject: [PATCH] Disable the non working eMMC on Zoom2/3 > >>>> > >>>> From: Madhusudhan Chikkature > >>>> Date: Wed, 31 Mar 2010 12:29:19 -0400 > >>>> Subject: [PATCH] Zoom2/3: Disable MMC > >>>> > >>>> The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the > >>>> writes to fail since the card size is not detected correctly by the > >> MMC > >>>> core. Disable the MMC2 support for Zoom2/3. > >>> > >>> [Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the > >> exact > >>> problem. Because we never face any issue for eMMC in ZOOM3. Because we > >>> have the same eMMC device in 3630-SDP and could have the same problem. > >>> > >> On Zoom3 the EXT_CSD Rev reported by eMMC is zero. See the log > attached. > >> > >> Hence the failures which are reported by people on the list. I had > already > >> bought this problem up on the list previously and was discussed, right? > >> From the log you can also see that a 16GB device is detected as a 1GB. > > > > [Ghorai] I feel it's an issue with eMMC in pilot-board. And production- > board is working fine. And I feel outside TI people having production > board only. And 16GB eMMC device is a very good size to work with > different things. Otherwise we are talking about MMC#2 boot, eMMC boot, > 16GB eMMC device in zoom,.. all these information in different page/ link > looks very misleading information, if really having such problem. > > I the mean time I will check this in Pilot board too and think you > checked in pilot board only. > > > Ref [1] I believe tony has the brand new zoom board - I think your > assumption here might be flawed.. > Wait, I just looked up the serial number on the board. The one I was using is a pilot version where this problem exists. I happen to get an other board which is production unit with ser # 1013089 Rev B. The eMMC on this board has no issue. It reports the EXT_CSD Rev 2 which is correct and works fine. http://omappedia.org/wiki/Zoom_Resources There is a table here which could help. Tony, do you care to just look up the serial number of your board? But again there are several boards out there which could have this non-working eMMC. So what do we do?? It does not make sense to keep something enabled which does not work. Regards, Madhu > -- > Regards, > Nishanth Menon > Ref: > [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Disable the non working eMMC on Zoom2/3
Ghorai, Sukumar had written, on 04/01/2010 01:34 PM, the following: -Original Message- From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- ow...@vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan Sent: 2010-04-01 05:56 To: t...@atomide.com Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org Subject: [PATCH] Disable the non working eMMC on Zoom2/3 From: Madhusudhan Chikkature Date: Wed, 31 Mar 2010 12:29:19 -0400 Subject: [PATCH] Zoom2/3: Disable MMC The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the writes to fail since the card size is not detected correctly by the MMC core. Disable the MMC2 support for Zoom2/3. [Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the exact problem. Because we never face any issue for eMMC in ZOOM3. Because we have the same eMMC device in 3630-SDP and could have the same problem. On Zoom3 the EXT_CSD Rev reported by eMMC is zero. See the log attached. Hence the failures which are reported by people on the list. I had already bought this problem up on the list previously and was discussed, right? From the log you can also see that a 16GB device is detected as a 1GB. [Ghorai] I feel it's an issue with eMMC in pilot-board. And production-board is working fine. And I feel outside TI people having production board only. And 16GB eMMC device is a very good size to work with different things. Otherwise we are talking about MMC#2 boot, eMMC boot, 16GB eMMC device in zoom,.. all these information in different page/ link looks very misleading information, if really having such problem. I the mean time I will check this in Pilot board too and think you checked in pilot board only. Ref [1] I believe tony has the brand new zoom board - I think your assumption here might be flawed.. -- Regards, Nishanth Menon Ref: [1] http://marc.info/?l=linux-omap&m=126938456103707&w=2 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH] Disable the non working eMMC on Zoom2/3
Madhusudhan,
> -Original Message-
> From: Chikkature Rajashekar, Madhusudhan
> Sent: 2010-04-01 22:35
> To: Ghorai, Sukumar; t...@atomide.com
> Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org
> Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3
>
>
>
> > -Original Message-
> > From: Ghorai, Sukumar [mailto:s-gho...@ti.com]
> > Sent: Wednesday, March 31, 2010 11:03 PM
> > To: Chikkature Rajashekar, Madhusudhan; t...@atomide.com
> > Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org
> > Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3
> >
> > Madhu,
> >
> > > -Original Message-
> > > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> > > ow...@vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan
> > > Sent: 2010-04-01 05:56
> > > To: t...@atomide.com
> > > Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org
> > > Subject: [PATCH] Disable the non working eMMC on Zoom2/3
> > >
> > > From: Madhusudhan Chikkature
> > > Date: Wed, 31 Mar 2010 12:29:19 -0400
> > > Subject: [PATCH] Zoom2/3: Disable MMC
> > >
> > > The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the
> > > writes to fail since the card size is not detected correctly by the
> MMC
> > > core. Disable the MMC2 support for Zoom2/3.
> >
> >
> > [Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the
> exact
> > problem. Because we never face any issue for eMMC in ZOOM3. Because we
> > have the same eMMC device in 3630-SDP and could have the same problem.
> >
>
> On Zoom3 the EXT_CSD Rev reported by eMMC is zero. See the log attached.
>
> Hence the failures which are reported by people on the list. I had already
> bought this problem up on the list previously and was discussed, right?
> From the log you can also see that a 16GB device is detected as a 1GB.
[Ghorai] I feel it's an issue with eMMC in pilot-board. And production-board is
working fine. And I feel outside TI people having production board only. And
16GB eMMC device is a very good size to work with different things. Otherwise
we are talking about MMC#2 boot, eMMC boot, 16GB eMMC device in zoom,.. all
these information in different page/ link looks very misleading information, if
really having such problem.
I the mean time I will check this in Pilot board too and think you checked in
pilot board only.
>
> Regards,
> Madhu
>
> > >
> > > Signed-off-by: Madhusudhan Chikkature
> > > ---
> > > arch/arm/mach-omap2/board-zoom-peripherals.c | 30 -
> --
> > --
> > > -
> > > 1 files changed, 0 insertions(+), 30 deletions(-)
> > >
> > > diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c
> > > b/arch/arm/mach-omap2/board-zoom-peripherals.c
> > > index 6b39849..ac791d2 100644
> > > --- a/arch/arm/mach-omap2/board-zoom-peripherals.c
> > > +++ b/arch/arm/mach-omap2/board-zoom-peripherals.c
> > > @@ -102,10 +102,6 @@ static struct regulator_consumer_supply
> > > zoom_vsim_supply = {
> > > .supply = "vmmc_aux",
> > > };
> > >
> > > -static struct regulator_consumer_supply zoom_vmmc2_supply = {
> > > - .supply = "vmmc",
> > > -};
> > > -
> > > /* VMMC1 for OMAP VDD_MMC1 (i/o) and MMC1 card */
> > > static struct regulator_init_data zoom_vmmc1 = {
> > > .constraints = {
> > > @@ -121,21 +117,6 @@ static struct regulator_init_data zoom_vmmc1 = {
> > > .consumer_supplies = &zoom_vmmc1_supply,
> > > };
> > >
> > > -/* VMMC2 for MMC2 card */
> > > -static struct regulator_init_data zoom_vmmc2 = {
> > > - .constraints = {
> > > - .min_uV = 185,
> > > - .max_uV = 185,
> > > - .apply_uV = true,
> > > - .valid_modes_mask = REGULATOR_MODE_NORMAL
> > > - | REGULATOR_MODE_STANDBY,
> > > - .valid_ops_mask = REGULATOR_CHANGE_MODE
> > > - | REGULATOR_CHANGE_STATUS,
> > > - },
> > > - .num_consumer_supplies = 1,
> > > - .consumer_supplies = &zoom_vmmc2_supply,
> > > -};
> > > -
> > > /* VSIM for OMAP VDD_MMC1A (i/o for DAT4..DAT7) */
> > > static struct regulator_init_data zoom_vsim = {
> > > .constraints = {
>
RE: [PATCH] Disable the non working eMMC on Zoom2/3
> -Original Message-
> From: Ghorai, Sukumar [mailto:s-gho...@ti.com]
> Sent: Wednesday, March 31, 2010 11:03 PM
> To: Chikkature Rajashekar, Madhusudhan; t...@atomide.com
> Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org
> Subject: RE: [PATCH] Disable the non working eMMC on Zoom2/3
>
> Madhu,
>
> > -Original Message-
> > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> > ow...@vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan
> > Sent: 2010-04-01 05:56
> > To: t...@atomide.com
> > Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org
> > Subject: [PATCH] Disable the non working eMMC on Zoom2/3
> >
> > From: Madhusudhan Chikkature
> > Date: Wed, 31 Mar 2010 12:29:19 -0400
> > Subject: [PATCH] Zoom2/3: Disable MMC
> >
> > The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the
> > writes to fail since the card size is not detected correctly by the MMC
> > core. Disable the MMC2 support for Zoom2/3.
>
>
> [Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the exact
> problem. Because we never face any issue for eMMC in ZOOM3. Because we
> have the same eMMC device in 3630-SDP and could have the same problem.
>
On Zoom3 the EXT_CSD Rev reported by eMMC is zero. See the log attached.
Hence the failures which are reported by people on the list. I had already
bought this problem up on the list previously and was discussed, right?
>From the log you can also see that a 16GB device is detected as a 1GB.
Regards,
Madhu
> >
> > Signed-off-by: Madhusudhan Chikkature
> > ---
> > arch/arm/mach-omap2/board-zoom-peripherals.c | 30 ---
> --
> > -
> > 1 files changed, 0 insertions(+), 30 deletions(-)
> >
> > diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c
> > b/arch/arm/mach-omap2/board-zoom-peripherals.c
> > index 6b39849..ac791d2 100644
> > --- a/arch/arm/mach-omap2/board-zoom-peripherals.c
> > +++ b/arch/arm/mach-omap2/board-zoom-peripherals.c
> > @@ -102,10 +102,6 @@ static struct regulator_consumer_supply
> > zoom_vsim_supply = {
> > .supply = "vmmc_aux",
> > };
> >
> > -static struct regulator_consumer_supply zoom_vmmc2_supply = {
> > - .supply = "vmmc",
> > -};
> > -
> > /* VMMC1 for OMAP VDD_MMC1 (i/o) and MMC1 card */
> > static struct regulator_init_data zoom_vmmc1 = {
> > .constraints = {
> > @@ -121,21 +117,6 @@ static struct regulator_init_data zoom_vmmc1 = {
> > .consumer_supplies = &zoom_vmmc1_supply,
> > };
> >
> > -/* VMMC2 for MMC2 card */
> > -static struct regulator_init_data zoom_vmmc2 = {
> > - .constraints = {
> > - .min_uV = 185,
> > - .max_uV = 185,
> > - .apply_uV = true,
> > - .valid_modes_mask = REGULATOR_MODE_NORMAL
> > - | REGULATOR_MODE_STANDBY,
> > - .valid_ops_mask = REGULATOR_CHANGE_MODE
> > - | REGULATOR_CHANGE_STATUS,
> > - },
> > - .num_consumer_supplies = 1,
> > - .consumer_supplies = &zoom_vmmc2_supply,
> > -};
> > -
> > /* VSIM for OMAP VDD_MMC1A (i/o for DAT4..DAT7) */
> > static struct regulator_init_data zoom_vsim = {
> > .constraints = {
> > @@ -159,15 +140,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = {
> > .gpio_wp= -EINVAL,
> > .power_saving = true,
> > },
> > - {
> > - .name = "internal",
> > - .mmc= 2,
> > - .wires = 8,
> > - .gpio_cd= -EINVAL,
> > - .gpio_wp= -EINVAL,
> > - .nonremovable = true,
> > - .power_saving = true,
> > - },
> > {} /* Terminator */
> > };
> >
> > @@ -183,7 +155,6 @@ static int zoom_twl_gpio_setup(struct device *dev,
> > */
> > zoom_vmmc1_supply.dev = mmc[0].dev;
> > zoom_vsim_supply.dev = mmc[0].dev;
> > - zoom_vmmc2_supply.dev = mmc[1].dev;
> >
> > return 0;
> > }
> > @@ -241,7 +212,6 @@ static struct twl4030_platform_data zoom_twldata = {
> > .keypad = &zoom_kp_twl4030_data,
> > .codec = &zoom_codec_data,
> > .vmmc1 = &zoom_vmmc1,
> > - .vmmc2 = &zoom_vmmc2,
> > .vsim = &zoom
RE: [PATCH] Disable the non working eMMC on Zoom2/3
Madhu,
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Chikkature Rajashekar, Madhusudhan
> Sent: 2010-04-01 05:56
> To: t...@atomide.com
> Cc: linux-omap@vger.kernel.org; linux-...@vger.kernel.org
> Subject: [PATCH] Disable the non working eMMC on Zoom2/3
>
> From: Madhusudhan Chikkature
> Date: Wed, 31 Mar 2010 12:29:19 -0400
> Subject: [PATCH] Zoom2/3: Disable MMC
>
> The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the
> writes to fail since the card size is not detected correctly by the MMC
> core. Disable the MMC2 support for Zoom2/3.
[Ghorai] Please let us know the EXT_CSD Rev you see in zoom3 and the exact
problem. Because we never face any issue for eMMC in ZOOM3. Because we have the
same eMMC device in 3630-SDP and could have the same problem.
>
> Signed-off-by: Madhusudhan Chikkature
> ---
> arch/arm/mach-omap2/board-zoom-peripherals.c | 30 -
> -
> 1 files changed, 0 insertions(+), 30 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c
> b/arch/arm/mach-omap2/board-zoom-peripherals.c
> index 6b39849..ac791d2 100644
> --- a/arch/arm/mach-omap2/board-zoom-peripherals.c
> +++ b/arch/arm/mach-omap2/board-zoom-peripherals.c
> @@ -102,10 +102,6 @@ static struct regulator_consumer_supply
> zoom_vsim_supply = {
> .supply = "vmmc_aux",
> };
>
> -static struct regulator_consumer_supply zoom_vmmc2_supply = {
> - .supply = "vmmc",
> -};
> -
> /* VMMC1 for OMAP VDD_MMC1 (i/o) and MMC1 card */
> static struct regulator_init_data zoom_vmmc1 = {
> .constraints = {
> @@ -121,21 +117,6 @@ static struct regulator_init_data zoom_vmmc1 = {
> .consumer_supplies = &zoom_vmmc1_supply,
> };
>
> -/* VMMC2 for MMC2 card */
> -static struct regulator_init_data zoom_vmmc2 = {
> - .constraints = {
> - .min_uV = 185,
> - .max_uV = 185,
> - .apply_uV = true,
> - .valid_modes_mask = REGULATOR_MODE_NORMAL
> - | REGULATOR_MODE_STANDBY,
> - .valid_ops_mask = REGULATOR_CHANGE_MODE
> - | REGULATOR_CHANGE_STATUS,
> - },
> - .num_consumer_supplies = 1,
> - .consumer_supplies = &zoom_vmmc2_supply,
> -};
> -
> /* VSIM for OMAP VDD_MMC1A (i/o for DAT4..DAT7) */
> static struct regulator_init_data zoom_vsim = {
> .constraints = {
> @@ -159,15 +140,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = {
> .gpio_wp= -EINVAL,
> .power_saving = true,
> },
> - {
> - .name = "internal",
> - .mmc= 2,
> - .wires = 8,
> - .gpio_cd= -EINVAL,
> - .gpio_wp= -EINVAL,
> - .nonremovable = true,
> - .power_saving = true,
> - },
> {} /* Terminator */
> };
>
> @@ -183,7 +155,6 @@ static int zoom_twl_gpio_setup(struct device *dev,
> */
> zoom_vmmc1_supply.dev = mmc[0].dev;
> zoom_vsim_supply.dev = mmc[0].dev;
> - zoom_vmmc2_supply.dev = mmc[1].dev;
>
> return 0;
> }
> @@ -241,7 +212,6 @@ static struct twl4030_platform_data zoom_twldata = {
> .keypad = &zoom_kp_twl4030_data,
> .codec = &zoom_codec_data,
> .vmmc1 = &zoom_vmmc1,
> - .vmmc2 = &zoom_vmmc2,
> .vsim = &zoom_vsim,
>
> };
> --
> 1.6.3.3
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH] Disable the non working eMMC on Zoom2/3
From: Madhusudhan Chikkature
Date: Wed, 31 Mar 2010 12:29:19 -0400
Subject: [PATCH] Zoom2/3: Disable MMC2
The eMMC on Zoom2/3 seems to have a lower EXT_CSD Rev.This causes the
writes to fail since the card size is not detected correctly by the MMC
core. Disable the MMC2 support for Zoom2/3.
Signed-off-by: Madhusudhan Chikkature
---
arch/arm/mach-omap2/board-zoom-peripherals.c | 30 --
1 files changed, 0 insertions(+), 30 deletions(-)
diff --git a/arch/arm/mach-omap2/board-zoom-peripherals.c
b/arch/arm/mach-omap2/board-zoom-peripherals.c
index 6b39849..ac791d2 100644
--- a/arch/arm/mach-omap2/board-zoom-peripherals.c
+++ b/arch/arm/mach-omap2/board-zoom-peripherals.c
@@ -102,10 +102,6 @@ static struct regulator_consumer_supply zoom_vsim_supply =
{
.supply = "vmmc_aux",
};
-static struct regulator_consumer_supply zoom_vmmc2_supply = {
- .supply = "vmmc",
-};
-
/* VMMC1 for OMAP VDD_MMC1 (i/o) and MMC1 card */
static struct regulator_init_data zoom_vmmc1 = {
.constraints = {
@@ -121,21 +117,6 @@ static struct regulator_init_data zoom_vmmc1 = {
.consumer_supplies = &zoom_vmmc1_supply,
};
-/* VMMC2 for MMC2 card */
-static struct regulator_init_data zoom_vmmc2 = {
- .constraints = {
- .min_uV = 185,
- .max_uV = 185,
- .apply_uV = true,
- .valid_modes_mask = REGULATOR_MODE_NORMAL
- | REGULATOR_MODE_STANDBY,
- .valid_ops_mask = REGULATOR_CHANGE_MODE
- | REGULATOR_CHANGE_STATUS,
- },
- .num_consumer_supplies = 1,
- .consumer_supplies = &zoom_vmmc2_supply,
-};
-
/* VSIM for OMAP VDD_MMC1A (i/o for DAT4..DAT7) */
static struct regulator_init_data zoom_vsim = {
.constraints = {
@@ -159,15 +140,6 @@ static struct omap2_hsmmc_info mmc[] __initdata = {
.gpio_wp= -EINVAL,
.power_saving = true,
},
- {
- .name = "internal",
- .mmc= 2,
- .wires = 8,
- .gpio_cd= -EINVAL,
- .gpio_wp= -EINVAL,
- .nonremovable = true,
- .power_saving = true,
- },
{} /* Terminator */
};
@@ -183,7 +155,6 @@ static int zoom_twl_gpio_setup(struct device *dev,
*/
zoom_vmmc1_supply.dev = mmc[0].dev;
zoom_vsim_supply.dev = mmc[0].dev;
- zoom_vmmc2_supply.dev = mmc[1].dev;
return 0;
}
@@ -241,7 +212,6 @@ static struct twl4030_platform_data zoom_twldata = {
.keypad = &zoom_kp_twl4030_data,
.codec = &zoom_codec_data,
.vmmc1 = &zoom_vmmc1,
- .vmmc2 = &zoom_vmmc2,
.vsim = &zoom_vsim,
};
--
1.6.3.3
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
