linux-toradex.git/drivers/pinctrl/mvebu/Makefile, branch v4.10

pinctrl: mvebu: guard sub-directory with CONFIG_PINCTRL_MVEBU

2015-12-01T09:41:03+00:00

CONFIG_PINCTRL_MVEBU is more suitable than CONFIG_PLAT_ORION
to guard the drivers/pinctrl/mvebu/ directory.

Signed-off-by: Masahiro Yamada 
Signed-off-by: Linus Walleij

pinctrl: mvebu: add pinctrl driver for Marvell Armada 39x

2015-03-04T12:53:55+00:00

This commit adds a new pinctrl driver for the Marvell Armada 39x
family of processors, which hooks into the existing infrastructure to
support pin-muxing on Marvell EBU processors. Two variants of the
Armada 39x are supported: 88F6920 (Armada 390) and 88F6928 (Armada
398), which have a few differences in the available functions for
certain pins.

Signed-off-by: Thomas Petazzoni 
Signed-off-by: Linus Walleij

pinctrl: mvebu: new driver for Orion platforms

2014-04-24T13:09:35+00:00

This commit extends the pinctrl mvebu logic with a new driver to cover
Orion5x SoC. It supports the definitions for the 5181l, 5182 and 5281
variants of Orion5x, which are the three ones supported by the old
style MPP code in arch/arm/mach-orion5x/.

Signed-off-by: Thomas Petazzoni 
Acked-by: Sebastian Hesselbarth 
Signed-off-by: Linus Walleij

pinctrl: mvebu: add pin-muxing driver for the Marvell Armada 380/385

2014-02-25T17:51:05+00:00

The Marvell Armada 380/385 are new ARM SoCs from Marvell, part of the
mvebu family, but using a Cortex-A9 CPU core. In terms of pin-muxing,
it is similar to Armada 370 and XP for the register layout, only
different in the number of available pins and their
functions. Therefore, we simply use the existing
drivers/pinctrl/mvebu/ infrastructure, with no other changes that the
list of pins and corresponding functions.

Signed-off-by: Thomas Petazzoni 
Signed-off-by: Sebastian Hesselbarth

pinctrl: mvebu: add pin-muxing driver for the Marvell Armada 375

2014-02-25T17:51:01+00:00

The Marvell Armada 375 is a new ARM SoC from Marvell, part of the
mvebu family, but using a Cortex-A9 CPU core. In terms of pin-muxing,
it is similar to Armada 370 and XP for the register layout, only
different in the number of available pins and their
functions. Therefore, we simply use the existing
drivers/pinctrl/mvebu/ infrastructure, with no other changes that the
list of pins and corresponding functions.

Signed-off-by: Thomas Petazzoni 
Signed-off-by: Sebastian Hesselbarth 
Reviewed-by: Gregory CLEMENT

pinctrl: mvebu: move to its own directory

2012-11-11T18:05:57+00:00

Like the spear platform, the mvebu platform has multiple files: one
core file, and then one file per SoC family. More files will be added
later, as support for mach-orion5x and mach-mv78xx0 SoCs is added to
pinctrl-mvebu. For those reasons, having a separate subdirectory,
drivers/pinctrl/mvebu/ makes sense, and it had already been suggested
by Linus Wallej when the driver was originally submitted.

Signed-off-by: Thomas Petazzoni 
Signed-off-by: Linus Walleij