a342d215c2
A number of drivers in drivers/gpio return -ENODEV when confronted with missing setup parameters such as the platform data. However, returning -ENODEV causes the driver layer to silently ignore the driver as it assumes the probe did not find anything and was only speculative. To make life easier to discern why a driver is not being attached, change to returning -EINVAL, which is a better description of the fact that the driver data was not valid. Also add a set of dev_dbg() statements to the error paths to provide an better explanation of the error as there may be more that one point in the driver. Signed-off-by: Ben Dooks <ben-linux@fluff.org> Cc: David Brownell <david-b@pacbell.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
|---|---|---|
| .. | ||
| bt8xxgpio.c | ||
| gpiolib.c | ||
| Kconfig | ||
| Makefile | ||
| max732x.c | ||
| max7301.c | ||
| mcp23s08.c | ||
| pca953x.c | ||
| pcf857x.c | ||
| twl4030-gpio.c | ||
| xilinx_gpio.c | ||