On Sat, Aug 23, 2014 at 10:56:37AM -0300, Fabio Estevam wrote: > On Sat, Aug 23, 2014 at 10:36 AM, Russell King - ARM Linux > <linux@xxxxxxxxxxxxxxxx> wrote: > > On Sat, Aug 23, 2014 at 10:32:23AM -0300, Fabio Estevam wrote: > >> On Sat, Aug 23, 2014 at 6:11 AM, Russell King > >> <rmk+kernel@xxxxxxxxxxxxxxxx> wrote: > >> > >> > - MX6QDL_PAD_GPIO_2__GPIO1_IO02 0x80000000 > >> > + MX6QDL_PAD_EIM_DA5__GPIO3_IO05 0x80000000 > >> > >> It would be better to replace the '0x80000000' with the real iomux > >> value (like 0x1b0b0 for example), so that we do not need to rely on > >> the bootloader doing the correct configuration for us. > > > > I'd just end up choosing something which appears to work - I've no idea > > at present what an appropriate value should be here. > > In the working system, you could read the register: > > IOMUXC_SW_PAD_CTL_PAD_EIM_AD05 (address: 0x20E043C) > > Most likely it will return the default value of 0xb0b1 if the > bootloader has not re-configured it. Most of the pins not associated with booting the kernel are left unconfigured by the boot loader - that's because uboot SPL has very little space for such things. Rabeeh has just told me that 0x1b0b1 would be a better value for it. I'll add an additional patch to the series for that, rather than modifying Rabeeh's original patch. -- FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up according to speedtest.net. -- 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
