From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx6ull: add UART5 input select register definition
Date: Wed, 18 Apr 2018 11:08:02 +0800 [thread overview]
Message-ID: <20180418030801.GP25429@dragon> (raw)
In-Reply-To: <0977332f-fb45-6d6d-8643-6efdce5d14a2@i2se.com>
On Mon, Apr 16, 2018 at 10:17:14AM +0200, Stefan Wahren wrote:
> >I'm okay with the second version of the patch, but i noticed that
> >at least UART5_RTS_B_SELECT_INPUT is also affected.
> >
> >The bits for the iMX6UL:
> >
> >000 CSI_DATA03_ALT8 ? Selecting Pad: CSI_DATA03 for Mode: ALT8
> >001 GPIO1_IO08_ALT8 ? Selecting Pad: GPIO1_IO08 for Mode: ALT8
> >010 GPIO1_IO09_ALT8 ? Selecting Pad: GPIO1_IO09 for Mode: ALT8
> >011 ENET1_RX_EN_ALT1 ? Selecting Pad: ENET1_RX_EN for Mode: ALT1
> >100 ENET1_TX_DATA0_ALT1 ? Selecting Pad: ENET1_TX_DATA0 for Mode: ALT1
> >101 CSI_DATA02_ALT8 ? Selecting Pad: CSI_DATA02 for Mode: ALT8
> >
> >But for the iMX6ULL:
> >
> >000 CSI_DATA03_ALT8 ? Selecting Pad: CSI_DATA03 for Mode: ALT8
> >001 GPIO1_IO08_ALT8 ? Selecting Pad: GPIO1_IO08 for Mode: ALT8
> >010 GPIO1_IO09_ALT8 ? Selecting Pad: GPIO1_IO09 for Mode: ALT8
> >011 UART1_CTS_B_ALT9 ? Selecting Pad: UART1_CTS_B for Mode: ALT9
> >100 UART1_RTS_B_ALT9 ? Selecting Pad: UART1_RTS_B for Mode: ALT9
> >101 ENET1_RX_EN_ALT1 ? Selecting Pad: ENET1_RX_EN for Mode: ALT1
> >110 ENET1_TX_DATA0_ALT1 ? Selecting Pad: ENET1_TX_DATA0 for Mode: ALT1
> >111 CSI_DATA02_ALT8 ? Selecting Pad: CSI_DATA02 for Mode: ALT8
> >
> >Comparing the datasheets isn't fun ...
> >
> >Should i provide a patch for this or is there a easier way to
> >figure out all the differences?
>
> gentle ping ...
You're welcomed to send a patch for that.
Shawn
next prev parent reply other threads:[~2018-04-18 3:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 22:24 [PATCH] ARM: dts: imx6ull: add UART5 input select register definition Greg Ungerer
2018-03-27 22:45 ` Fabio Estevam
2018-03-29 15:35 ` Stefan Wahren
2018-04-16 8:17 ` Stefan Wahren
2018-04-18 3:08 ` Shawn Guo [this message]
2018-03-28 6:47 ` Stefan Wahren
2018-03-28 14:19 ` Greg Ungerer
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=20180418030801.GP25429@dragon \
--to=shawnguo@kernel.org \
--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).