From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Gregory CLEMENT <gregory.clement@free-electrons.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Alexandre Courbot <gnurou@gmail.com>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Linus Walleij <linus.walleij@linaro.org>,
Omri Itach <omrii@marvell.com>,
linux-kernel@vger.kernel.org, Nadav Haklai <nadavh@marvell.com>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Neta Zur Hershkovits <neta@marvell.com>,
Kostya Porotchkin <kostap@marvell.com>,
Shadi Ammouri <shadi@marvell.com>,
Marcin Wojtas <mw@semihalf.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 5/6] gpio: mvebu: Add support for the Armada 7K/8K SoCs
Date: Fri, 19 May 2017 17:27:36 +0100 [thread overview]
Message-ID: <20170519162736.GU22219@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20170519162410.GT22219@n2100.armlinux.org.uk>
On Fri, May 19, 2017 at 05:24:10PM +0100, Russell King - ARM Linux wrote:
> On Fri, May 19, 2017 at 06:09:24PM +0200, Gregory CLEMENT wrote:
> > The Armada 7K and 8K SoCs use the same gpio controller as most of the
> > other mvebu SoCs. However, the main difference is that the GPIO
> > controller is part of a bigger system controller, and a syscon is used to
> > control the overall system controller. Therefore, the driver needs to be
> > adjusted to retrieve the regmap of the syscon to access registers, and
> > account for the fact that registers are located at a certain offset
> > within the regmap.
> >
> > This commit add the support of the syscon and introduce a new variant for
> > this case.
>
> Do you really need all this complexity of merging what seems to be two
> GPIO devices into one for DT purposes? The device itself appears to be
> two instances of the orion-gpio controller, one at 0x100 into the
> system controller and a second one at 0x140.
>
> If you instantiate two orion-gpio controllers, then you don't need to
> add the "mvchip->offset" stuff.
>
> I'd also say that it was the more correct approach, rather than adding
> more complexity to GPIO drivers to support whatever incarnation comes
> next.
Hmm, in fact, mvebu->offset always appears to be zero in this driver,
so I think the changes that add this member are entirely rendundant to
the function of this patch.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-05-19 16:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 16:09 [PATCH 0/6] Extend mvebu gpio driver to support the controllers of the Marvell Armada 7K/8K Gregory CLEMENT
2017-05-19 16:09 ` [PATCH 1/6] gpio: mvebu: sort header include Gregory CLEMENT
2017-05-23 9:15 ` Linus Walleij
2017-05-19 16:09 ` [PATCH 2/6] gpio: mvebu: switch to regmap for register access Gregory CLEMENT
2017-05-23 9:16 ` Linus Walleij
2017-05-19 16:09 ` [PATCH 3/6] gpio: dt-bindings: Add documentation for gpio controllers on Armada 7K/8K Gregory CLEMENT
2017-05-23 9:20 ` Linus Walleij
2017-05-23 13:06 ` Gregory CLEMENT
2017-05-29 8:08 ` Linus Walleij
2017-05-30 22:23 ` Rob Herring
2017-05-31 10:02 ` Gregory CLEMENT
2017-05-31 10:43 ` Michael Turquette
2017-05-31 14:41 ` Gregory CLEMENT
[not found] ` <306395ff39de3d3d3c8f55e5da4de8def29ae8d1.1495210061.git-series.gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2017-05-30 22:29 ` Rob Herring
2017-05-31 10:05 ` Gregory CLEMENT
2017-06-01 17:33 ` Gregory CLEMENT
2017-05-19 16:09 ` [PATCH 4/6] gpio: mvebu: allow building driver for " Gregory CLEMENT
2017-05-23 9:21 ` Linus Walleij
[not found] ` <cover.e10718b9c0f9fdd07327ae14e213be8da5b1f7ef.1495210061.git-series.gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2017-05-19 16:09 ` [PATCH 5/6] gpio: mvebu: Add support for the Armada 7K/8K SoCs Gregory CLEMENT
[not found] ` <54efbdfb0a9800b2c72c6fa1d945c87182b242b4.1495210061.git-series.gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2017-05-19 16:24 ` Russell King - ARM Linux
2017-05-19 16:27 ` Russell King - ARM Linux [this message]
[not found] ` <20170519162736.GU22219-l+eeeJia6m9URfEZ8mYm6t73F7V6hmMc@public.gmane.org>
2017-05-19 17:05 ` Thomas Petazzoni
2017-05-19 16:09 ` [PATCH 6/6] arm64: dts: marvell: add gpio support for Armada 7K/8K Gregory CLEMENT
2017-05-31 9:16 ` [PATCH 0/6] Extend mvebu gpio driver to support the controllers of the Marvell " Thomas Petazzoni
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=20170519162736.GU22219@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=kostap@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=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=neta@marvell.com \
--cc=omrii@marvell.com \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shadi@marvell.com \
--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).