On Wed, Apr 23, 2014 at 5:51 PM, Antoine Ténart <antoine.ten...@free-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 majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
