diff options
author | Geert Uytterhoeven <geert+renesas@glider.be> | 2015-12-04 16:33:53 +0100 |
---|---|---|
committer | Linus Walleij <linus.walleij@linaro.org> | 2015-12-11 10:11:40 +0100 |
commit | e1fef9e2ce4272b720ecb1ce696a72aaddbb7585 (patch) | |
tree | 7f0db2e1ff9ef4fac656f2fa0a89c3758cb4bb9e /Documentation/leds | |
parent | 8b092be9fd6a2cd84c437128e9b0d85e364efcfb (diff) | |
download | linux-e1fef9e2ce4272b720ecb1ce696a72aaddbb7585.tar.bz2 |
gpio: rcar: Improve clock error handling and reporting
If the Renesas R-Car GPIO driver cannot find a functional clock, it
prints a warning, .e.g.
gpio_rcar ffc40000.gpio: unable to get clock
and continues, as the clock is optional, depending on the SoC type.
This warning may confuse users.
To fix this, add a flag to indicate that the clock is mandatory or
optional:
- If the clock is mandatory (on R-Car Gen2 and Gen3), a missing clock
is now treated as a fatal error,
- If the clock is optional (on R-Car Gen1), the warning is no longer
printed.
Suggested-by: Magnus Damm <magnus.damm@gmail.com>
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Simon Horman <horms+renesas@verge.net.au>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'Documentation/leds')
0 files changed, 0 insertions, 0 deletions