* Dave Gerlach <d-gerlach@xxxxxx> [140422 12:53]: > On 04/22/2014 02:01 PM, Tony Lindgren wrote: > >* Dave Gerlach <d-gerlach@xxxxxx> [140422 11:52]: > >>This patch, along with patch here [1], fixes boot for am437x-gp-evm. The > >>bootloader configures gpio5_7 to control the DDR3 termination regulator, > >>the linked patch prevents that gpio bank from being reset and losing > >>the previously configured state, and this patch binds the gpio to a > >>regulator so the kernel is aware of the state of the gpio. > >> > >>[1] https://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg102941.html > > > >Setting up the GPIO regulator makes sense to me. But the hack in the > >link above is potentially a nasty time bomb for anybody trying to > >use GPIO bank 5 on that board. > > > >What tests have been done that the GPIO bank behaves properly when > >it's not reset? > > We've been using this configuration on this board for a while without any > apparent issues. Also, am335x-evmsk already uses the same idea for the VTT > regulator on board from commit 6046adb6ad701026c10adeac8d6a4138895f12e5 > [ARM: dts: am335x-evmsk: Do not reset gpio0] and I am unaware of any issues > with that either. OK. Do you have other GPIOs in use as interrupts for devices in these banks and do they work fine? Also, can you please test to make sure this works with the most recent Javier's GPIO patches that had the issue of not booting on am335x-evmsk? Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
