On Thursday 27 April 2006 1:47 am, Sujith Sankar wrote:
> Hi All,
>
> Our team is implementing a USB OTG Controller Driver in Linux for ARC
> controller. The transceiver and OTG controller are integrated.
>
> We have the following doubt.
>
> 1.) The implementation involves three modules viz EH
On Thu, 27 Apr 2006, Sujith Sankar wrote:
> If shared handlers were used, how did you mask the interrupts while servicing?
>
> If SA_SHIRQ is used, isn't it the responsibility of ISR to mask the
> interrupts at the starting, service the received interrupt and unmask
> the interrupts before return
27, 2006 5:02 PM
To: Li Yang-r58472
Cc: linux usb devel
Subject: Re: [linux-usb-devel] USB OTG ISR Registration
If shared handlers were used, how did you mask the interrupts while
servicing?
If SA_SHIRQ is used, isn't it the responsibility of ISR to mask the
interrupts at the starting, ser
o: Li Yang-r58472
> Cc: linux usb devel
> Subject: Re: [linux-usb-devel] USB OTG ISR Registration
>
> If shared handlers were used, how did you mask the interrupts while servicing?
>
> If SA_SHIRQ is used, isn't it the responsibility of ISR to mask the
> interrupts at
If shared handlers were used, how did you mask the interrupts while servicing?
If SA_SHIRQ is used, isn't it the responsibility of ISR to mask the
interrupts at the starting, service the received interrupt and unmask
the interrupts before returning?
Or were you using SA_SHIRQ | SA_INTERRUPT?
If t
Actually we had done a driver for ARC OTG controller, which is still not very
stable. We used shared interrupt handlers.
Best Regards,
Leo
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Sujith
> Sankar
> Sent: Thursday, April 27, 2006 4:47 PM
>
