linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: dts: i.MX51: Separate TXD/RXD and RTS/CTS pinmux entries for UARTs
Date: Mon, 26 Aug 2013 09:19:53 +0200	[thread overview]
Message-ID: <20130826071953.GG30088@pengutronix.de> (raw)
In-Reply-To: <1377070105-15902-1-git-send-email-shc_work@mail.ru>

On Wed, Aug 21, 2013 at 11:28:23AM +0400, Alexander Shiyan wrote:
> RTS/CTS pins can be used for different purposes, so create separate
> definitions for these pins.
> 
> Signed-off-by: Alexander Shiyan <shc_work@mail.ru>

This series looks good to me.

Acked-by: Sascha Hauer <s.hauer@pengutronix.de>

Sascha

> ---
>  arch/arm/boot/dts/imx51-babbage.dts |  4 ++--
>  arch/arm/boot/dts/imx51.dtsi        | 10 ++++++++++
>  2 files changed, 12 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/imx51-babbage.dts b/arch/arm/boot/dts/imx51-babbage.dts
> index 1d337d9..f13f339 100644
> --- a/arch/arm/boot/dts/imx51-babbage.dts
> +++ b/arch/arm/boot/dts/imx51-babbage.dts
> @@ -95,7 +95,7 @@
>  
>  &uart3 {
>  	pinctrl-names = "default";
> -	pinctrl-0 = <&pinctrl_uart3_1>;
> +	pinctrl-0 = <&pinctrl_uart3_1 &pinctrl_uart3_rtscts_1>;
>  	fsl,uart-has-rtscts;
>  	status = "okay";
>  };
> @@ -252,7 +252,7 @@
>  
>  &uart1 {
>  	pinctrl-names = "default";
> -	pinctrl-0 = <&pinctrl_uart1_1>;
> +	pinctrl-0 = <&pinctrl_uart1_1 &pinctrl_uart1_rtscts_1>;
>  	fsl,uart-has-rtscts;
>  	status = "okay";
>  };
> diff --git a/arch/arm/boot/dts/imx51.dtsi b/arch/arm/boot/dts/imx51.dtsi
> index a85abb4..b7cda0a 100644
> --- a/arch/arm/boot/dts/imx51.dtsi
> +++ b/arch/arm/boot/dts/imx51.dtsi
> @@ -747,6 +747,11 @@
>  			fsl,pins = <
>  				MX51_PAD_UART1_RXD__UART1_RXD 0x1c5
>  				MX51_PAD_UART1_TXD__UART1_TXD 0x1c5
> +			>;
> +		};
> +
> +		pinctrl_uart1_rtscts_1: uart1rtscts-1 {
> +			fsl,pins = <
>  				MX51_PAD_UART1_RTS__UART1_RTS 0x1c5
>  				MX51_PAD_UART1_CTS__UART1_CTS 0x1c5
>  			>;
> @@ -767,6 +772,11 @@
>  			fsl,pins = <
>  				MX51_PAD_EIM_D25__UART3_RXD 0x1c5
>  				MX51_PAD_EIM_D26__UART3_TXD 0x1c5
> +			>;
> +		};
> +
> +		pinctrl_uart3_rtscts_1: uart3rtscts-1 {
> +			fsl,pins = <
>  				MX51_PAD_EIM_D27__UART3_RTS 0x1c5
>  				MX51_PAD_EIM_D24__UART3_CTS 0x1c5
>  			>;
> -- 
> 1.8.1.5
> 
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  parent reply	other threads:[~2013-08-26  7:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21  7:28 [PATCH 1/3] ARM: dts: i.MX51: Separate TXD/RXD and RTS/CTS pinmux entries for UARTs Alexander Shiyan
2013-08-21  7:28 ` [PATCH 2/3] ARM: dts: i.MX51: Add IRAM devicetree node Alexander Shiyan
2013-08-21  7:28 ` [PATCH 3/3] ARM: dts: i.MX51: Add W1 " Alexander Shiyan
2013-08-26  7:19 ` Sascha Hauer [this message]
2013-08-29 11:19 ` [PATCH 1/3] ARM: dts: i.MX51: Separate TXD/RXD and RTS/CTS pinmux entries for UARTs Shawn Guo

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=20130826071953.GG30088@pengutronix.de \
    --to=s.hauer@pengutronix.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).