On Friday 14 September 2012, Linus Walleij wrote: > On Fri, Sep 14, 2012 at 10:25 AM, Girish K S > <girish.shivananjappa@xxxxxxxxxx> wrote: > > On 14 September 2012 12:37, Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote: > >> Hi Girish, > >> > >> I should also have stated that this patch has not been tested with an > >> eMMC 4.5 device, thus the power off notification is not fully tested. > >> Unfortunate I don't have such a device available right now. What I did > >> test was that patch must not break anything and tested that the > >> suspend/resume sequence is fixed for eMMC with sleep support. I also > >> tested this with MMC_CAP2_POWEROFF_NOTIFY enabled. > >> > >> Are you able to help out in testing with a eMMC 4.5 device with > >> POWER_OFF_NOTIFY support? > > > > I am also facing the same problem. The board that i used earlier to > > upstream 4.5 patches is not functioning. Thats the reason for the > > delay in upstreaming or sending the patch. Once i get it repaired i ll > > definitely do it. > > It would be helpful if somebody in the list can do this in the mean time. > > Let's page Arnd, I was under the impression that he has a eMMC 4.5 > board so maybe he can test it? I have a few eMMC samples but am only using them with my (slow) thinkpad SD card reader. I also don't know which eMMC-4.5 features they implement, as some may be early prototypes. What exactly do you need tested? Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
