xavi/android_kernel_m2note/drivers/gpio, branch ng-7.1.2

gpio: improve error path in gpiolib

2019-07-08T11:36:43+00:00

At several places the gpiolib will proceed to handle a GPIO descriptor even if it's ->chip member is NULL and no gpiochip is associated. Fix this by checking that both the descriptor cookie *and* the chip pointer are valid. Also bail out earlier with more specific diagnostic messages on missing operations for setting as input/output or debounce. ChangeLog v1->v2: - Also return -EIO on gpiod_set_debounce() with missing operations in the vtable - Fix indentations. Change-Id: I4143419af27ecfe4ec6cfbfc8bd95ddfd9f8daa1 Suggested-by: Alexandre Courbot Acked-by: Alexandre Courbot Reviewed-by: Frank Rowand Cc: Tim Bird Signed-off-by: Linus Walleij

gpio: mpc8xxx: Correct irq handler function

2017-04-11T08:58:54+00:00

commit d71cf15b865bdd45925f7b094d169aaabd705145 upstream. From the beginning of the gpio-mpc8xxx.c, the "handle_level_irq" has being used to handle GPIO interrupts in the PowerPC/Layerscape platforms. But actually, almost all PowerPC/Layerscape platforms assert an interrupt request upon either a high-to-low change or any change on the state of the signal. So the "handle_level_irq" is not reasonable for PowerPC/Layerscape GPIO interrupt, it should be "handle_edge_irq". Otherwise the system may lost some interrupts from the PIN's state changes. Signed-off-by: Liu Gang Signed-off-by: Linus Walleij Signed-off-by: Willy Tarreau

3.10.102-> 3.10.103

2016-09-09T22:45:11+00:00

3.10.78 -> 3.10.79

2016-08-26T14:16:17+00:00

3.10.70 -> 3.10.71

2016-08-26T13:59:39+00:00

3.10.68 -> 3.10.69

2016-08-26T13:59:18+00:00

3.10.67 -> 3.10.68

2016-08-26T13:52:33+00:00

3.10.66 -> 3.10.67

2016-08-26T13:52:24+00:00

3.10.65 -> 3.10.66

2016-08-26T13:51:56+00:00

first commit

2016-08-15T02:19:42+00:00