On Thursday 06 January 2005 12:52 pm, Ian Campbell wrote: > in viper_init_irq(): > set_irq_type(VIPER_USB_IRQ, IRQT_RISING);
Just out of curiousity ... does anyone know what the story is on getting an arch-neutral set_irq_type() call? Sure, all the board support code can do that stuff. Or the drivers can #ifdef CONFIG_ARCH_ARM #elif ... (etc) to use the relevant arch-specific APIs (covering the boards for those particular architectures). But surely it'd be better to have one arch-neutral call in the chip's driver; nobody else needs to know how that hardware signal works. - Dave ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
