From: Maxime Ripard <maxime@cerno.tech>
To: Samuel Holland <samuel@sholland.org>
Cc: Marc Zyngier <maz@kernel.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Ondrej Jirman <megous@megous.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 00/10] sunxi: Support IRQ wakeup from deep sleep
Date: Fri, 22 Jan 2021 11:47:05 +0100 [thread overview]
Message-ID: <20210122104705.bo2x22ef56hdj26q@gilmour> (raw)
In-Reply-To: <08e9bc97-c18d-9b8f-28be-3892d77730bf@sholland.org>
[-- Attachment #1: Type: text/plain, Size: 2100 bytes --]
On Thu, Jan 21, 2021 at 07:33:54PM -0600, Samuel Holland wrote:
> On 1/21/21 2:35 PM, Marc Zyngier wrote:
> > On Sun, 17 Jan 2021 23:50:30 -0600, Samuel Holland wrote:
> >> Allwinner sun6i/sun8i/sun50i SoCs (A31 and newer) have two interrupt
> >> controllers: GIC and R_INTC. GIC does not support wakeup. R_INTC handles
> >> the external NMI pin, and provides 32+ IRQs to the ARISC. The first 16
> >> of these correspond 1:1 to a block of GIC IRQs starting with the NMI.
> >> The last 13-16 multiplex the first (up to) 128 GIC SPIs.
> >>
> >> This series replaces the existing chained irqchip driver that could only
> >> control the NMI, with a stacked irqchip driver that also provides wakeup
> >> capability for those multiplexed SPI IRQs. The idea is to preconfigure
> >> the ARISC's IRQ controller, and then the ARISC firmware knows to wake up
> >> as soon as it receives an IRQ. It can also decide how deep it can
> >> suspend based on the enabled wakeup IRQs.
> >>
> >> [...]
> >
> > Applied to irq/irqchip-5.12, thanks!
> >
> > [01/10] dt-bindings: irq: sun6i-r: Split the binding from sun7i-nmi
> > commit: ad6b47cdef760410311f41876b21eb0c6fda4717
> > [02/10] dt-bindings: irq: sun6i-r: Add a compatible for the H3
> > commit: 6436eb4417094ea3308b33d8392fc02a1068dc78
> > [03/10] irqchip/sun6i-r: Use a stacked irqchip driver
> > commit: 4e34614636b31747b190488240a95647c227021f
> > [04/10] irqchip/sun6i-r: Add wakeup support
> > commit: 7ab365f6cd6de1e2b0cb1e1e3873dbf68e6f1003
> >
> > Please route the dts patches via the soc tree. Also, I had to
> > manually fix the first patch as it wouldn't apply on top of
> > 5.11-rc4 (which tree has it been diffed against?). Please
> > check that the resolution is correct.
>
> This series was based on sunxi/for-next, which contains commit
> 752b0aac99c7 ("dt-bindings: irq: sun7i-nmi: Add binding documentation
> for the V3s NMI")[1].
I assume merging the DT bits alone would break things? If so, I guess we
can wait for 5.12 to be released before merging it
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2021-01-22 10:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 5:50 [PATCH v5 00/10] sunxi: Support IRQ wakeup from deep sleep Samuel Holland
2021-01-18 5:50 ` [PATCH v5 01/10] dt-bindings: irq: sun6i-r: Split the binding from sun7i-nmi Samuel Holland
2021-01-18 5:50 ` [PATCH v5 02/10] dt-bindings: irq: sun6i-r: Add a compatible for the H3 Samuel Holland
2021-01-18 5:50 ` [PATCH v5 03/10] irqchip/sun6i-r: Use a stacked irqchip driver Samuel Holland
2021-01-18 5:50 ` [PATCH v5 04/10] irqchip/sun6i-r: Add wakeup support Samuel Holland
2021-01-18 5:50 ` [PATCH v5 05/10] ARM: dts: sunxi: Rename nmi_intc to r_intc Samuel Holland
2021-01-18 5:50 ` [PATCH v5 06/10] ARM: dts: sunxi: Use the new r_intc binding Samuel Holland
2021-01-18 5:50 ` [PATCH v5 07/10] ARM: dts: sunxi: h3/h5: Add r_intc node Samuel Holland
2021-01-18 5:50 ` [PATCH v5 08/10] ARM: dts: sunxi: Move wakeup-capable IRQs to r_intc Samuel Holland
2021-01-18 5:50 ` [PATCH v5 09/10] arm64: dts: allwinner: Use the new r_intc binding Samuel Holland
2021-01-18 5:50 ` [PATCH v5 10/10] arm64: dts: allwinner: Move wakeup-capable IRQs to r_intc Samuel Holland
2021-01-21 20:35 ` [PATCH v5 00/10] sunxi: Support IRQ wakeup from deep sleep Marc Zyngier
2021-01-22 1:33 ` Samuel Holland
2021-01-22 10:47 ` Maxime Ripard [this message]
2021-01-23 6:26 ` Samuel Holland
2021-01-25 10:56 ` Maxime Ripard
2021-01-28 1:57 ` Chen-Yu Tsai
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=20210122104705.bo2x22ef56hdj26q@gilmour \
--to=maxime@cerno.tech \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=megous@megous.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=tglx@linutronix.de \
--cc=wens@csie.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).