Re: [PATCH 1/2] gpio: gpio-mxc: Fix: higher 16 GPIOs usable as wake source

2017-08-01 Thread Linus Walleij
On Wed, Jul 12, 2017 at 10:36 AM, Philipp Rosenberger wrote: > In the function gpio_set_wake_irq(), port->irq_high is only checked for > zero. As platform_get_irq() returns a value less then zero if no interrupt > was found, any gpio >= 16 was handled like an

Re: [PATCH 1/2] gpio: gpio-mxc: Fix: higher 16 GPIOs usable as wake source

2017-08-01 Thread Linus Walleij
On Wed, Jul 12, 2017 at 10:36 AM, Philipp Rosenberger wrote: > In the function gpio_set_wake_irq(), port->irq_high is only checked for > zero. As platform_get_irq() returns a value less then zero if no interrupt > was found, any gpio >= 16 was handled like an irq_high interrupt was > available.

[PATCH 1/2] gpio: gpio-mxc: Fix: higher 16 GPIOs usable as wake source

2017-07-12 Thread Philipp Rosenberger
In the function gpio_set_wake_irq(), port->irq_high is only checked for zero. As platform_get_irq() returns a value less then zero if no interrupt was found, any gpio >= 16 was handled like an irq_high interrupt was available. On iMX27 for example no high interrupt is available. This lead to the

[PATCH 1/2] gpio: gpio-mxc: Fix: higher 16 GPIOs usable as wake source

2017-07-12 Thread Philipp Rosenberger
In the function gpio_set_wake_irq(), port->irq_high is only checked for zero. As platform_get_irq() returns a value less then zero if no interrupt was found, any gpio >= 16 was handled like an irq_high interrupt was available. On iMX27 for example no high interrupt is available. This lead to the