From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/3] genirq: Allow the irqchip state of an IRQ to be save/restored
Date: Mon, 13 Apr 2015 17:21:18 +0100 [thread overview]
Message-ID: <552BECFE.6040403@arm.com> (raw)
In-Reply-To: <552BEC41.3080909@linaro.org>
On 13/04/15 17:18, Srinivas Kandagatla wrote:
>
>
> On 08/04/15 18:48, Bjorn Andersson wrote:
>> On Wed, Mar 18, 2015 at 4:01 AM, Marc Zyngier <marc.zyngier@arm.com> 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
>>> to a parameter set to IRQCHIP_STATE_PENDING, IRQCHIP_STATE_ACTIVE,
>>> IRQCHIP_STATE_MASKED or IRQCHIP_STATE_LINE_LEVEL.
>>> - irq_set_irqchip_state similarly sets the state of the interrupt.
>>>
>>> Reviewed-by: Bjorn Andersson <bjorn.andersson@sonymobile.com>
>>> Tested-by: Bjorn Andersson <bjorn.andersson@sonymobile.com>
>>> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
>>> ---
>>
>> 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).
>
> +1
>
> Couple of Qualcomm board support are left incomplete due to missing
> drivers using these patches.
> Would be nice to get this patch mainlined sooner.
These patches are already in -next. Should everything go according to
plan, they should hit 4.1.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-04-13 16:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 11:01 [PATCH v4 0/3] genirq: Saving/restoring the irqchip state of an irq line Marc Zyngier
2015-03-18 11:01 ` [PATCH v4 1/3] genirq: Allow the irqchip state of an IRQ to be save/restored Marc Zyngier
2015-04-08 17:48 ` Bjorn Andersson
2015-04-13 16:18 ` Srinivas Kandagatla
2015-04-13 16:21 ` Marc Zyngier [this message]
2015-03-18 11:01 ` [PATCH v4 2/3] irqchip: GIC: Add support for irq_{get, set}_irqchip_state Marc Zyngier
2015-05-13 2:25 ` Feng Kan
2015-05-13 11:58 ` Linus Walleij
2015-05-13 15:44 ` Feng Kan
2015-05-14 10:32 ` Linus Walleij
2015-05-14 20:14 ` Feng Kan
2015-05-19 8:40 ` Linus Walleij
2015-05-19 10:01 ` [PATCH v4 2/3] irqchip: GIC: Add support for irq_{get,set}_irqchip_state Marc Zyngier
2015-05-19 15:01 ` [PATCH v4 2/3] irqchip: GIC: Add support for irq_{get, set}_irqchip_state Linus Walleij
2015-05-19 21:45 ` Feng Kan
2015-05-20 7:58 ` [PATCH v4 2/3] irqchip: GIC: Add support for irq_{get,set}_irqchip_state Marc Zyngier
2015-03-18 11:01 ` [PATCH v4 3/3] irqchip: GICv3: Add support for irq_{get, set}_irqchip_state Marc Zyngier
2015-04-13 14:12 ` [PATCH v4 0/3] genirq: Saving/restoring the irqchip state of an irq line Eric Auger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=552BECFE.6040403@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).