devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Wang <frank.wang@rock-chips.com>
To: heiko@sntech.de, robh+dt@kernel.org, mark.rutland@arm.com,
	linux@armlinux.org.uk, wim@iguana.be, linux@roeck-us.net,
	ellisys@163.com
Cc: huangtao@rock-chips.com, devicetree@vger.kernel.org,
	charles.chen@rock-chips.com, wmc@rock-chips.com,
	kevan.lan@rock-chips.com, linux-kernel@vger.kernel.org,
	sugar.zhang@rock-chips.com, linux-rockchip@lists.infradead.org,
	Frank Wang <frank.wang@rock-chips.com>,
	cody.xie@rock-chips.com, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] arm: dts: rk322x: fix i2s1 pinctrl error
Date: Wed, 17 May 2017 17:52:24 +0800	[thread overview]
Message-ID: <1495014746-27621-2-git-send-email-frank.wang@rock-chips.com> (raw)
In-Reply-To: <1495014746-27621-1-git-send-email-frank.wang@rock-chips.com>

From: Sugar Zhang <sugar.zhang@rock-chips.com>

Refer to Chapter 5.3.2 of rk3229 TRM, we can see that GPIO1A[2,4,5]
using RK_FUNC_2 not RK_FUNC_1. This patch fixes it.

Signed-off-by: Sugar Zhang <sugar.zhang@rock-chips.com>
Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
---
 arch/arm/boot/dts/rk322x.dtsi | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/arch/arm/boot/dts/rk322x.dtsi b/arch/arm/boot/dts/rk322x.dtsi
index 48a0c1c..cc6a27d 100644
--- a/arch/arm/boot/dts/rk322x.dtsi
+++ b/arch/arm/boot/dts/rk322x.dtsi
@@ -621,9 +621,9 @@
 						<0 12 RK_FUNC_1 &pcfg_pull_none>,
 						<0 13 RK_FUNC_1 &pcfg_pull_none>,
 						<0 14 RK_FUNC_1 &pcfg_pull_none>,
-						<1 2 RK_FUNC_1 &pcfg_pull_none>,
-						<1 4 RK_FUNC_1 &pcfg_pull_none>,
-						<1 5 RK_FUNC_1 &pcfg_pull_none>;
+						<1 2 RK_FUNC_2 &pcfg_pull_none>,
+						<1 4 RK_FUNC_2 &pcfg_pull_none>,
+						<1 5 RK_FUNC_2 &pcfg_pull_none>;
 			};
 		};
 
-- 
2.0.0

  reply	other threads:[~2017-05-17  9:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17  9:52 [PATCH v2 0/3] add and fix some device node for rk322x SoC Frank Wang
2017-05-17  9:52 ` Frank Wang [this message]
2017-05-17 18:10   ` [PATCH v2 1/3] arm: dts: rk322x: fix i2s1 pinctrl error Heiko Stuebner
2017-05-17  9:52 ` [PATCH v2 2/3] arm: dts: rk322x: correct uart2 pinctrl and add another sets Frank Wang
     [not found]   ` <1495014746-27621-3-git-send-email-frank.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-05-17 18:26     ` Heiko Stuebner
2017-05-17  9:52 ` [PATCH v2 3/3] arm: dts: rk322x: add watchdog device node Frank Wang
2017-05-17 17:33   ` Heiko Stuebner

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=1495014746-27621-2-git-send-email-frank.wang@rock-chips.com \
    --to=frank.wang@rock-chips.com \
    --cc=charles.chen@rock-chips.com \
    --cc=cody.xie@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=ellisys@163.com \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=kevan.lan@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sugar.zhang@rock-chips.com \
    --cc=wim@iguana.be \
    --cc=wmc@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).