> Hi, > > I am trying to use the parport interrupt (pin 10) on a RT_PREEMPT Linux > Kernel. I am using the parport_pc module to register a custom driver > that synchronize the clocks using an external clock generator, by > sending a signal to the parport interrupt pin 10 (ACK). With kernel > 2.4.24 i have no problems on using the interface that the parport_pc > driver offers me. But, as my userspace applications needs RT, i've > installed the RT_PREEMPT patches, and my driver is not working now. The > attach function of my driver is: [...] > > This should be enough to register my driver with the parint_handler > function as the "callback" when the IRQ (7) ocurrs. In summary, i am > registering the device, the callback, enabling the IRQ at the control > register (0x10), and enabling the IRQ in the parport_driver. Ok. It seems to work for very limnited time quantums. Maybe the interrupt handler thread IRQ7 should have a higher priority, but i dont know how to do this... :S > I've change the IRQ flags to IRQF_NODElAY in the parport driver, > and I've write also a module without using the parport_pc, > and still the interrupt denies to works. -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
