Hi Fabio,
Hi Lukasz,
On Wed, Sep 20, 2017 at 6:22 AM, Łukasz Majewski <lukma@xxxxxxx> wrote:
Could you be more specific here?
The 0x80000000 corresponds to IMX_NO_PAD_CTL in pinctrl-imx.c, which
prevents from manual GPIO control.
The 0x80000000 value is the IOMUXC_SW_PAD_CTL_PAD_CSI0_DATA11 (0x020E_0654)
config data (16 bits only -> 0x0).
Writing 0x0 to this register is perfectly fine for my application.
I'm a bit in doubt to what I shall do more?
As per the Reference Manual, the POR reset for
IOMUXC_SW_PAD_CTL_PAD_CSI0_DATA11 is 0x1b0b0.
0x80000000 tells the kernel to not touch this IOMUX and use whatever
value comes from the bootloader.
If your bootloader does not touch this register, then you probably
read 0x1b0b0 from it.
In this case, please do this instead:
MX6QDL_PAD_CSI0_DAT11__GPIO5_IO29 0x1b0b0
Ok. Thanks for explanation :-)
--
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@xxxxxxx
--
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
