qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH 03/11] hw/sd/omap_mmc: Convert output qemu_irqs to gpio and sysbus IRQ APIs
Date: Tue, 28 Jan 2025 10:58:22 -0800	[thread overview]
Message-ID: <429db883-84b4-4486-9789-132d13e4d4dc@linaro.org> (raw)
In-Reply-To: <20250128104519.3981448-4-peter.maydell@linaro.org>

On 1/28/25 02:45, Peter Maydell wrote:
> The omap_mmc device has three outbound qemu_irq lines:
>   * one actual interrupt line
>   * two which connect to the DMA controller and are signalled for
>     TX and RX DMA
> 
> Convert these to a sysbus IRQ and two named GPIO outputs.
> 
> Signed-off-by: Peter Maydell<peter.maydell@linaro.org>
> ---
>   hw/sd/omap_mmc.c | 20 +++++++++++++-------
>   1 file changed, 13 insertions(+), 7 deletions(-)

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

r~


  reply	other threads:[~2025-01-28 18:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28 10:45 [PATCH 00/11] hw/sd: QOMify omap-mmc, remove legacy APIs Peter Maydell
2025-01-28 10:45 ` [PATCH 01/11] hw/sd/omap_mmc: Do a minimal conversion to QDev Peter Maydell
2025-01-28 18:50   ` Richard Henderson
2025-01-28 20:13     ` Peter Maydell
2025-01-30 22:30   ` Philippe Mathieu-Daudé
2025-01-28 10:45 ` [PATCH 02/11] hw/sd/omap_mmc: Convert remaining 'struct omap_mmc_s' uses to OMAPMMCState Peter Maydell
2025-01-28 18:51   ` Richard Henderson
2025-01-30 22:05   ` Philippe Mathieu-Daudé
2025-01-28 10:45 ` [PATCH 03/11] hw/sd/omap_mmc: Convert output qemu_irqs to gpio and sysbus IRQ APIs Peter Maydell
2025-01-28 18:58   ` Richard Henderson [this message]
2025-01-30 22:06   ` Philippe Mathieu-Daudé
2025-01-28 10:45 ` [PATCH 04/11] hw/sd/omap_mmc: Convert to SDBus API Peter Maydell
2025-01-30 22:26   ` Philippe Mathieu-Daudé
2025-01-31 10:22     ` Peter Maydell
2025-01-28 10:45 ` [PATCH 05/11] hw/sd/omap_mmc: Use similar API for "wire up omap_clk" to other OMAP devices Peter Maydell
2025-01-30 22:09   ` Philippe Mathieu-Daudé
2025-01-28 10:45 ` [PATCH 06/11] hw/arm/omap1: Inline creation of MMC Peter Maydell
2025-01-28 19:04   ` Richard Henderson
2025-01-30 22:11   ` Philippe Mathieu-Daudé
2025-01-28 10:45 ` [PATCH 07/11] hw/sd/omap_mmc: Remove unused coverswitch qemu_irq Peter Maydell
2025-01-28 19:04   ` Richard Henderson
2025-01-30 22:14   ` Philippe Mathieu-Daudé
2025-01-28 10:45 ` [PATCH 08/11] hw/sd/omap_mmc: Untabify Peter Maydell
2025-01-28 19:04   ` Richard Henderson
2025-01-30 22:14   ` Philippe Mathieu-Daudé
2025-01-28 10:45 ` [PATCH 09/11] hw/sd: Remove unused 'enable' method from SDCardClass Peter Maydell
2025-01-28 19:06   ` Richard Henderson
2025-01-29  7:36   ` Philippe Mathieu-Daudé
2025-01-28 10:45 ` [PATCH 10/11] hw/sd: Remove unused legacy functions, stop killing mammoths Peter Maydell
2025-01-28 19:10   ` Richard Henderson
2025-01-30 22:21   ` Philippe Mathieu-Daudé
2025-01-31  7:52   ` Markus Armbruster
2025-01-28 10:45 ` [PATCH 11/11] hw/sd: Remove unused SDState::enable Peter Maydell
2025-01-28 19:13   ` Richard Henderson
2025-01-30 22:15   ` Philippe Mathieu-Daudé
2025-01-31 17:01 ` [PATCH 00/11] hw/sd: QOMify omap-mmc, remove legacy APIs Philippe Mathieu-Daudé

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=429db883-84b4-4486-9789-132d13e4d4dc@linaro.org \
    --to=richard.henderson@linaro.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).