From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Jisheng Zhang <jszhang@marvell.com>,
linus.walleij@linaro.org, antoine.tenart@free-electrons.com,
catalin.marinas@arm.com, will.deacon@arm.com,
mark.rutland@arm.com, robh+dt@kernel.org, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] arm64: dts: berlin4ct: add the pinctrl node and muxing setup for uart0
Date: Sun, 20 Sep 2015 21:38:00 +0200 [thread overview]
Message-ID: <55FF0B18.5060505@gmail.com> (raw)
In-Reply-To: <1442656956-5740-6-git-send-email-jszhang@marvell.com>
On 19.09.2015 12:02, Jisheng Zhang wrote:
> Add the avio, soc, sm pinctrl nodes for Marvell berlin4ct SoC. This
> patch also adds urt0 txd and rxd muxing setup in the dtsi because uart0
> always use them to work, no other possibilities.
Please split the patch into two:
one adding the pinctrl nodes and
one adding the default pinmux to uart0 node.
> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> ---
> arch/arm64/boot/dts/marvell/berlin4ct.dtsi | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/marvell/berlin4ct.dtsi b/arch/arm64/boot/dts/marvell/berlin4ct.dtsi
> index a3b5f1d..4566e4e 100644
> --- a/arch/arm64/boot/dts/marvell/berlin4ct.dtsi
> +++ b/arch/arm64/boot/dts/marvell/berlin4ct.dtsi
> @@ -225,6 +225,16 @@
> };
> };
>
> + soc_pinctrl: pinctrl@ea8000 {
> + compatible = "marvell,berlin4ct-soc-pinctrl";
> + reg = <0xea8000 0x14>;
> + };
> +
> + avio_pinctrl: pinctrl@ea8400 {
> + compatible = "marvell,berlin4ct-avio-pinctrl";
> + reg = <0xea8400 8>;
s/8/0x8/
> + };
> +
> apb@fc0000 {
> compatible = "simple-bus";
> #address-cells = <1>;
> @@ -278,6 +288,23 @@
> clocks = <&osc>;
> reg-shift = <2>;
> status = "disabled";
> + pinctrl-0 = <&urt0_txd_pmux>, <&urt0_rxd_pmux>;
> + pinctrl-names = "default", "default";
pinctrl-names = "default", "default"; refers to pinctrl-0 and pinctrl-1
respectively. There is no pinctrl-1, so please remove the second
pinctrl-names element.
> + };
> + };
> +
> + sm_pinctrl: pinctrl@fe2200 {
> + compatible = "marvell,berlin4ct-sm-pinctrl";
> + reg = <0xfe2200 0xc>;
> +
> + urt0_txd_pmux: urt0_txd-pmux {
> + groups = "SM_URT0_TXD";
> + function = "sm_urt0_txd";
> + };
> +
> + urt0_rxd_pmux: urt0_rxd-pmux {
> + groups = "SM_URT0_RXD";
> + function = "sm_urt0_rxd";
If you change the driver to generic function names ("uart0") this
boils down to a single
uart0_pmux: uart0-pmux {
groups = "SM_UART0_TXD", "SM_UART0_RXD";
function = "uart0";
};
pinmux node and the reference in uart0 node to
pinctrl-0 = <&uart0_pmux>;
pinctrl-names = "default";
Sebastian
> };
> };
> };
>
prev parent reply other threads:[~2015-09-20 19:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 10:02 [PATCH 0/5] arm64: berlin: add pinctrl support Jisheng Zhang
2015-09-19 10:02 ` [PATCH 1/5] pinctrl: berlin: regmap as an extra argument of berlin_pinctrl_probe() Jisheng Zhang
2015-09-19 10:02 ` [PATCH 2/5] pinctrl: berlin: add the berlin4ct pinctrl driver Jisheng Zhang
2015-09-20 19:32 ` Sebastian Hesselbarth
[not found] ` <55FF09D5.6090707-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-09-21 7:27 ` Jisheng Zhang
2015-09-21 12:06 ` Jisheng Zhang
2015-09-19 10:02 ` [PATCH 3/5] arm64: berlin: add the pinctrl dependency for Marvell Berlin SoCs Jisheng Zhang
[not found] ` <1442656956-5740-1-git-send-email-jszhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
2015-09-19 10:02 ` [PATCH 4/5] pinctrl: dt-binding: document berlin4ct SoC Jisheng Zhang
2015-09-19 10:02 ` [PATCH 5/5] arm64: dts: berlin4ct: add the pinctrl node and muxing setup for uart0 Jisheng Zhang
2015-09-20 19:38 ` Sebastian Hesselbarth [this message]
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=55FF0B18.5060505@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=antoine.tenart@free-electrons.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jszhang@marvell.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.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).