[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbT94HqVroM_0gSJJ8Q2+YaKXLwjFGMn+4SCa_PYiF19Q@mail.gmail.com>
Date: Thu, 24 Apr 2014 14:52:20 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Antoine Ténart <antoine.tenart@...e-electrons.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
Cc: Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
zhiming Xu <zmxu@...vell.com>,
Jisheng Zhang <jszhang@...vell.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/7] ARM: berlin: add pinctrl support
On Wed, Apr 23, 2014 at 5:51 PM, Antoine Ténart
<antoine.tenart@...e-electrons.com> wrote:
> This series adds support for the Marvell Berlin pin-controller, allowing
> to configure the pin muxing from the device tree.
>
> The Berlin pin-controller support is divided into 3 drivers, each
> driving one Berlin SoC. These drivers use a Berlin common part.
>
> This series applies on top of patches introducing the Marvell Berlin
> BG2Q you can find on Sebastian's berlin/for-next branch[1] and the patch
> allowing not to define the get_group_pins() function[2].
>
> Tested on the Berlin BG2Q.
So now I need some advice from the mvebu pinctrl maintainers
(Thomas, Sebastian etc):
- Is this a totally different pin controller so that drivers/pinctrl/mvebu
can not be used?
- Really?
- OK can you help me review this thing?
- Should the base folder really be named "berlin" or is this going to
be part of a bigger family of pin controllers so a more neutral name
should be sought?
- Why do hardware engineers seek to reinvent wheels like pin
controllers, GPIO and DMA engines all the time :-/
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists