On 12/15/2013 03:54 PM, Sekhar Nori wrote:
On Sunday 15 December 2013 07:20 PM, Sekhar Nori wrote:
On Sunday 15 December 2013 12:41 AM, Santosh Shilimkar wrote:
Linus, Sekhar,
On Thursday 12 December 2013 01:12 PM, Grygorii Strashko wrote:
This series is intended to update Davinci GPIO
On 12/16/2013 09:29 AM, Alexandre Courbot wrote:
On Fri, Dec 13, 2013 at 3:12 AM, Grygorii Strashko
grygorii.stras...@ti.com wrote:
The similar GPIO HW block is used by keystone SoCs as
in Davinci SoCs.
Hence, reuse Davinci GPIO driver for Keystone taking into
account that Keystone contains ARM
On Sunday 15 December 2013 08:50 AM, Sekhar Nori wrote:
On Sunday 15 December 2013 12:41 AM, Santosh Shilimkar wrote:
Linus, Sekhar,
On Thursday 12 December 2013 01:12 PM, Grygorii Strashko wrote:
This series is intended to update Davinci GPIO driver and reuse
it for Keystone SoCs, because
On Thursday 12 December 2013 01:12 PM, Grygorii Strashko wrote:
The system may crash if:
- there are more then 1 bank
- unbanked irqs are enabled
- someone will call gpio_to_irq() for GPIO from bank2 or above
Hence, fix it by not creating irq_domain if unbanked irqs are enabled
and correct
On Thursday 12 December 2013 01:12 PM, Grygorii Strashko wrote:
The similar GPIO HW block is used by keystone SoCs as
in Davinci SoCs.
Hence, reuse Davinci GPIO driver for Keystone taking into
account that Keystone contains ARM GIC IRQ controller which
is implemented using IRQ Chip.
On Monday 16 December 2013 10:09 AM, Santosh Shilimkar wrote:
On Sunday 15 December 2013 08:50 AM, Sekhar Nori wrote:
On Sunday 15 December 2013 12:41 AM, Santosh Shilimkar wrote:
Linus, Sekhar,
On Thursday 12 December 2013 01:12 PM, Grygorii Strashko wrote:
This series is intended to update
On 12/16/2013 06:38 PM, Santosh Shilimkar wrote:
On Thursday 12 December 2013 01:12 PM, Grygorii Strashko wrote:
The similar GPIO HW block is used by keystone SoCs as
in Davinci SoCs.
Hence, reuse Davinci GPIO driver for Keystone taking into
account that Keystone contains ARM GIC IRQ controller