Re: [patch 1/4] Make usb_hcd_irq available for multi-role USB controllers with a shared interrupt line
Alan Cox <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
> For ohci-hcd, we used -1. The problem here is, while IRQ 0 is definitely > not valid for PCI devices (as Alan Cox reminded me a couple of weeks ago), > USB controllers are found in odd embedded configurations often, so we > cannot just use 0 as invalid everywhere. I don't know if -1 is good though. > Seems like it should be. Alan Cox also cautioned against using NO_IRQ, > because it's not universally defined by all platforms, and in general is > an invention of old IDE. Looks like -1 is the way to go. Zero means "no IRQ" in the kernel. No platform should be reporting an IRQ number of zero, the platform has to re-map it should there be a physical IRQ 0 used by drivers. Alan ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel