From: Anson Huang <Anson.Huang@nxp.com>
To: robh+dt@kernel.org, mark.rutland@arm.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, u.kleine-koenig@pengutronix.de
Cc: Linux-imx@nxp.com
Subject: [PATCH V2 0/7] Add missing UART DCE/DTE pins macro defines
Date: Sat, 15 Feb 2020 13:15:51 +0800 [thread overview]
Message-ID: <1581743758-4475-1-git-send-email-Anson.Huang@nxp.com> (raw)
The patch set is to add missing UART DCE/DTE pins, because of previous
UART pins macro defines do NOT contain DCE/DTE, per the advice from
Uwe in V1 patch comment, to better distinguish the DCE/DTE functions,
I change the existing UART pins to contain the DCE/DTE, then add the
missing UART pins, meanwhile, keep the old macro definis there for some time
in order to make it backward compatible, and then, switch the existing
consumer DTs to use new UART pins macro defines with DCE/DTE inside.
As the changes in V2 is significant compared to V1, so I did NOT put
a change log in each patch, you can treat each patch as new patch, thanks.
Anson Huang (7):
ARM: dts: imx6sx: Improve UART pins macro defines
ARM: dts: imx6sx: Add missing UART RTS/CTS pins mux
ARM: dts: imx6sx-nitrogen6sx: Use new pin names with DCE/DTE for UART
pins
ARM: dts: imx6sx-sabreauto: Use new pin names with DCE/DTE for UART
pins
ARM: dts: imx6sx-sdb: Use new pin names with DCE/DTE for UART pins
ARM: dts: imx6sx-softing-vining-2000: Use new pin names with DCE/DTE
for UART pins
ARM: dts: imx6sx-udoo-neo: Use new pin names with DCE/DTE for UART
pins
arch/arm/boot/dts/imx6sx-nitrogen6sx.dts | 20 +-
arch/arm/boot/dts/imx6sx-pinfunc.h | 288 ++++++++++++++++-------
arch/arm/boot/dts/imx6sx-sabreauto.dts | 4 +-
arch/arm/boot/dts/imx6sx-sdb.dtsi | 12 +-
arch/arm/boot/dts/imx6sx-softing-vining-2000.dts | 8 +-
arch/arm/boot/dts/imx6sx-udoo-neo.dtsi | 28 +--
6 files changed, 237 insertions(+), 123 deletions(-)
--
2.7.4
next reply other threads:[~2020-02-15 5:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 5:15 Anson Huang [this message]
2020-02-15 5:15 ` [PATCH V2 1/7] ARM: dts: imx6sx: Improve UART pins macro defines Anson Huang
2020-02-17 8:23 ` Uwe Kleine-König
2020-02-15 5:15 ` [PATCH V2 2/7] ARM: dts: imx6sx: Add missing UART RTS/CTS pins mux Anson Huang
2020-02-17 8:26 ` Uwe Kleine-König
2020-02-15 5:15 ` [PATCH V2 3/7] ARM: dts: imx6sx-nitrogen6sx: Use new pin names with DCE/DTE for UART pins Anson Huang
2020-02-17 8:35 ` Uwe Kleine-König
2020-02-15 5:15 ` [PATCH V2 4/7] ARM: dts: imx6sx-sabreauto: " Anson Huang
2020-02-17 8:35 ` Uwe Kleine-König
2020-02-15 5:15 ` [PATCH V2 5/7] ARM: dts: imx6sx-sdb: " Anson Huang
2020-02-17 8:36 ` Uwe Kleine-König
2020-02-15 5:15 ` [PATCH V2 6/7] ARM: dts: imx6sx-softing-vining-2000: " Anson Huang
2020-02-17 8:37 ` Uwe Kleine-König
2020-02-15 5:15 ` [PATCH V2 7/7] ARM: dts: imx6sx-udoo-neo: " Anson Huang
2020-02-17 8:38 ` Uwe Kleine-König
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=1581743758-4475-1-git-send-email-Anson.Huang@nxp.com \
--to=anson.huang@nxp.com \
--cc=Linux-imx@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).