From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/8] dts: sun8i-h3: clarify uart1 pinmux definition name
Date: Thu, 8 Sep 2016 08:18:51 +0200 [thread overview]
Message-ID: <20160908061851.GB8913@lukather> (raw)
In-Reply-To: <1473235141-12768-3-git-send-email-jorik@kippendief.biz>
Hi,
On Wed, Sep 07, 2016 at 09:58:55AM +0200, jorik at kippendief.biz wrote:
> From: Jorik Jonker <jorik@kippendief.biz>
>
> Signed-off-by: Jorik Jonker <jorik@kippendief.biz>
Commit log?
> ---
> arch/arm/boot/dts/sun8i-h3-bananapi-m2-plus.dts | 2 +-
> arch/arm/boot/dts/sun8i-h3.dtsi | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/sun8i-h3-bananapi-m2-plus.dts b/arch/arm/boot/dts/sun8i-h3-bananapi-m2-plus.dts
> index 3779280..45f623b 100644
> --- a/arch/arm/boot/dts/sun8i-h3-bananapi-m2-plus.dts
> +++ b/arch/arm/boot/dts/sun8i-h3-bananapi-m2-plus.dts
> @@ -185,7 +185,7 @@
>
> &uart1 {
> pinctrl-names = "default";
> - pinctrl-0 = <&uart1_pins_a>;
> + pinctrl-0 = <&uart1_rts_cts_pins>;
> status = "okay";
> };
>
> diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm/boot/dts/sun8i-h3.dtsi
> index ee10004..933d42c 100644
> --- a/arch/arm/boot/dts/sun8i-h3.dtsi
> +++ b/arch/arm/boot/dts/sun8i-h3.dtsi
> @@ -367,7 +367,7 @@
> allwinner,pull = <SUN4I_PINCTRL_NO_PULL>;
> };
>
> - uart1_pins_a: uart1 at 0 {
> + uart1_rts_cts_pins: uart1_rts_cts {
> allwinner,pins = "PG6", "PG7", "PG8", "PG9";
I'd prefer to have one pinctrl node for RX/TX, and one for
RTS/CTS. That way, we don't have to duplicate the nodes for the boards
that want to enable only RX/TX
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160908/611da8dc/attachment.sig>
next prev parent reply other threads:[~2016-09-08 6:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 7:58 [PATCH v4 0/8] dts: sun8i-h3: complete UART I2C definitions for H3 jorik at kippendief.biz
2016-09-07 7:58 ` [PATCH v4 1/8] dts: sun8i-h3: drop _a and address suffix from uart0 pinmux jorik at kippendief.biz
2016-09-08 6:17 ` Maxime Ripard
2016-09-07 7:58 ` [PATCH v4 2/8] dts: sun8i-h3: clarify uart1 pinmux definition name jorik at kippendief.biz
2016-09-08 6:18 ` Maxime Ripard [this message]
2016-09-07 7:58 ` [PATCH v4 3/8] dts: sun8i-h3: move uart0 pinmux/peripheral assocation to DSTI jorik at kippendief.biz
2016-09-08 6:22 ` Maxime Ripard
2016-09-07 7:58 ` [PATCH v4 4/8] dts: sun8i-h3: move uart1 " jorik at kippendief.biz
2016-09-07 8:54 ` Chen-Yu Tsai
2016-09-08 6:23 ` Maxime Ripard
2016-09-08 8:02 ` Jorik Jonker
2016-09-08 9:01 ` Maxime Ripard
2016-09-08 9:51 ` Jorik Jonker
2016-09-12 9:47 ` Maxime Ripard
2016-09-07 7:58 ` [PATCH v4 5/8] dts: sun8i-h3: add pinmux definitions for UART2-3 jorik at kippendief.biz
2016-09-07 7:58 ` [PATCH v4 6/8] dts: sun8i-h3: associate pinmux/peripherals " jorik at kippendief.biz
2016-09-07 7:59 ` [PATCH v4 7/8] dts: sun8i-h3: add pinmux definitions for I2C0-2 jorik at kippendief.biz
2016-09-07 7:59 ` [PATCH v4 8/8] dts: sun8i-h3: add I2C0-2 peripherals to H3 SOC jorik at kippendief.biz
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=20160908061851.GB8913@lukather \
--to=maxime.ripard@free-electrons.com \
--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