Re: [GPIO] Crashed when not using

2012-08-05 Thread Shilimkar, Santosh
On Tue, Jul 31, 2012 at 6:26 PM, Poddar, Sourav wrote: > Hi Santosh, > > On Tue, Jul 31, 2012 at 6:02 PM, Shilimkar, Santosh > wrote: >> On Tue, Jul 31, 2012 at 8:52 AM, Felipe Balbi wrote: >>> >>> Hi, >>> >>> On Tue, Jul 31, 2012 at 10:23:16AM +0530, Poddar, Sourav wrote: >>> > The device

Re: [GPIO] Crashed when not using

2012-07-31 Thread Poddar, Sourav
Hi Santosh, On Tue, Jul 31, 2012 at 6:02 PM, Shilimkar, Santosh wrote: > On Tue, Jul 31, 2012 at 8:52 AM, Felipe Balbi wrote: >> >> Hi, >> >> On Tue, Jul 31, 2012 at 10:23:16AM +0530, Poddar, Sourav wrote: >> > The device tree data for acquiring the above GPIO interrupt line >> > looks

Re: [GPIO] Crashed when not using

2012-07-31 Thread Felipe Balbi
Hi, On Tue, Jul 31, 2012 at 02:32:43PM +0200, Shilimkar, Santosh wrote: > On Tue, Jul 31, 2012 at 8:52 AM, Felipe Balbi wrote: > > > > Hi, > > > > On Tue, Jul 31, 2012 at 10:23:16AM +0530, Poddar, Sourav wrote: > > > The device tree data for acquiring the above GPIO interrupt line > > >

Re: [GPIO] Crashed when not using

2012-07-31 Thread Shilimkar, Santosh
On Tue, Jul 31, 2012 at 8:52 AM, Felipe Balbi wrote: > > Hi, > > On Tue, Jul 31, 2012 at 10:23:16AM +0530, Poddar, Sourav wrote: > > The device tree data for acquiring the above GPIO interrupt line > > looks > > like this. > > > > +++ linux-omap-storage/arch/arm/boot/dts/o

Re: [GPIO] Crashed when not using

2012-07-30 Thread Felipe Balbi
Hi, On Tue, Jul 31, 2012 at 10:23:16AM +0530, Poddar, Sourav wrote: > The device tree data for acquiring the above GPIO interrupt line looks > like this. > > +++ linux-omap-storage/arch/arm/boot/dts/omap5-evm.dts 2012-07-30 > 14:11:08.931694001 +0530 > @@ -42,7 +42,8

Re: [GPIO] Crashed when not using

2012-07-30 Thread Felipe Balbi
Hi, On Mon, Jul 30, 2012 at 01:36:47PM -0700, Kevin Hilman wrote: > >>> The device tree data for acquiring the above GPIO interrupt line looks > >>> like this. > >>> > >>> +++ linux-omap-storage/arch/arm/boot/dts/omap5-evm.dts 2012-07-30 > >>> 14:11:08.931694001 +0530 > >>> @@ -42,7 +42,8 @@ >

Re: [GPIO] Crashed when not using

2012-07-30 Thread Poddar, Sourav
Hi Kevin, On Tue, Jul 31, 2012 at 2:06 AM, Kevin Hilman wrote: > "Poddar, Sourav" writes: > >> On Mon, Jul 30, 2012 at 3:04 PM, DebBarma, Tarun Kanti >> wrote: >>> Sourav, >>> >>> On Mon, Jul 30, 2012 at 2:13 PM, Poddar, Sourav >>> wrote: Hi All, I tried using gpio as an interr

Re: [GPIO] Crashed when not using

2012-07-30 Thread Shilimkar, Santosh
On Mon, Jul 30, 2012 at 10:36 PM, Kevin Hilman wrote: > > "Poddar, Sourav" writes: > > > On Mon, Jul 30, 2012 at 3:04 PM, DebBarma, Tarun Kanti > > wrote: > >> Sourav, > >> > >> On Mon, Jul 30, 2012 at 2:13 PM, Poddar, Sourav > >> wrote: > >>> Hi All, > >>> > >>> I tried using gpio as an interr

Re: [GPIO] Crashed when not using

2012-07-30 Thread Kevin Hilman
"Poddar, Sourav" writes: > On Mon, Jul 30, 2012 at 3:04 PM, DebBarma, Tarun Kanti > wrote: >> Sourav, >> >> On Mon, Jul 30, 2012 at 2:13 PM, Poddar, Sourav wrote: >>> Hi All, >>> >>> I tried using gpio as an interrupt line for my driver >>> (drivers/staging/iio/light/tsl2x7x_core.c) for omap5.

Re: [GPIO] Crashed when not using

2012-07-30 Thread Poddar, Sourav
On Mon, Jul 30, 2012 at 3:04 PM, DebBarma, Tarun Kanti wrote: > Sourav, > > On Mon, Jul 30, 2012 at 2:13 PM, Poddar, Sourav wrote: >> Hi All, >> >> I tried using gpio as an interrupt line for my driver >> (drivers/staging/iio/light/tsl2x7x_core.c) for omap5. >> The interrupt line number was direc

Re: [GPIO] Crashed when not using

2012-07-30 Thread DebBarma, Tarun Kanti
Sourav, On Mon, Jul 30, 2012 at 2:13 PM, Poddar, Sourav wrote: > Hi All, > > I tried using gpio as an interrupt line for my driver > (drivers/staging/iio/light/tsl2x7x_core.c) for omap5. > The interrupt line number was directly passed to the driver using > device tree. But what I observed > is th

[GPIO] Crashed when not using

2012-07-30 Thread Poddar, Sourav
Hi All, I tried using gpio as an interrupt line for my driver (drivers/staging/iio/light/tsl2x7x_core.c) for omap5. The interrupt line number was directly passed to the driver using device tree. But what I observed is the following crash.. [1.599273] mousedev: PS/2 mouse device common for al