On 14/09/15 11:57, Daniel Baluta wrote:
> On Sat, Sep 12, 2015 at 12:14 PM, Jonathan Cameron wrote:
>> On 11/09/15 14:59, Cristina Opriceana wrote:
>>> Enhance interrupt generation in the dummy driver and expand its usage
>>> by introducing the irq_work infrastructure to trigger an interrupt.
>>>
On Sat, Sep 12, 2015 at 12:14 PM, Jonathan Cameron wrote:
> On 11/09/15 14:59, Cristina Opriceana wrote:
>> Enhance interrupt generation in the dummy driver and expand its usage
>> by introducing the irq_work infrastructure to trigger an interrupt.
>>
>> This way, the irq_work_queue() wrapper perm
On 11/09/15 14:59, Cristina Opriceana wrote:
> Enhance interrupt generation in the dummy driver and expand its usage
> by introducing the irq_work infrastructure to trigger an interrupt.
>
> This way, the irq_work_queue() wrapper permits calling both of the top
> half and threaded part from a hard
Enhance interrupt generation in the dummy driver and expand its usage
by introducing the irq_work infrastructure to trigger an interrupt.
This way, the irq_work_queue() wrapper permits calling both of the top
half and threaded part from a hard irq context, unlike handle_nested_irq(),
which only ca
4 matches
Mail list logo