From: Frank Wang <frank.wang@rock-chips.com>
To: Kever Yang <ellisys@163.com>
Cc: heiko@sntech.de, robh+dt@kernel.org, mark.rutland@arm.com,
linux@armlinux.org.uk, 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, cody.xie@rock-chips.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] arm: dts: rk322x: correct uart2 pinctrl and add another sets
Date: Wed, 17 May 2017 15:35:42 +0800 [thread overview]
Message-ID: <eb0f4b99-4e9a-7af3-a341-146a692fe49a@rock-chips.com> (raw)
In-Reply-To: <3974d438-89ca-04e2-03cd-6d3946dd461e@163.com>
Hi Kever,
On 2017/5/17 14:31, Kever Yang wrote:
> Hi Frank,
>
>
> On 05/17/2017 11:40 AM, Frank Wang wrote:
>> Correct UART2 PINCTRL flag and add another PINCTRL sets for UART2
>> in case of confict with SDMMC.
>>
>> Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
>> ---
>> arch/arm/boot/dts/rk322x.dtsi | 11 +++++++++--
>> 1 file changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/rk322x.dtsi
>> b/arch/arm/boot/dts/rk322x.dtsi
>> index cc6a27d..ea1239a 100644
>> --- a/arch/arm/boot/dts/rk322x.dtsi
>> +++ b/arch/arm/boot/dts/rk322x.dtsi
>> @@ -222,7 +222,7 @@
>> clocks = <&cru SCLK_UART2>, <&cru PCLK_UART2>;
>> clock-names = "baudclk", "apb_pclk";
>> pinctrl-names = "default";
>> - pinctrl-0 = <&uart2_xfer>;
>> + pinctrl-0 = <&uart21_xfer>;
>
> There are more than one group of UART in rk322x, maybe we need to move
> or add this setting in the dts file to override dtsi setting?
>
That makes sense, I will delete above change in next version and
overwrite it in dts file later.
BR.
Frank
> Thanks,
> - Kever
>> reg-shift = <2>;
>> reg-io-width = <4>;
>> status = "disabled";
>> @@ -693,7 +693,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_up>,
>> <1 19 RK_FUNC_2 &pcfg_pull_none>;
>> };
>> @@ -705,5 +705,12 @@
>> rockchip,pins = <0 24 RK_FUNC_1 &pcfg_pull_none>;
>> };
>> };
>> +
>> + uart2-1 {
>> + uart21_xfer: uart21-xfer {
>> + rockchip,pins = <1 10 RK_FUNC_2 &pcfg_pull_up>,
>> + <1 9 RK_FUNC_2 &pcfg_pull_none>;
>> + };
>> + };
>> };
>> };
>
>
>
>
>
next prev parent reply other threads:[~2017-05-17 7:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 3:40 [PATCH 0/3] add and fix some device node for rk322x SoC Frank Wang
2017-05-17 3:40 ` [PATCH 1/3] arm: dts: rk322x: fix i2s1 pinctrl error Frank Wang
2017-05-17 9:01 ` Heiko Stübner
2017-05-17 9:21 ` Frank Wang
2017-05-17 3:40 ` [PATCH 2/3] arm: dts: rk322x: correct uart2 pinctrl and add another sets Frank Wang
2017-05-17 6:31 ` Kever Yang
2017-05-17 7:35 ` Frank Wang [this message]
2017-05-17 3:40 ` [PATCH 3/3] arm: dts: rk322x: add watchdog device node Frank Wang
2017-05-18 3:18 ` kbuild test robot
2017-05-18 3:58 ` Frank Wang
2017-05-18 7:18 ` 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=eb0f4b99-4e9a-7af3-a341-146a692fe49a@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=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sugar.zhang@rock-chips.com \
--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
all inboxes | Powered by JetHome®