No interrupts coming to device driver.

From: Alexander Nedotsukov (bland_at_FreeBSD.org)
Date: 11/10/05

  • Next message: Daniel O'Connor: "Re: No interrupts coming to device driver." 
    Date: Thu, 10 Nov 2005 17:50:05 +0900
To: freebsd-hackers@FreeBSD.org

    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?

    Thanks,
    Alexander.
    _______________________________________________
    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: Daniel O'Connor: "Re: No interrupts coming to device driver."

    Relevant Pages

    • Re: No interrupts coming to device driver.
      ... : coming to driver. ... I believe I configured chip (carrier freq. ... divisor) and enabled interrupt mode the same way it windows driver does. ... If it is on the ISA bus, then you can look at the IRQ line that you ...
      (freebsd-hackers)
    • Re: [GIT PATCH] more Driver core patches for 2.6.19
      ... The design requires to have an in kernel stub driver with interrupt ... The chip specific portion of the interrupt handler. ... wakeup user space task ...
      (Linux-Kernel)
    • Re: How to Disable Ethernet
      ... How can I be sure that KITL is no longer accessing it? ... When I run my driver, I get interrupts from the 91C96 that ... a new interrupt is generated. ... >> 91C96 ethernet chip other than my driver. ...
      (microsoft.public.windowsce.platbuilder)
    • Re: [PATCH] OMAP: I2C driver for TI OMAP boards #2
      ... "I2C chip type X at address A, using interrupt I and platform_data P") ... the device driver model is done, I guess it'll come naturally if needed. ...
      (Linux-Kernel)
    • 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)