linux.git/drivers/pinctrl/Kconfig, branch v4.12

pinctrl: Add pincontrol driver for ARTPEC-6 SoC

2017-04-07T09:48:33+00:00

Add pinctrl driver support for the Axis ARTPEC-6 SoC.
There are only some pins that actually have different
functions available, but all can control bias (pull-up/-down)
and drive strength.

Code originally written by Chris Paterson.

Signed-off-by: Jesper Nilsson 
Signed-off-by: Linus Walleij

pinctrl: Introduce TI IOdelay configuration driver

2017-01-09T18:43:21+00:00

SoC family such as DRA7 family of processors have, in addition
to the regular muxing of pins (as done by pinctrl-single), a separate
hardware module called IODelay which is also expected to be configured.
The "IODelay" module has it's own register space that is independent
of the control module and the padconf register area.

With recent changes to the pinctrl framework, we can now support
this hardware with a reasonably minimal driver by using #pinctrl-cells,
GENERIC_PINCTRL_GROUPS and GENERIC_PINMUX_FUNCTIONS.

It is advocated strongly in TI's official documentation considering
the existing design of the DRA7 family of processors during mux or
IODelay reconfiguration, there is a potential for a significant glitch
which may cause functional impairment to certain hardware. It is
hence recommended to do as little of muxing as absolutely necessary
without I/O isolation (which can only be done in initial stages of
bootloader).

NOTE: with the system wide I/O isolation scheme present in DRA7 SoC
family, it is not reasonable to do stop all I/O operations for every
such pad configuration scheme. So, we will let it glitch when used in
this mode.

Even with the above limitation, certain functionality such as MMC has
mandatory need for IODelay reconfiguration requirements, depending on
speed of transfer. In these cases, with careful examination of usecase
involved, the expected glitch can be controlled such that it does not
impact functionality.

In short, IODelay module support as a padconf driver being introduced
here is not expected to do SoC wide I/O Isolation and is meant for
a limited subset of IODelay configuration requirements that need to
be dynamic and whose glitchy behavior will not cause functionality
failure for that interface.

IMPORTANT NOTE: we take the approach of keeping LOCK_BITs cleared
to 0x0 at all times, even when configuring Manual IO Timing Modes.
This is done by eliminating the LOCK_BIT=1 setting from Step
of the Manual IO timing Mode configuration procedure. This option
leaves the CFG_* registers unprotected from unintended writes to the
CTRL_CORE_PAD_* registers while Manual IO Timing Modes are configured.

This approach is taken to allow for a generic driver to exist in kernel
world that has to be used carefully in required usecases.

Signed-off-by: Nishanth Menon 
Signed-off-by: Lokesh Vutla 
[tony@atomide.com: updated to use generic pinctrl functions, added
 binding documentation, updated comments]
Acked-by: Rob Herring 
Signed-off-by: Tony Lindgren 
Signed-off-by: Linus Walleij

pinctrl: single: Use generic pinmux helpers for managing functions

2017-01-03T08:26:19+00:00

We can now drop the driver specific code for managing functions.

Signed-off-by: Tony Lindgren 
[Replaces GENERIC_PINMUX with GENERIC_PINMUX_FUNCTIONS]
Signed-off-by: Linus Walleij

pinctrl: single: Use generic pinctrl helpers for managing groups

2017-01-03T08:26:19+00:00

We can now drop the driver specific code for managing groups.

Signed-off-by: Tony Lindgren 
Signed-off-by: Linus Walleij

pinctrl: core: Add generic pinctrl functions for managing groups

2017-01-03T08:26:18+00:00

We can add generic helpers for function handling for cases where the pin
controller driver does not need to use static arrays.

Signed-off-by: Tony Lindgren 
[Renamed the Kconfig item and moved things around]
Signed-off-by: Linus Walleij

pinctrl: stricten up generic group code

2017-01-03T08:26:18+00:00

Rename the symbol PINCTRL_GENERIC to PINCTRL_GENERIC_GROUPS since
it all pertains to groups. Replace everywhere.

ifdef out the radix tree and the struct when not using the
generic groups.

Cc: Tony Lindgren 
Signed-off-by: Linus Walleij

pinctrl: core: Add generic pinctrl functions for managing groups

2017-01-03T08:26:17+00:00

We can add generic helpers for pin group handling for cases where the pin
controller driver does not need to use static arrays.

Signed-off-by: Tony Lindgren 
Signed-off-by: Linus Walleij

pinctrl: New driver for TI DA850/OMAP-L138/AM18XX pinconf

2016-12-07T14:27:00+00:00

This adds a new driver for pinconf on TI DA850/OMAP-L138/AM18XX. These
SoCs have a separate controller for controlling pullup/pulldown groups.

Signed-off-by: David Lechner 
Reviewed-by: Sekhar Nori 
Signed-off-by: Linus Walleij

pinctrl-sx150x: Convert driver to use regmap API

2016-11-08T08:39:06+00:00

To allow for future code simplification

Tested-by: Neil Armstrong 
Acked-by: Neil Armstrong 
Signed-off-by: Andrey Smirnov 
Signed-off-by: Linus Walleij

pinctrl: max77620: add OF dependency

2016-10-29T08:30:16+00:00

Drivers using pinconf_generic_params tables cannot be built with
CONFIG_OF disabled:

drivers/pinctrl/pinctrl-max77620.c:53:44: error: array type has incomplete element type ‘struct pinconf_generic_params’
drivers/pinctrl/pinctrl-max77620.c:55:3: error: field name not in record or union initializer
drivers/pinctrl/pinctrl-max77620.c:55:3: note: (near initialization for ‘max77620_cfg_params’)
drivers/pinctrl/pinctrl-max77620.c:56:3: error: field name not in record or union initializer

This adds a dependency for max77620 to disallow that configuration.

Alternatively, we could rework the pinctrl infrastructure to make the
configuration valid for compile-testing.

Cc: Krzysztof Kozlowski 
Cc: Lee Jones 
Fixes: 453943dc8f45 ("mfd: Enable compile testing for max77620 and max77686")
Signed-off-by: Arnd Bergmann 
Signed-off-by: Linus Walleij