From: lukma@denx.de (Łukasz Majewski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] dts: display5: Device tree description of LWN's DISPLAY5 board
Date: Wed, 20 Sep 2017 11:45:12 +0200 [thread overview]
Message-ID: <3537f09b-be9d-0b43-0bec-87d08b43312f@denx.de> (raw)
In-Reply-To: <CAOMZO5CHR14LWqkgpSiPnMV_6X+Fq=fe-KmE5CrdiqxRUyT8xg@mail.gmail.com>
Hi Fabio,
> Hi Lukasz,
>
> On Wed, Sep 20, 2017 at 6:22 AM, ?ukasz Majewski <lukma@denx.de> 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 at denx.de
prev parent reply other threads:[~2017-09-20 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 14:59 [PATCH 1/2] dts: display5: Device tree description of LWN's DISPLAY5 board Lukasz Majewski
2017-09-18 14:59 ` [PATCH 2/2] dts: Enable building of LWN's Display5 board Lukasz Majewski
2017-09-18 16:07 ` Fabio Estevam
2017-09-18 16:06 ` [PATCH 1/2] dts: display5: Device tree description of LWN's DISPLAY5 board Fabio Estevam
2017-09-20 9:22 ` Łukasz Majewski
2017-09-20 9:39 ` Fabio Estevam
2017-09-20 9:45 ` Łukasz Majewski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3537f09b-be9d-0b43-0bec-87d08b43312f@denx.de \
--to=lukma@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).