mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre Torgue <alexandre.torgue@st.com>
To: Fabrice Gasnier <fabrice.gasnier@st.com>, <tglx@linutronix.de>,
	<jason@lakedaemon.net>, <maz@kernel.org>
Cc: <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Add STM32 LP timer EXTI interrupts
Date: Mon, 9 Nov 2020 11:54:00 +0100	[thread overview]
Message-ID: <c77e3222-85cf-a22f-3b9f-f081565a9243@st.com> (raw)
In-Reply-To: <1602859219-15684-1-git-send-email-fabrice.gasnier@st.com>

Hi Fabrice

On 10/16/20 4:40 PM, Fabrice Gasnier wrote:
> STM32 LP timer that's available on STM32MP15x can wakeup the platform
> using EXTI interrupts.
> 
> This series add:
> - LP timer EXTI - GIC interrupt events to EXTI driver and device-tree
> - LP timer wakeup-source to device-tree
> 
> Fabrice Gasnier (3):
>    irqchip/stm32-exti: Add all LP timer exti direct events support
>    ARM: dts: stm32: Add LP timer irqs on stm32mp151
>    ARM: dts: stm32: Add LP timer wakeup-source on stm32mp151
> 
>   arch/arm/boot/dts/stm32mp151.dtsi | 10 ++++++++++
>   drivers/irqchip/irq-stm32-exti.c  |  4 ++++
>   2 files changed, 14 insertions(+)
> 

DT patches applied on stm32-next.

thanks
alex

      parent reply	other threads:[~2020-11-09 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 14:40 Fabrice Gasnier
2020-10-16 14:40 ` [PATCH 1/3] irqchip/stm32-exti: Add all LP timer exti direct events support Fabrice Gasnier
2020-11-01 17:00   ` [tip: irq/urgent] " tip-bot2 for Fabrice Gasnier
2020-10-16 14:40 ` [PATCH 2/3] ARM: dts: stm32: Add LP timer irqs on stm32mp151 Fabrice Gasnier
2020-10-16 14:40 ` [PATCH 3/3] ARM: dts: stm32: Add LP timer wakeup-source " Fabrice Gasnier
2020-10-25 12:06 ` [PATCH 0/3] Add STM32 LP timer EXTI interrupts Marc Zyngier
2020-11-09 10:54 ` Alexandre Torgue [this message]

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=c77e3222-85cf-a22f-3b9f-f081565a9243@st.com \
    --to=alexandre.torgue@st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrice.gasnier@st.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=maz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tglx@linutronix.de \
    /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
all inboxes | Powered by JetHome®