a userspace appliaction can not catch an hardware interrupt directly. you need a driver to handle this or alternatively use user space io.
On Wed, Nov 13, 2013 at 11:25 AM, Oana Medvesan <[email protected]>wrote: > > Hello > > I use a Qualcomm Device (apq8074Dragonboard) with this kernel: > msm-AU_LINUX_ANDROID_JB_3.2_RB5.04.03.00.146.064 > > And in one of my own applications (not a kernel driver) i try to catch the > touch screen interrupt. > > cat /proc/interrupts | grep gpio > > 240: 1 GIC msmgpio > > 288: 0 msmgpio wcd9xxx > > 290: 0 msmgpio msm-sdccsdiowakeup > > 291: 0 msmgpio > > 331: 1 msmgpio atmel_mxt_ts > > The Ts controller is an atmel, so I thought that IRQ=331 is the one. > But I can’t catch it. > I can catch the msmgpio GIC IRQ (the 240) but not the msmgpio type. > Could you give me any pointers on how the msmgpio interrupt works for the > touchscreen and how exactly should I catch it? > > > Thanks you > > Regards, > Oana > > -- > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-kernel > --- > You received this message because you are subscribed to the Google Groups > "Android Linux Kernel Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel --- You received this message because you are subscribed to the Google Groups "Android Linux Kernel Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
