Thread (1 message) 1 message, 1 author, 2014-08-23

Re: [PATCH 6/6] ARM: dts: hummingboard: gpio-ir on gpio 3,5

From: Fabio Estevam <hidden>
Date: 2014-08-23 13:56:37
Also in: linux-arm-kernel

On Sat, Aug 23, 2014 at 10:36 AM, Russell King - ARM Linux
[off-list ref] wrote:
On Sat, Aug 23, 2014 at 10:32:23AM -0300, Fabio Estevam wrote:
quoted
On Sat, Aug 23, 2014 at 6:11 AM, Russell King
[off-list ref] wrote:
quoted
-                               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.

,and then put this read value into the device tree. This way we
guarantee that the kernel will have this pin correctly configured,
without depending on the bootloader.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help