[lkml]   [2015]   [Apr]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v4 1/3] genirq: Allow the irqchip state of an IRQ to be save/restored

On 08/04/15 18:48, Bjorn Andersson wrote:
> On Wed, Mar 18, 2015 at 4:01 AM, Marc Zyngier <> wrote:
>> There is a number of cases where a kernel subsystem may want to
>> introspect the state of an interrupt at the irqchip level:
>> - When a peripheral is shared between virtual machines,
>> its interrupt state becomes part of the guest's state,
>> and must be switched accordingly. KVM on arm/arm64 requires
>> this for its guest-visible timer
>> - Some GPIO controllers seem to require peeking into the
>> interrupt controller they are connected to to report
>> their internal state
>> This seem to be a pattern that is common enough for the core code
>> to try and support this without too many horrible hacks. Introduce
>> a pair of accessors (irq_get_irqchip_state/irq_set_irqchip_state)
>> to retrieve the bits that can be of interest to another subsystem:
>> pending, active, and masked.
>> - irq_get_irqchip_state returns the state of the interrupt according
>> - irq_set_irqchip_state similarly sets the state of the interrupt.
>> Reviewed-by: Bjorn Andersson <>
>> Tested-by: Bjorn Andersson <>
>> Signed-off-by: Marc Zyngier <>
>> ---
> Sorry for bothering you Thomas, but we have a couple of driver for the
> Qualcomm platforms that depends on this patch (the line level part).


Couple of Qualcomm board support are left incomplete due to missing
drivers using these patches.
Would be nice to get this patch mainlined sooner.


> Could you please have a look at it?
> Thanks,
> Bjorn
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in
> the body of a message to
> More majordomo info at

 \ /
  Last update: 2015-04-13 19:01    [W:0.067 / U:21.620 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site