Re: recommended use of request_any_context_irq()

On Thu, Sep 22, 2016 at 5:03 PM, Thomas Gleixner wrote: > Leo, > > On Thu, 22 Sep 2016, Leo Li wrote: >> core code. And my concerns is that there are other drivers can hit >> the same problem if connected to the threaded interrupt controller. >> What can we do prevent similar

Re: recommended use of request_any_context_irq()

On Thu, Sep 22, 2016 at 5:03 PM, Thomas Gleixner wrote: > Leo, > > On Thu, 22 Sep 2016, Leo Li wrote: >> core code. And my concerns is that there are other drivers can hit >> the same problem if connected to the threaded interrupt controller. >> What can we do prevent similar problem in the

Re: recommended use of request_any_context_irq()

Leo, On Thu, 22 Sep 2016, Leo Li wrote: > core code. And my concerns is that there are other drivers can hit > the same problem if connected to the threaded interrupt controller. > What can we do prevent similar problem in the future? The simplest way is to be more informative in the failure

Re: recommended use of request_any_context_irq()

Leo, On Thu, 22 Sep 2016, Leo Li wrote: > core code. And my concerns is that there are other drivers can hit > the same problem if connected to the threaded interrupt controller. > What can we do prevent similar problem in the future? The simplest way is to be more informative in the failure

Re: recommended use of request_any_context_irq()

On Thu, Sep 22, 2016 at 3:47 PM, Thomas Gleixner wrote: > On Thu, 22 Sep 2016, Leo Li wrote: >> On Thu, Sep 22, 2016 at 3:10 AM, Marc Zyngier wrote: >> > There is strictly no reason to perform a blanket change of all the >> > drivers. What would be the

Re: recommended use of request_any_context_irq()

On Thu, Sep 22, 2016 at 3:47 PM, Thomas Gleixner wrote: > On Thu, 22 Sep 2016, Leo Li wrote: >> On Thu, Sep 22, 2016 at 3:10 AM, Marc Zyngier wrote: >> > There is strictly no reason to perform a blanket change of all the >> > drivers. What would be the reason to change them other than to cater

Re: recommended use of request_any_context_irq()

On Thu, 22 Sep 2016, Leo Li wrote: > On Thu, Sep 22, 2016 at 3:10 AM, Marc Zyngier wrote: > > There is strictly no reason to perform a blanket change of all the > > drivers. What would be the reason to change them other than to cater for > > a contrived use case that may

Re: recommended use of request_any_context_irq()

On Thu, 22 Sep 2016, Leo Li wrote: > On Thu, Sep 22, 2016 at 3:10 AM, Marc Zyngier wrote: > > There is strictly no reason to perform a blanket change of all the > > drivers. What would be the reason to change them other than to cater for > > a contrived use case that may never happen? > > Maybe

Re: recommended use of request_any_context_irq()

On Thu, Sep 22, 2016 at 3:10 AM, Marc Zyngier wrote: > Leo, > > On 21/09/16 22:14, Leo Li wrote: >> Hi Marc and Thomas, >> >> With the introduction of request_any_context_irq() routine, driver can >> deal with interrupt controllers using either threaded irq or normal >> irq.

Re: recommended use of request_any_context_irq()

On Thu, Sep 22, 2016 at 3:10 AM, Marc Zyngier wrote: > Leo, > > On 21/09/16 22:14, Leo Li wrote: >> Hi Marc and Thomas, >> >> With the introduction of request_any_context_irq() routine, driver can >> deal with interrupt controllers using either threaded irq or normal >> irq. But I don't see many

Re: recommended use of request_any_context_irq()

On Thu, 22 Sep 2016, Marc Zyngier wrote: > On 21/09/16 22:14, Leo Li wrote: > > Hi Marc and Thomas, > > > > With the introduction of request_any_context_irq() routine, driver can > > deal with interrupt controllers using either threaded irq or normal > > irq. But I don't see many drivers that

Re: recommended use of request_any_context_irq()

On Thu, 22 Sep 2016, Marc Zyngier wrote: > On 21/09/16 22:14, Leo Li wrote: > > Hi Marc and Thomas, > > > > With the introduction of request_any_context_irq() routine, driver can > > deal with interrupt controllers using either threaded irq or normal > > irq. But I don't see many drivers that

Re: recommended use of request_any_context_irq()

Leo, On 21/09/16 22:14, Leo Li wrote: > Hi Marc and Thomas, > > With the introduction of request_any_context_irq() routine, driver can > deal with interrupt controllers using either threaded irq or normal > irq. But I don't see many drivers that have been changed to use this > function to

Re: recommended use of request_any_context_irq()

Leo, On 21/09/16 22:14, Leo Li wrote: > Hi Marc and Thomas, > > With the introduction of request_any_context_irq() routine, driver can > deal with interrupt controllers using either threaded irq or normal > irq. But I don't see many drivers that have been changed to use this > function to

recommended use of request_any_context_irq()

Hi Marc and Thomas, With the introduction of request_any_context_irq() routine, driver can deal with interrupt controllers using either threaded irq or normal irq. But I don't see many drivers that have been changed to use this function to request interrupt. For on-board devices, the driver

recommended use of request_any_context_irq()

Hi Marc and Thomas, With the introduction of request_any_context_irq() routine, driver can deal with interrupt controllers using either threaded irq or normal irq. But I don't see many drivers that have been changed to use this function to request interrupt. For on-board devices, the driver