linux.git/drivers/sh, branch v3.6-rc2

sh: intc: Handle domain association for sparseirq pre-allocated vectors.

2012-08-09T04:21:05+00:00

Presently it's assumed that the irqdomain code handles the irq_desc
allocation for us, but this isn't necessarily the case when we've
pre-allocated IRQs via sparseirq. Previously we had a -EEXIST check in
the code that attempted to trap these cases and simply update them
in-place, but this behaviour was inadvertently lost in the transition to
irqdomains.

This simply restores the previous behaviour, first attempting to let the
irqdomain core fetch the allocation for us, and falling back to an
in-place domain association in the extant IRQ case. Fixes up regressions
on platforms that pre-allocate legacy IRQs (specifically ARM-based
SH-Mobile platforms, as SH stopped pre-allocating vectors some time ago).

Reported-by: Kuninori Morimoto 
Signed-off-by: Paul Mundt

Merge branch 'common/irqdomain' into sh-latest

2012-08-01T08:14:52+00:00

sh: intc: initial irqdomain support.

2012-08-01T08:13:46+00:00

Trivial support for irq domains, using either a linear map or radix tree
depending on the vector layout.

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

Merge branch 'common/pinctrl' into sh-latest

2012-07-20T07:42:59+00:00

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