Hi, On Tue, Apr 25, 2006 at 08:36:45AM +0200, Veldeman, Jan wrote: > In some cases the irq may not be requested by usb_add_hcd. E.g. the > interrupt is shared among different parts of the same driver, and by > having only 1 handler which calls the others, helps in making the > driver cleaner. > > By exporting usb_hcd_irq, the driver can call the irq handler at the > correct time, without duplicating any code (otherwise, the > functionality of ush_hcd_irq had to be duplicated). > > A negative number denotes that the irq should not be requested by > usb_add_hcd. > > Signed-off-by: Jan Veldeman <[EMAIL PROTECTED]> > > --- > > drivers/usb/core/hcd.c | 8 ++++++-- > drivers/usb/core/hcd.h | 2 +- > 2 files changed, 7 insertions(+), 3 deletions(-) >
are there other objections to this patch? (besides not using irq 0 as a special case, which has been fixed) Best regards, Jan ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
