Re: No interrupts coming to device driver.

From: Hans Petter Selasky (hselasky_at_c2i.net)
Date: 11/10/05

  • Next message: Poul-Henning Kamp: "Re: GEOM for multipath? How?" 
    To: freebsd-hackers@freebsd.org
Date: Thu, 10 Nov 2005 14:08:49 +0100

    On Thursday 10 November 2005 09:50, Alexander Nedotsukov wrote:
    > Hi,
    >
    > I trying to create small lirc (www.lirc.org) compatible CIR driver for
    > it8705 chip (sits on ISA bus). My problem is I can not get interrupts
    > coming to driver. I believe I configured chip (carrier freq. + baudrate
    > divisor) and enabled interrupt mode the same way it windows driver does.
    > It also seems to be correct according to chip specs. But nothing. vmstat
    > -i shows zeros for assigned irq. And my IRS stay cold. I wrote small
    > userland program which polls CIRs IIR (interrupt identefication
    > register) and it shows interrupt pending bit set on right after I press
    > key on remote control. Looks like I missed something fundamental. Does
    > anyone can give me a hint where to look?
    >

    Sounds like you have an unacknowledged interrupt. Does it help if you call the
    interrupt handler once after that your chip has been reset and configured?
    Else sharing some of the source code might help.

    --HPS
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"

  • Next message: Poul-Henning Kamp: "Re: GEOM for multipath? How?"

    Relevant Pages

    • No interrupts coming to device driver.
      ... I trying to create small lirc compatible CIR driver for ... coming to driver. ... I believe I configured chip (carrier freq. ... divisor) and enabled interrupt mode the same way it windows driver does. ...
      (freebsd-hackers)
    • Re: No interrupts coming to device driver.
      ... >> divisor) and enabled interrupt mode the same way it windows driver does. ... >> It also seems to be correct according to chip specs. ... calling interrupt handler right after initialization does not seem to help. ...
      (freebsd-hackers)