On Fri, 27 Sep 2013, Javier Martinez Canillas wrote:
I cc'ed Aaro Koskinen and Paul Walmsley now which seems to have OMAP1
platforms
to test. Could you please test [1] and [2] on a OMAP1 board? These patches
solves a long standing issue we have on OMAP2+ when booting with DT and it
would
On 09/27/2013 01:18 AM, Stephen Warren wrote:
On 09/24/2013 01:58 AM, Javier Martinez Canillas wrote:
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of whether an interrupt pin is also
On 9/27/2013 1:05 PM, Javier Martinez Canillas wrote:
On 09/27/2013 01:18 AM, Stephen Warren wrote:
On 09/24/2013 01:58 AM, Javier Martinez Canillas wrote:
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
Hi,
On Fri, Sep 27, 2013 at 09:35:33AM +0200, Javier Martinez Canillas wrote:
I cc'ed Aaro Koskinen and Paul Walmsley now which seems to have OMAP1
platforms to test. Could you please test [1] and [2] on a OMAP1 board?
[...]
[1]: https://patchwork.kernel.org/patch/2937351/
[2]:
On 09/24/2013 01:58 AM, Javier Martinez Canillas wrote:
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of whether an interrupt pin is also a GPIO or not,
the HW should be fully
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of whether an interrupt pin is also a GPIO or not,
the HW should be fully configured/enabled as an IRQ if a driver solely
uses IRQ APIs such
* Javier Martinez Canillas javier.marti...@collabora.co.uk [130924 01:06]:
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of whether an interrupt pin is also a GPIO or not,
the HW
On 09/24/2013 05:40 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [130924 01:06]:
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of whether an
On Tuesday 24 September 2013 09:10 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [130924 01:06]:
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as an interrupt input. Since drivers
should not be aware of
On Tuesday 24 September 2013 11:45 AM, Balaji T K wrote:
On Tuesday 24 September 2013 09:10 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [130924 01:06]:
The OMAP GPIO controller HW requires a pin to be configured in GPIO
input mode in order to operate as
* Balaji T K balaj...@ti.com [130924 08:54]:
On Tuesday 24 September 2013 09:10 PM, Tony Lindgren wrote:
Also please mention the regression that this fixes. So far we know
that smsc911x for tobi and igep boards in mainline, and also the
MMC card detect for omap4 boards.
Hi Tony,
Card
* Santosh Shilimkar santosh.shilim...@ti.com [130924 08:56]:
On Tuesday 24 September 2013 11:45 AM, Balaji T K wrote:
On Tuesday 24 September 2013 09:10 PM, Tony Lindgren wrote:
* Javier Martinez Canillas javier.marti...@collabora.co.uk [130924
01:06]:
The OMAP GPIO controller HW
12 matches
Mail list logo
