From: Peter Maydell <peter.maydell@linaro.org>
To: "Inès Varhol" <ines.varhol@telecom-paris.fr>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
"Alistair Francis" <alistair@alistair23.me>,
"Arnaud Minier" <arnaud.minier@telecom-paris.fr>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v3 0/3] Connect STM32L4x5 USART devices to the EXTI
Date: Mon, 8 Jul 2024 15:51:06 +0100 [thread overview]
Message-ID: <CAFEAcA9MDLPAqQWMADPupSJmheHuCPUnf+9Uebrt9x+ikZmRaA@mail.gmail.com> (raw)
In-Reply-To: <20240707085927.122867-1-ines.varhol@telecom-paris.fr>
On Sun, 7 Jul 2024 at 09:59, Inès Varhol <ines.varhol@telecom-paris.fr> wrote:
>
> STM32L4x5 EXTI was handling only configurable interrupts
> (such as those coming from STM32L4x5 SYSCFG which was the
> only device connected to the EXTI).
> This patch adds support for direct line interrupts and
> connects the existing STM32L4x5 USART devices to the EXTI.
> The patch also corrects the handling of configurable line
> interrupts in the EXTI.
>
> Changes from v2 (2nd commit):
> - The 2nd commit was split, part of the changes went in
> another patch correcting EXTI configurable interrupts.
> Stayed in the commit only changes relevant to direct interrupts.
>
> Changes from v1 (2nd commit):
> - add STM32L4x5 EXTI status fields `irq_levels` to track
> configurable irq levels and do edge detection
> - use `qemu_set_irq` instead of qemu_irq_raise/lower
>
> Signed-off-by: Inès Varhol <ines.varhol@telecom-paris.fr>
Applied to target-arm.next, thanks.
-- PMM
prev parent reply other threads:[~2024-07-08 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-07 8:58 [PATCH v3 0/3] Connect STM32L4x5 USART devices to the EXTI Inès Varhol
2024-07-07 8:58 ` [PATCH v3 1/3] hw/misc: In STM32L4x5 EXTI, consolidate 2 constants Inès Varhol
2024-07-07 8:58 ` [PATCH v3 2/3] hw/misc: In STM32L4x5 EXTI, handle direct interrupts Inès Varhol
2024-07-07 8:58 ` [PATCH v3 3/3] hw/arm: In STM32L4x5 SOC, connect USART devices to EXTI Inès Varhol
2024-07-08 14:51 ` Peter Maydell [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=CAFEAcA9MDLPAqQWMADPupSJmheHuCPUnf+9Uebrt9x+ikZmRaA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alistair@alistair23.me \
--cc=arnaud.minier@telecom-paris.fr \
--cc=ines.varhol@telecom-paris.fr \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).