From: "Inès Varhol" <ines.varhol@telecom-paris.fr>
To: qemu-devel@nongnu.org
Cc: "Arnaud Minier" <arnaud.minier@telecom-paris.fr>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-arm@nongnu.org, "Inès Varhol" <ines.varhol@telecom-paris.fr>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: [PATCH v2 0/3] Connect STM32L4x5 USART devices to the EXTI
Date: Wed, 22 May 2024 22:39:37 +0200 [thread overview]
Message-ID: <20240522204020.203905-1-ines.varhol@telecom-paris.fr> (raw)
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 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>
Inès Varhol (3):
hw/misc: In STM32L4x5 EXTI, consolidate 2 constants
hw/misc: In STM32L4x5 EXTI, handle direct and configurable interrupts
hw/arm: In STM32L4x5 SOC, connect USART devices to EXTI
include/hw/misc/stm32l4x5_exti.h | 6 ++++--
hw/arm/stm32l4x5_soc.c | 24 +++++++++++-------------
hw/misc/stm32l4x5_exti.c | 31 ++++++++++++++++++++++---------
3 files changed, 37 insertions(+), 24 deletions(-)
--
2.43.2
next reply other threads:[~2024-05-22 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 20:39 Inès Varhol [this message]
2024-05-22 20:39 ` [PATCH v2 1/3] hw/misc: In STM32L4x5 EXTI, consolidate 2 constants Inès Varhol
2024-05-22 20:39 ` [PATCH v2 2/3] hw/misc: In STM32L4x5 EXTI, handle direct and configurable interrupts Inès Varhol
2024-05-28 14:33 ` Peter Maydell
2024-05-22 20:39 ` [PATCH v2 3/3] hw/arm: In STM32L4x5 SOC, connect USART devices to EXTI Inès Varhol
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=20240522204020.203905-1-ines.varhol@telecom-paris.fr \
--to=ines.varhol@telecom-paris.fr \
--cc=arnaud.minier@telecom-paris.fr \
--cc=peter.maydell@linaro.org \
--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).