From: jszhang@marvell.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: dts: berlin4ct: enable all i2c nodes for the STB board
Date: Mon, 23 Nov 2015 16:17:13 +0800 [thread overview]
Message-ID: <20151123161713.509b3294@xhacker> (raw)
In-Reply-To: <5652CA62.50602@gmail.com>
On Mon, 23 Nov 2015 09:12:18 +0100
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> On 23.11.2015 03:49, Jisheng Zhang wrote:
> > On Fri, 20 Nov 2015 22:19:32 +0100
> > Sebastian Hesselbarth wrote:
> >> On 20.11.2015 10:47, Jisheng Zhang wrote:
> >>> Enable all i2c nodes for the Marvell berlin BG4CT STB board.
> >>>
> >>> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> >>> ---
> >>> arch/arm64/boot/dts/marvell/berlin4ct-stb.dts | 50 +++++++++++++++++++++++++++
> >>> 1 file changed, 50 insertions(+)
> >>>
> >>> diff --git a/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts b/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts
> >>> index 348c37e..9e8e2e0 100644
> >>> --- a/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts
> >>> +++ b/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts
> >>> @@ -61,6 +61,56 @@
> >>> };
> >>> };
> >>>
> >>> +&avio_pinctrl {
> >>> + twsi1_pmux: twsi1-pmux {
> >>> + groups = "TX_EDDC_SCL", "TX_EDDC_SDA";
> >>> + function = "tx_eddc";
> >>> + };
> >>
> >> Please keep the pinmux sub-nodes in the SoC dtsi as long
> >> as they are not strictly board specific, i.e. gpios.
> >
> > Hmm, seems all boards configure this pin for EDDC usage, so it's fine
> > to move to soc
> >
> >>
> >>> +};
> >>> +
> >>> +&i2c0 {
> >>> + status = "okay";
> >>> + pinctrl-0 = <&twsi0_pmux>;
> >>> + pinctrl-names = "default";
> >>
> >> If there is only one (or a default) pinctrl-0 option for i2c0,
> >> you can also move it to the SoC dtsi.
> >
> > Some board may not use i2c0, i2c2, i2c3 host and use the pin as gpio for other
> > purpose. Considering the above twsi1_pmux usage, what's the better solution?
> > move twsi1_pmux to soc's dtsi and leave i2c0, i2c2, i2c3 pinctrl in board dts?
>
> If some boards don't use i2cN, they do not enable the node in their
> board dts. That is sufficient to not configure the pinmux as it will
> only be set if a driver is loaded for that node.
>
> If there is only one or two different pinmux settings for a specific
> function _always_ move the pinmux setting into SoC dtsi. If there is
> a well known default out of two or more possible settings, we may also
> have that pinmux as a default in the i2c node and only overwrite it
> when we have a board that uses a different setting.
Got it. Thanks for the detailed explanations.
>
> So, for i2c: Move all pinctrl/pinctrl-names properties to the SoC
> dtsi.
Will do in v2 when clk stuff is accepted.
Thanks,
Jisheng
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
To: Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
pawel.moll-5wv7dgnIgG8@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
catalin.marinas-5wv7dgnIgG8@public.gmane.org,
will.deacon-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/2] arm64: dts: berlin4ct: enable all i2c nodes for the STB board
Date: Mon, 23 Nov 2015 16:17:13 +0800 [thread overview]
Message-ID: <20151123161713.509b3294@xhacker> (raw)
In-Reply-To: <5652CA62.50602-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Mon, 23 Nov 2015 09:12:18 +0100
Sebastian Hesselbarth <sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On 23.11.2015 03:49, Jisheng Zhang wrote:
> > On Fri, 20 Nov 2015 22:19:32 +0100
> > Sebastian Hesselbarth wrote:
> >> On 20.11.2015 10:47, Jisheng Zhang wrote:
> >>> Enable all i2c nodes for the Marvell berlin BG4CT STB board.
> >>>
> >>> Signed-off-by: Jisheng Zhang <jszhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
> >>> ---
> >>> arch/arm64/boot/dts/marvell/berlin4ct-stb.dts | 50 +++++++++++++++++++++++++++
> >>> 1 file changed, 50 insertions(+)
> >>>
> >>> diff --git a/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts b/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts
> >>> index 348c37e..9e8e2e0 100644
> >>> --- a/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts
> >>> +++ b/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts
> >>> @@ -61,6 +61,56 @@
> >>> };
> >>> };
> >>>
> >>> +&avio_pinctrl {
> >>> + twsi1_pmux: twsi1-pmux {
> >>> + groups = "TX_EDDC_SCL", "TX_EDDC_SDA";
> >>> + function = "tx_eddc";
> >>> + };
> >>
> >> Please keep the pinmux sub-nodes in the SoC dtsi as long
> >> as they are not strictly board specific, i.e. gpios.
> >
> > Hmm, seems all boards configure this pin for EDDC usage, so it's fine
> > to move to soc
> >
> >>
> >>> +};
> >>> +
> >>> +&i2c0 {
> >>> + status = "okay";
> >>> + pinctrl-0 = <&twsi0_pmux>;
> >>> + pinctrl-names = "default";
> >>
> >> If there is only one (or a default) pinctrl-0 option for i2c0,
> >> you can also move it to the SoC dtsi.
> >
> > Some board may not use i2c0, i2c2, i2c3 host and use the pin as gpio for other
> > purpose. Considering the above twsi1_pmux usage, what's the better solution?
> > move twsi1_pmux to soc's dtsi and leave i2c0, i2c2, i2c3 pinctrl in board dts?
>
> If some boards don't use i2cN, they do not enable the node in their
> board dts. That is sufficient to not configure the pinmux as it will
> only be set if a driver is loaded for that node.
>
> If there is only one or two different pinmux settings for a specific
> function _always_ move the pinmux setting into SoC dtsi. If there is
> a well known default out of two or more possible settings, we may also
> have that pinmux as a default in the i2c node and only overwrite it
> when we have a board that uses a different setting.
Got it. Thanks for the detailed explanations.
>
> So, for i2c: Move all pinctrl/pinctrl-names properties to the SoC
> dtsi.
Will do in v2 when clk stuff is accepted.
Thanks,
Jisheng
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@marvell.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: <robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: dts: berlin4ct: enable all i2c nodes for the STB board
Date: Mon, 23 Nov 2015 16:17:13 +0800 [thread overview]
Message-ID: <20151123161713.509b3294@xhacker> (raw)
In-Reply-To: <5652CA62.50602@gmail.com>
On Mon, 23 Nov 2015 09:12:18 +0100
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> On 23.11.2015 03:49, Jisheng Zhang wrote:
> > On Fri, 20 Nov 2015 22:19:32 +0100
> > Sebastian Hesselbarth wrote:
> >> On 20.11.2015 10:47, Jisheng Zhang wrote:
> >>> Enable all i2c nodes for the Marvell berlin BG4CT STB board.
> >>>
> >>> Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> >>> ---
> >>> arch/arm64/boot/dts/marvell/berlin4ct-stb.dts | 50 +++++++++++++++++++++++++++
> >>> 1 file changed, 50 insertions(+)
> >>>
> >>> diff --git a/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts b/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts
> >>> index 348c37e..9e8e2e0 100644
> >>> --- a/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts
> >>> +++ b/arch/arm64/boot/dts/marvell/berlin4ct-stb.dts
> >>> @@ -61,6 +61,56 @@
> >>> };
> >>> };
> >>>
> >>> +&avio_pinctrl {
> >>> + twsi1_pmux: twsi1-pmux {
> >>> + groups = "TX_EDDC_SCL", "TX_EDDC_SDA";
> >>> + function = "tx_eddc";
> >>> + };
> >>
> >> Please keep the pinmux sub-nodes in the SoC dtsi as long
> >> as they are not strictly board specific, i.e. gpios.
> >
> > Hmm, seems all boards configure this pin for EDDC usage, so it's fine
> > to move to soc
> >
> >>
> >>> +};
> >>> +
> >>> +&i2c0 {
> >>> + status = "okay";
> >>> + pinctrl-0 = <&twsi0_pmux>;
> >>> + pinctrl-names = "default";
> >>
> >> If there is only one (or a default) pinctrl-0 option for i2c0,
> >> you can also move it to the SoC dtsi.
> >
> > Some board may not use i2c0, i2c2, i2c3 host and use the pin as gpio for other
> > purpose. Considering the above twsi1_pmux usage, what's the better solution?
> > move twsi1_pmux to soc's dtsi and leave i2c0, i2c2, i2c3 pinctrl in board dts?
>
> If some boards don't use i2cN, they do not enable the node in their
> board dts. That is sufficient to not configure the pinmux as it will
> only be set if a driver is loaded for that node.
>
> If there is only one or two different pinmux settings for a specific
> function _always_ move the pinmux setting into SoC dtsi. If there is
> a well known default out of two or more possible settings, we may also
> have that pinmux as a default in the i2c node and only overwrite it
> when we have a board that uses a different setting.
Got it. Thanks for the detailed explanations.
>
> So, for i2c: Move all pinctrl/pinctrl-names properties to the SoC
> dtsi.
Will do in v2 when clk stuff is accepted.
Thanks,
Jisheng
next prev parent reply other threads:[~2015-11-23 8:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 9:46 [PATCH 0/2] Add I2C support for Marvell Berlin BG4CT Jisheng Zhang
2015-11-20 9:46 ` Jisheng Zhang
2015-11-20 9:46 ` Jisheng Zhang
2015-11-20 9:47 ` [PATCH 1/2] arm64: dts: berlin4ct: add I2C nodes for BG4CT Jisheng Zhang
2015-11-20 9:47 ` Jisheng Zhang
2015-11-20 9:47 ` Jisheng Zhang
2015-11-20 21:21 ` Sebastian Hesselbarth
2015-11-20 21:21 ` Sebastian Hesselbarth
2015-11-23 2:43 ` Jisheng Zhang
2015-11-23 2:43 ` Jisheng Zhang
2015-11-23 2:43 ` Jisheng Zhang
2015-11-20 9:47 ` [PATCH 2/2] arm64: dts: berlin4ct: enable all i2c nodes for the STB board Jisheng Zhang
2015-11-20 9:47 ` Jisheng Zhang
2015-11-20 9:47 ` Jisheng Zhang
2015-11-20 21:19 ` Sebastian Hesselbarth
2015-11-20 21:19 ` Sebastian Hesselbarth
2015-11-23 2:49 ` Jisheng Zhang
2015-11-23 2:49 ` Jisheng Zhang
2015-11-23 2:49 ` Jisheng Zhang
2015-11-23 8:12 ` Sebastian Hesselbarth
2015-11-23 8:12 ` Sebastian Hesselbarth
2015-11-23 8:12 ` Sebastian Hesselbarth
2015-11-23 8:17 ` Jisheng Zhang [this message]
2015-11-23 8:17 ` Jisheng Zhang
2015-11-23 8:17 ` Jisheng Zhang
2015-11-20 9:51 ` [PATCH 0/2] Add I2C support for Marvell Berlin BG4CT Jisheng Zhang
2015-11-20 9:51 ` Jisheng Zhang
2015-11-20 9:51 ` Jisheng Zhang
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=20151123161713.509b3294@xhacker \
--to=jszhang@marvell.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.