Re: Regression in v4.20 with omap_hsmmc GPIO CD and WP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Adam Ford <aford173@xxxxxxxxx> [181228 12:58]:
> On Fri, Dec 28, 2018 at 6:41 AM Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
> >
> > On Thu, Dec 27, 2018 at 7:50 PM Tony Lindgren <tony@xxxxxxxxxxx> wrote:
> >
> > > Looks like commit e63201f19438 ("mmc: omap_hsmmc: Delete platform data
> > > GPIO CD and WP") caused mmcblk0 to stop being detected on boot on some
> > > omaps. According to Aaro and Adam, mmcblk0 does get detected after
> > > replugging the SD card. Reverting the commit fixes the issue.
> >
> > Which boardfiles are we talking about, so I can have a look?
> > Or are these Device Tree devices?
> 
> I could confirm that logicpd-torpedo-37xx-devkit was fixed by
> reverting the GPIO code or removing the pdata quirks references to the
> pbias seem to fix the issue.  I haven't tried both together yet, nor
> have I had a chance to spend much time to fix the pbias driver to
> correctly disconnect the IO pins when used on an AM/DM36/37 board.
> For the Torpedo, I know the newer versions of the bootloader set the
> pbias and IO pins correctly now (it didn't used to do that).  I am
> hoping to look at the pbias driver this weekend if I have time.

Could it be that now n900 is fixed for the cover detection and
logicpd-torpedo-37xx-devkit has the GPIO direction configured
wrong in the dts?

Regards,

Tony



[Index of Archives]     [Linux Memonry Technology]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux