devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Caesar Wang <wxt@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, leozwang@google.com,
	keescook@google.com, Xing Zheng <zhengxing@rock-chips.com>
Subject: Re: [PATCH v1 1/6] ARM: dts: fix the correct pinctrl control for rk3036
Date: Fri, 18 Dec 2015 00:28:27 +0100	[thread overview]
Message-ID: <1838222.r8GKl7OzB9@diego> (raw)
In-Reply-To: <1450362112-8075-2-git-send-email-wxt@rock-chips.com>

Am Donnerstag, 17. Dezember 2015, 22:21:47 schrieb Caesar Wang:
> The pinctrl gpio pull up/down is incorrect since the rk3036 SoCs
> can't set the status in the internal.
> 
> We should keep the default status for enable the gpio status,
> In fact, the pull_none is the disable the gpio pull up/down.
> 
> Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
> Signed-off-by: Caesar Wang <wxt@rock-chips.com>

>From the signed-off-by's I guess this change was created by Xing (author), 
right?


Heiko

> ---
> 
>  arch/arm/boot/dts/rk3036.dtsi | 34 +++++++++++++++-------------------
>  1 file changed, 15 insertions(+), 19 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/rk3036.dtsi b/arch/arm/boot/dts/rk3036.dtsi
> index f8758bf..620e6e0 100644
> --- a/arch/arm/boot/dts/rk3036.dtsi
> +++ b/arch/arm/boot/dts/rk3036.dtsi
> @@ -427,12 +427,8 @@
>  			#interrupt-cells = <2>;
>  		};
> 
> -		pcfg_pull_up: pcfg-pull-up {
> -			bias-pull-up;
> -		};
> -
> -		pcfg_pull_down: pcfg-pull-down {
> -			bias-pull-down;
> +		pcfg_pull_default: pcfg_pull_default {
> +			bias-pull-pin-default;
>  		};
> 
>  		pcfg_pull_none: pcfg-pull-none {
> @@ -473,18 +469,18 @@
>  			};
> 
>  			emmc_cmd: emmc-cmd {
> -				rockchip,pins = <2 1 RK_FUNC_2 &pcfg_pull_none>;
> +				rockchip,pins = <2 1 RK_FUNC_2 &pcfg_pull_default>;
>  			};
> 
>  			emmc_bus8: emmc-bus8 {
> -				rockchip,pins = <1 24 RK_FUNC_2 &pcfg_pull_none>,
> -						<1 25 RK_FUNC_2 &pcfg_pull_none>,
> -						<1 26 RK_FUNC_2 &pcfg_pull_none>,
> -						<1 27 RK_FUNC_2 &pcfg_pull_none>,
> -						<1 28 RK_FUNC_2 &pcfg_pull_none>,
> -						<1 29 RK_FUNC_2 &pcfg_pull_none>,
> -						<1 30 RK_FUNC_2 &pcfg_pull_none>,
> -						<1 31 RK_FUNC_2 &pcfg_pull_none>;
> +				rockchip,pins = <1 24 RK_FUNC_2 &pcfg_pull_default>,
> +						<1 25 RK_FUNC_2 &pcfg_pull_default>,
> +						<1 26 RK_FUNC_2 &pcfg_pull_default>,
> +						<1 27 RK_FUNC_2 &pcfg_pull_default>,
> +						<1 28 RK_FUNC_2 &pcfg_pull_default>,
> +						<1 29 RK_FUNC_2 &pcfg_pull_default>,
> +						<1 30 RK_FUNC_2 &pcfg_pull_default>,
> +						<1 31 RK_FUNC_2 &pcfg_pull_default>;
>  			};
>  		};
> 
> @@ -522,12 +518,12 @@
> 
>  		uart0 {
>  			uart0_xfer: uart0-xfer {
> -				rockchip,pins = <0 16 RK_FUNC_1 &pcfg_pull_up>,
> +				rockchip,pins = <0 16 RK_FUNC_1 &pcfg_pull_default>,
>  						<0 17 RK_FUNC_1 &pcfg_pull_none>;
>  			};
> 
>  			uart0_cts: uart0-cts {
> -				rockchip,pins = <0 18 RK_FUNC_1 &pcfg_pull_up>;
> +				rockchip,pins = <0 18 RK_FUNC_1 &pcfg_pull_default>;
>  			};
> 
>  			uart0_rts: uart0-rts {
> @@ -537,7 +533,7 @@
> 
>  		uart1 {
>  			uart1_xfer: uart1-xfer {
> -				rockchip,pins = <2 22 RK_FUNC_1 &pcfg_pull_none>,
> +				rockchip,pins = <2 22 RK_FUNC_1 &pcfg_pull_default>,
>  						<2 23 RK_FUNC_1 &pcfg_pull_none>;
>  			};
>  			/* no rts / cts for uart1 */
> @@ -545,7 +541,7 @@
> 
>  		uart2 {
>  			uart2_xfer: uart2-xfer {
> -				rockchip,pins = <1 18 RK_FUNC_2 &pcfg_pull_none>,
> +				rockchip,pins = <1 18 RK_FUNC_2 &pcfg_pull_default>,
>  						<1 19 RK_FUNC_2 &pcfg_pull_none>;
>  			};
>  			/* no rts / cts for uart2 */

  reply	other threads:[~2015-12-17 23:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 14:21 [PATCH v1 0/6] Support the rk3036 Kylin board Caesar Wang
2015-12-17 14:21 ` [PATCH v1 1/6] ARM: dts: fix the correct pinctrl control for rk3036 Caesar Wang
2015-12-17 23:28   ` Heiko Stübner [this message]
2015-12-18  1:29     ` Caesar Wang
2015-12-17 14:21 ` [PATCH v1 2/6] ARM: dts: add the lcdc and hdmi node " Caesar Wang
2015-12-17 14:21 ` [PATCH v1 3/6] ARM: dts: add the sdio/sdmmc " Caesar Wang
2015-12-17 14:21 ` [PATCH v1 4/6] ARM: dts: rockchip: add the kylin board " Caesar Wang
2015-12-19  4:17   ` Rob Herring
2015-12-17 14:21 ` [PATCH v1 5/6] ARM: dts: add the sound codec for kylin board Caesar Wang
2015-12-17 23:33   ` Heiko Stübner
2015-12-17 14:21 ` [PATCH v1 6/6] ARM: dts: add the sdio node " Caesar Wang
     [not found] ` <CAGXu5jKEykL1+F=m2kk8E4qOKeUmc-jHnZ-fYpz1OS8oQ1Pgxg@mail.gmail.com>
     [not found]   ` <CAGXu5jKEykL1+F=m2kk8E4qOKeUmc-jHnZ-fYpz1OS8oQ1Pgxg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-12-17 23:48     ` [PATCH v1 0/6] Support the rk3036 Kylin board Heiko Stübner
     [not found] ` <1450362112-8075-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-12-19 17:16   ` Heiko Stübner
2015-12-20 12:49     ` Caesar Wang
     [not found]       ` <5676A3CA.6090205-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-20 14:44         ` Heiko Stübner

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=1838222.r8GKl7OzB9@diego \
    --to=heiko@sntech.de \
    --cc=devicetree@vger.kernel.org \
    --cc=keescook@google.com \
    --cc=leozwang@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=wxt@rock-chips.com \
    --cc=zhengxing@rock-chips.com \
    /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).