Sascha Herrmann wrote: > Maybe one way to eliminate the extra latency of the second register read > would be to split the interrupt handling function into a generic part > and two different functions to handle the different types of interrupts:
Yes, if you want to optimize the number of register accesses and work queue invocations, splitting the paths that touch interrupts seems to be the most straightforward approach. > If you think the solution above would be ok, I could try to send a > version which allows the configuration of trigger type and level. Sounds good to me. Pity the irq_get_irq_type() you mentioned doesn't exist. That would have made things a bit nicer. - Werner ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
