diff options
| author | Nishanth Menon <nm@ti.com> | 2011-09-23 11:54:15 -0500 |
|---|---|---|
| committer | Colin Cross <ccross@android.com> | 2011-09-23 20:05:25 -0700 |
| commit | 65e4c72b3cf5d0999344e32c51492a5fdd136006 (patch) | |
| tree | 648b55fb50941af65fdded548b23fa8ed39f022d /arch/arm/include/asm | |
| parent | 41978441492eb365bb35a303f381aa2aec729b1b (diff) | |
| download | kernel_samsung_tuna-65e4c72b3cf5d0999344e32c51492a5fdd136006.zip kernel_samsung_tuna-65e4c72b3cf5d0999344e32c51492a5fdd136006.tar.gz kernel_samsung_tuna-65e4c72b3cf5d0999344e32c51492a5fdd136006.tar.bz2 | |
OMAP2+: mux: warn only when GPIO really not found
omap_mux_init_gpio calls _omap_mux_init_gpio for each of the
partitions defined for the device while searching for the mux
signal requested. However, on platforms such as OMAP4 which have
multiple partitions, GPIO which is present in a later partition
will be failed to be found by _omap_mux_init_gpio in the earlier
partition search. It currently puts out a scary warning
"__omap_mux_init_gpio: Could not set gpioxx"
which is interpreted as mux configuration was faulty, which could
be:
a) a real mismatch due to typo error on behalf of the developer
or
b) just an indication that the signal was not found in an earlier
partition.
Instead move the warning to omap_mux_init_gpio to report this
warning *only after* all alternatives have been exhausted to
ensure that this warning is really for (a).
Change-Id: I243efb658aa335a82cca43232e4491c0d01c1117
Signed-off-by: Nishanth Menon <nm@ti.com>
Diffstat (limited to 'arch/arm/include/asm')
0 files changed, 0 insertions, 0 deletions