Is there a way for a device driver to set the priority of the IRQ thread that services interrupts from its hardware? I am writing a device driver for a digital I/O board with general purpose interrupt capability, and I would like the application to be able to tell the driver what priority it needs those interrupts to be given. Currently it appears that preemp_rt spawns all IRQ threads with priority 50, and that the only way to change the priority of an IRQ is for an application program to execute the chrt program, after the IRQ thread has been created. However this requires that the driver pass back information to the calling program about which IRQ it is using, so that the program can then call popen to first search for the PID of the corresponding thread, and then execute chrt to change its priority. This is possible but messy, and relies on the name of IRQ threads not changing in the future. So is there a way for driver code in the kernel to identify the thread of a given IRQ, and then change its priority? Thanks, Martin -- 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
