From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>,
linux-arm-kernel@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org,
Kalyan Kinthada <kalyan.kinthada@alliedtelesis.co.nz>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [PATCHv4 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC
Date: Fri, 13 Jan 2017 10:54:17 +0100 [thread overview]
Message-ID: <2fca7ac2-9a88-19b1-28c5-5192b9c4a2bc@gmail.com> (raw)
In-Reply-To: <20170113091222.7132-4-chris.packham@alliedtelesis.co.nz>
On 13.01.2017 10:12, Chris Packham wrote:
> From: Kalyan Kinthada <kalyan.kinthada@alliedtelesis.co.nz>
>
> This pinctrl driver supports the 98DX3236, 98DX3336 and 98DX4251 SoCs
> from Marvell.
>
> Signed-off-by: Kalyan Kinthada <kalyan.kinthada@alliedtelesis.co.nz>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> Acked-by: Rob Herring <robh@kernel.org>
> Acked-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> ---
>
> Notes:
> Changes in v2:
> - include sdio support for the 98DX4251
> Changes in v3:
> - None
> Changes in v4:
> - Correct some discrepencies between binding and driver.
Well, unfortunately I still see differences between the "gpio" in
the binding and "gpo" in the driver.
Please go back to that list I sent you yesterday and fix them all.
[...]
> diff --git a/Documentation/devicetree/bindings/pinctrl/marvell,armada-98dx3236-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/marvell,armada-98dx3236-pinctrl.txt
> new file mode 100644
> index 000000000000..b5bd23992fdf
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/marvell,armada-98dx3236-pinctrl.txt
> @@ -0,0 +1,46 @@
[...]
> +mpp6 6 gpio, sd0(clk), dev(a2)
e.g. this is "gpio" ...
[...]
> diff --git a/drivers/pinctrl/mvebu/pinctrl-armada-xp.c b/drivers/pinctrl/mvebu/pinctrl-armada-xp.c
> index e4ea71a9d985..9601d662c7f5 100644
> --- a/drivers/pinctrl/mvebu/pinctrl-armada-xp.c
> +++ b/drivers/pinctrl/mvebu/pinctrl-armada-xp.c
> @@ -49,6 +49,10 @@ enum armada_xp_variant {
[...]
> + MPP_MODE(6,
> + MPP_VAR_FUNCTION(0x0, "gpo", NULL, V_98DX3236_PLUS),
... but here it is "gpo".
Sebastian
next prev parent reply other threads:[~2017-01-13 9:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 9:12 [PATCHv4 0/5] Support for Marvell switches with integrated CPUs Chris Packham
2017-01-13 9:12 ` [PATCHv4 1/5] clk: mvebu: support for 98DX3236 SoC Chris Packham
2017-01-18 22:25 ` Rob Herring
2017-01-19 3:24 ` Chris Packham
[not found] ` <20170113091222.7132-2-chris.packham-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2017-01-21 0:48 ` Stephen Boyd
2017-01-23 7:53 ` Chris Packham
2017-01-23 23:53 ` Stephen Boyd
2017-01-13 9:12 ` [PATCHv4 2/5] arm: mvebu: support for SMP on 98DX3336 SoC Chris Packham
2017-01-19 0:47 ` Stephen Boyd
2017-01-19 3:23 ` Chris Packham
2017-01-13 9:12 ` [PATCHv4 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC Chris Packham
2017-01-13 9:54 ` Sebastian Hesselbarth [this message]
2017-01-14 7:50 ` Chris Packham
2017-01-19 21:12 ` Chris Packham
[not found] ` <66c205acea6046978bf17e6d8fc1959f-5g7mGxlPNYb6GjIOKuZY+ItlCAj8ZROq@public.gmane.org>
2017-01-19 23:19 ` Sebastian Hesselbarth
2017-01-19 23:36 ` Chris Packham
[not found] ` <20170113091222.7132-4-chris.packham-6g8wRflRTwXFdCa3tKVlE6U/zSkkHjvu@public.gmane.org>
2017-01-19 10:02 ` Russell King - ARM Linux
2017-01-19 21:10 ` Chris Packham
2017-01-23 8:18 ` Chris Packham
2017-01-26 14:11 ` Linus Walleij
2017-01-13 9:12 ` [PATCHv4 4/5] arm: mvebu: Add device tree for 98DX3236 SoCs Chris Packham
2017-01-13 9:12 ` [PATCHv4 5/5] arm: mvebu: Add device tree for db-dxbc2 and db-xc3-24g4xg boards Chris Packham
2017-01-26 15:17 ` [PATCHv4 0/5] Support for Marvell switches with integrated CPUs Gregory CLEMENT
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=2fca7ac2-9a88-19b1-28c5-5192b9c4a2bc@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=devicetree@vger.kernel.org \
--cc=kalyan.kinthada@alliedtelesis.co.nz \
--cc=ldewangan@nvidia.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=robh+dt@kernel.org \
--cc=thomas.petazzoni@free-electrons.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).