litmus-rt-ext-res.git/include/linux/pinctrl, branch EXT-RES

pinctrl: pinconf: Add generic helper function for freeing mappings

2016-06-23T09:18:56+00:00

The pinconf-generic.h file exposes functions for creating generic mappings
but it does not expose a function for freeing the mappings. Add a function
for freeing generic mappings.

Signed-off-by: Jon Hunter 
Signed-off-by: Linus Walleij

pinctrl: Add devm_ apis for pinctrl_{register, unregister}

2016-04-20T22:01:21+00:00

Add device managed APIs devm_pinctrl_register() and
devm_pinctrl_unregister() for the APIs pinctrl_register()
and pinctrl_unregister().

This helps in reducing code in error path and sometimes
removal of .remove callback for driver unbind.

Signed-off-by: Laxman Dewangan 
Reviewed-by: Philipp Zabel 
Acked-by: Bjorn Andersson 
Signed-off-by: Linus Walleij

drivers/pinctrl: Add the concept of an "init" state

2015-10-27T10:24:23+00:00

For pinctrl the "default" state is applied to pins before the driver's
probe function is called.  This is normally a sensible thing to do,
but in some cases can cause problems.  That's because the pins will
change state before the driver is given a chance to program how those
pins should behave.

As an example you might have a regulator that is controlled by a PWM
(output high = high voltage, output low = low voltage).  The firmware
might leave this pin as driven high.  If we allow the driver core to
reconfigure this pin as a PWM pin before the PWM's probe function runs
then you might end up running at too low of a voltage while we probe.

Let's introudce a new "init" state.  If this is defined we'll set
pinctrl to this state before probe and then "default" after probe
(unless the driver explicitly changed states already).

An alternative idea that was thought of was to use the pre-existing
"sleep" or "idle" states and add a boolean property that we should
start in that mode.  This was not done because the "init" state is
needed for correctness and those other states are only present (and
only transitioned in to and out of) when (optional) power management
is enabled.

Changes in v3:
- Moved declarations to pinctrl/devinfo.h
- Fixed author/SoB

Changes in v2:
- Added comment to pinctrl_init_done() as per Linus W.

Signed-off-by: Douglas Anderson 
Acked-by: Greg Kroah-Hartman 
Tested-by: Caesar Wang 
Signed-off-by: Linus Walleij

pinctrl: pinconf-generic: sort pin configuration params alphabetically

2015-10-02T22:07:27+00:00

Currently, the dt_params array in drivers/pinctrl/pinconf-generic.c
is not sorted in the same order as the enum pin_config_param in
include/linux/pinctrl/pinconf-generic.h.

Sort enum pin_config_param, conf_items, dt_params, alphabetically
for consistency.

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

pinctrl: use "const struct ..." rather than "struct ... const"

2015-06-01T13:48:12+00:00

Only this member, pins, is defined as "struct ... const *", but the
others in this struct, pinlops, pmxops, confops, etc. are defined as
"const struct ... *".

Swap the "struct pinctrl_pin_desc" and "const" for consistency.

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

pinctrl: remove useless const qualifier

2015-06-01T13:47:20+00:00

This "const" claims the get_function_groups callback never
changes the given num_groups pointer.  It is always true
in C language, so not worth mentioning.

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

pinctrl: use ERR_CAST instead of ERR_PTR/PTR_ERR

2015-05-06T13:34:51+00:00

Inspired by scripts/coccinelle/api/err_cast.cocci

Signed-off-by: Fabian Frederick 
Signed-off-by: Linus Walleij

pinctrl: move strict option to pinmux_ops

2015-05-06T12:45:19+00:00

While the pinmux_ops are ideally just a vtable for pin mux
calls, the "strict" setting belongs so intuitively with the
pin multiplexing that we should move it here anyway. Putting
it in the top pinctrl_desc makes no sense.

Cc: Sonic Zhang 
Signed-off-by: Linus Walleij

pinctrl: allow exlusive GPIO/mux pin allocation

2015-05-06T12:45:19+00:00

Disallow simultaneous use of the the GPIO and peripheral mux
functions by setting a flag "strict" in struct pinctrl_desc.

The blackfin pinmux and gpio controller doesn't allow user to
set up a pin for both GPIO and peripheral function. So, add flag
strict in struct pinctrl_desc to check both gpio_owner and
mux_owner before approving the pin request.

v2-changes:
- if strict flag is set, check gpio_owner and mux_onwer in if and
  else clause

v3-changes:
- add kerneldoc for this struct
- augment Documentation/pinctrl.txt

Signed-off-by: Sonic Zhang 
Signed-off-by: Linus Walleij

Revert "pinctrl: consumer: use correct retval for placeholder functions"

2015-03-05T09:08:14+00:00

This reverts commit 5a7d2efdd93f6c4bb6cd3d5df3d2f5611c9b87ac.

As per discussion on the mailing list, this is not the right
thing to do. NULL cookies are valid in the stubs.

Reported-by: Wolfram Sang 
Signed-off-by: Linus Walleij