From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/3] genirq: Allow the irqchip state of an IRQ to be save/restored
Date: Fri, 06 Feb 2015 09:02:09 +0000 [thread overview]
Message-ID: <54D48311.7040305@arm.com> (raw)
In-Reply-To: <CAJAp7Oju0yD14Y53T7xC2D9oHUANyUs2BT42S4g=iJ1md76TGg@mail.gmail.com>
On 05/02/15 23:33, Bjorn Andersson wrote:
> On Wed, Jan 7, 2015 at 9:51 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>
>
> Any update on the status of this?
>
> I would like to be able to move ahead with the pinctrl driver for the
> Qualcomm PM8921 pmic, that depends on this being in place.
None so far.
Thomas, do you have any comment on this one?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2015-02-06 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 17:50 [PATCH v3 0/3] genirq: Saving/restoring the irqchip state of an irq line Marc Zyngier
2015-01-07 17:51 ` [PATCH v3 1/3] genirq: Allow the irqchip state of an IRQ to be save/restored Marc Zyngier
2015-02-05 23:33 ` Bjorn Andersson
2015-02-06 9:02 ` Marc Zyngier [this message]
2015-01-07 17:51 ` [PATCH v3 2/3] irqchip: GIC: Add support for irq_{get, set}_irqchip_state Marc Zyngier
2015-01-07 17:51 ` [PATCH v3 3/3] irqchip: GICv3: " Marc Zyngier
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=54D48311.7040305@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).