> Greg:
>
> This patch contains the changes to the ohci-sa driver.
>
> Alan Stern
This patch introduces several paths in the interrupt handler that return
IRQ_NONE. In the original code, we took care (in usb_hcd_sa_hcim_irq)
to always return IRQ_HANDLED, no matter what. I don't recall
On Thu, Feb 10, 2005 at 02:08:16PM -0800, Christopher Hoover wrote:
> > Greg:
> >
> > This patch contains the changes to the ohci-sa driver.
> >
> > Alan Stern
>
>
> This patch introduces several paths in the interrupt handler that return
> IRQ_NONE. In the original code, we took care (in
On Thu, 10 Feb 2005, Russell King wrote:
> On Thu, Feb 10, 2005 at 02:08:16PM -0800, Christopher Hoover wrote:
> > > Greg:
> > >
> > > This patch contains the changes to the ohci-sa driver.
> > >
> > > Alan Stern
> >
> >
> > This patch introduces several paths in the interrupt handler that
> The other path introduced by my patch where IRQ_NONE can be returned
> gets used only at times when the controller is not running
> and hence is
> incapable of generating interrupts. So it shouldn't be a problem.
>
> Would this be satisfactory? Or do you prefer to change the
> core interrup
On Monday 14 February 2005 4:59 pm, Christopher Hoover wrote:
>
> > The other path introduced by my patch where IRQ_NONE can be returned
> > gets used only at times when the controller is not running
> > and hence is
> > incapable of generating interrupts. So it shouldn't be a problem.
> >
> >
