Re: One Question about WM9712 touch screen interrupt (windows mobile and PXA270)



At first, you should make sure your interrupt route to IRQ or PenDown signal
from the WM9712.
For PenDown signel the signale will be asserted whenever you touch down the
screen and
For IRQ mode you will need to write 0x0 to WM97_GPIO_PIN_STATUS(0x54) to
clear the IRQ status.

<black02@xxxxxxx> ׫??ì¶à]¼þÐÂÂ?:1167145429.252357.133240@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I had initialized and configured the WM9712 codec for touch screen.
When I hit the screen first time, it will make a interrupt from WM9712.
After that, there are not any interrupt generated. I know I need clear
the interrupt in the ISR. But I'm not familiar with the WM9712. What
should I do in the ISR for clear interrupt and prepore for the next
interrupt?
Thanks!!



.



Relevant Pages

  • [Fwd: 2.6.20-14.23 pauses on ThinkPad X32]
    ... Latency: 96 ... Subsystem: 1014:052d ... Interrupt: pin A routed to IRQ 11 ...
    (Ubuntu)
  • libata strangeness in 2.6.2-mm1 based kernel
    ... host bus clock speed is 400.0851 MHz. ... PCI Interrupt Link ... Linux Plug and Play Support v0.97 Adam Belay ... PCI Interrupt Link enabled at IRQ 23 ...
    (Linux-Kernel)
  • Re: Polling loop good here???
    ... The "vertical retrace interrupt" was IRQ 2... ... In today's hardware - as has been mentioned - they've almost certainly ... it...make use of the drivers... ...
    (alt.lang.asm)
  • PROBLEM:
    ... Unable to handle kernel paging request at virtual address 00ff0744 ... Interrupt: pin A routed to IRQ 5 ...
    (Linux-Kernel)
  • Re: [RFC] killing the NR_IRQS arrays.
    ... introduce an irq_nr(irq) to get the actual irq number for the places ... the linux "virtual" interrupt domain from the physical numbering domains ... catches interrupt packets and below that I have interrupt controllers ... That is a 16 entries irq_desc* array, so we can go from a legacy IRQ ...
    (Linux-Kernel)