linux-toradex.git/drivers/pinctrl/pinmux.c, branch v4.9.131

pinctrl: return -ENOMEM instead of -EINVAL for kasprintf() failure

2016-05-31T08:33:00+00:00

-ENOMEM is more suitable error code because kasprintf() fails
in case of memory shortage.

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

pinctrl: do not care about blank pin name

2016-05-31T08:19:56+00:00

If a pin name is not specified in struct pinctrl_pin_desc,
pinctrl_register_one_pin() dynamically assigns its name.
So, desc->name is always a valid pointer here.

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

pinctrl: convert to use match_string() helper

2016-03-17T22:09:34+00:00

The new helper returns index of the mathing string in an array.  We
would use it here.

Signed-off-by: Andy Shevchenko 
Acked-by: Linus Walleij 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

pinctrl: join lines that can be a single line within 80 columns

2015-09-14T07:13:43+00:00

There is no reason to break a line shorter than 80 columns.

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

pinctrl: use dev_err() to show message in pinmux_func_name_to_selector()

2015-07-27T12:44:33+00:00

Use dev_err() rather than pr_err() to display the error message.

pinctrl_dev_get_name(pctldev) is no longer necessary because
dev_err() shows which device the message is related to.

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

pinctrl: don't print unavailable function groups

2015-06-10T08:44:05+00:00

There is no reason to try to print groups associated to a function if
get_function_groups returns an error. Moreover, it can lead to a NULL
pointer dereference error.

Signed-off-by: Ludovic Desroches 
Signed-off-by: Linus Walleij

pinctrl: improve debugfs for strict controllers

2015-05-28T08:14:21+00:00

If we know we are using a strict pin controller (one that cannot
mix device functions+group use and GPIO) we can be a bit more
specific in debugfs, just print either device-function-group
or GPIO consumer for the pin. Let's do that to be helpful.

Cc: Sonic Zhang 
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

pinctrl: clean up after enable refactoring

2014-09-04T08:05:07+00:00

commit 2243a87d90b42eb38bc281957df3e57c712b5e56
"pinctrl: avoid duplicated calling enable_pinmux_setting for a pin"
removed the .disable callback from the struct pinmux_ops,
making the .enable() callback the only remaining callback.

However .enable() is a bad name as it seems to imply that a
muxing can also be disabled. Rename the callback to .set_mux()
and also take this opportunity to clean out any remaining
mentions of .disable() from the documentation.

Acked-by: Stephen Warren 
Acked-by: Bjorn Andersson 
Acked-by: Fan Wu 
Signed-off-by: Linus Walleij