linux-toradex.git/drivers/sh/pfc, branch v3.6

sh: pfc: Fix up GPIO mux type reconfig case.

2012-09-25T02:51:05+00:00

Some drivers need to switch pin states between GPIO and pin function at
runtime, which was inadvertently broken in the pinctrl driver for GPIOs
being bound to a specific direction.

This fixes up the request path to ensure that previously configured GPIOs
don't cause us to inadvertently error out with an unsupported mux on
reconfig, which in practice is primarily aimed at trapping pull-up/down
users that have yet to be implemented under the new API.

Fixes up regressions in the TPU PWM driver, amongst others.

Reported-by: Laurent Pinchart 
Tested-by: Laurent Pinchart 
Signed-off-by: Paul Mundt

sh: pfc: Release spinlock in sh_pfc_gpio_request_enable() error path

2012-09-18T07:54:46+00:00

The sh_pfc_gpio_request_enable() function acquires a spinlock but fails
to release it before returning if the requested mux type is not
supported. Fix this.

Signed-off-by: Laurent Pinchart 
Signed-off-by: Paul Mundt

sh: pfc: Fix up init ordering mess.

2012-08-01T07:27:38+00:00

Commit ca5481c68e9fbcea62bb3c78ae6cccf99ca8fb73 ("sh: pfc: Rudimentary
pinctrl-backed GPIO support.") introduced a regression for platforms that
were doing early GPIO API calls (from arch_initcall() or earlier),
leading to a situation where our two-stage registration logic would trip
itself up and we'd -ENODEV out of the pinctrl registration path,
resulting in endless -EPROBE_DEFER errors. Further lack of checking any
sort of errors from gpio_request() resulted in boot time warnings,
tripping on the FLAG_REQUESTED test-and-set in gpio_ensure_requested().

As it turns out there's no particular need to bother with the two-stage
registration, as the platform bus is already available at the point that
we have to start caring. As such, it's easiest to simply fold these
together in to a single init path, the ordering of which is ensured
through the platform's mux registration, as usual.

Reported-by: Rafael J. Wysocki 
Reported-by: Kuninori Morimoto 
Signed-off-by: Paul Mundt

sh: pfc: Build fix for pinctrl_remove_gpio_range() changes.

2012-07-25T04:10:11+00:00

pinctrl_remove_gpio_range() is now handled by the pinctrl core in the
unreg path for some reason, so use that instead.

Signed-off-by: Paul Mundt

sh: pfc: pin config get/set support.

2012-07-20T07:39:09+00:00

This implements simple support for adjusting the pin config value via the
pinctrl API. The pinconf-generic code is abandoned for now until we've
got a chance to revamp the pinmux_type state tracking that's needed by
legacy code.

Signed-off-by: Paul Mundt

sh: pfc: Prefer DRV_NAME over KBUILD_MODNAME.

2012-07-20T07:18:21+00:00

While this code is still being shuffled around the KBUILD_MODNAME value
isn't particularly useful, switch to something a bit more useful.

Signed-off-by: Paul Mundt

sh: pfc: pinctrl legacy group support.

2012-07-17T06:48:18+00:00

This follows the function support by simply doing 1 pin per group
encapsulation in order to keep with legacy behaviour. This will be
built on incrementally as SoCs define their own pin groups.

Signed-off-by: Paul Mundt

sh: pfc: Ignore pinmux GPIOs with invalid enum IDs.

2012-07-17T06:23:11+00:00

If we encounter invalid entries in the pinmux GPIO range, make sure we've
still got a dummy pin definition but don't otherwise map it.

Signed-off-by: Paul Mundt

sh: pfc: Export pinctrl binding init symbol.

2012-07-17T06:21:47+00:00

symbol_request() requires the registration symbol to be exported, make
sure it is.

Signed-off-by: Paul Mundt

sh: pfc: Error out on pinctrl init resolution failure.

2012-07-17T06:18:37+00:00

pinctrl support is required for correct operation, failure to locate
the init routine is fatal.

Signed-off-by: Paul Mundt