From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Cc: "Pekka Enberg" <penberg@iki.fi>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Andrew Baumann" <Andrew.Baumann@microsoft.com>,
"patches@linaro.org" <patches@linaro.org>
Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH for-2.12 0/2] bcm2835_sdhost: fix interrupt handling
Date: Wed, 4 Apr 2018 11:18:23 +0100 [thread overview]
Message-ID: <CAFEAcA8trs8tMKBqbOLaNx4OR9H9+xO4jJQjY2+yeCNdsdCBCA@mail.gmail.com> (raw)
In-Reply-To: <20180319161556.16446-1-peter.maydell@linaro.org>
Ping for code review, please? It would be nice if our 'raspi3'
model for 2.12 was one we could say actually booted a known
Linux image...
thanks
-- PMM
On 19 March 2018 at 16:15, Peter Maydell <peter.maydell@linaro.org> wrote:
> This patchset fixes the code in the bcm2835_sdhost device
> so that it raises interrupts in more plausible places.
>
> The Linux bcm2835_sdhost driver doesn't work on QEMU at the moment,
> because our model raises spurious data interrupts. Our function
> bcm2835_sdhost_fifo_run() will flag an interrupt any time it is
> called with s->datacnt == 0, even if the host hasn't actually issued
> a data read or write command yet. This means that the driver gets a
> spurious data interrupt as soon as it enables IRQs and then does
> something else that causes us to call the fifo_run routine, like
> writing to SDHCFG, and before it does the write to SDCMD to issue the
> read. The driver's IRQ handler then spins forever complaining that
> there's no data and the SD controller isn't in a state where there's
> going to be any data:
>
> [ 41.040738] sdhost-bcm2835 3f202000.mmc: fsm 1, hsts 00000000
> [ 41.042059] sdhost-bcm2835 3f202000.mmc: fsm 1, hsts 00000000
> (continues forever).
>
> Move the interrupt flag setting to more plausible places:
> * for BUSY, raise this as soon as a BUSYWAIT command has executed
> * for DATA, raise this when the FIFO has any space free (for a write)
> or any data in it (for a read)
> * for BLOCK, raise this when the data count is 0 and we've
> actually done some reading or writing
>
> This is pure guesswork since the documentation for this hardware is
> not public, but it is sufficient to get the Linux bcm2835_sdhost
> driver to work.
>
> If anybody has other OSes than Linux that use the sdhost SD
> controller (not the 'Arasan' one, which is a different bit of
> the SoC) testing with those would be appreciated. If anybody
> has documentation for this hardware that would be even better.
>
> With these patches plus the previous set, I can get the Debian
> raspi3 image to boot (though there are a lot of warnings relating
> to the pl011 UART for some reason).
>
> thanks
> -- PMM
>
> Peter Maydell (2):
> hw/sd/bcm2835_sdhost: Add tracepoints
> hw/sd/bcm2835_sdhost: Don't raise spurious interrupts
>
> hw/sd/bcm2835_sdhost.c | 51 +++++++++++++++++++++++++++++++-------------------
> hw/sd/trace-events | 6 ++++++
> 2 files changed, 38 insertions(+), 19 deletions(-)
>
> --
> 2.16.2
next prev parent reply other threads:[~2018-04-04 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 16:15 [Qemu-devel] [PATCH for-2.12 0/2] bcm2835_sdhost: fix interrupt handling Peter Maydell
2018-03-19 16:15 ` [Qemu-devel] [PATCH for-2.12 1/2] hw/sd/bcm2835_sdhost: Add tracepoints Peter Maydell
2018-04-04 11:42 ` Philippe Mathieu-Daudé
2018-04-04 11:54 ` Peter Maydell
2018-04-04 13:44 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2018-03-19 16:15 ` [Qemu-devel] [PATCH for-2.12 2/2] hw/sd/bcm2835_sdhost: Don't raise spurious interrupts Peter Maydell
2018-03-19 16:34 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2018-04-04 11:50 ` [Qemu-devel] " Philippe Mathieu-Daudé
2018-04-04 11:57 ` Peter Maydell
2018-04-04 13:50 ` Philippe Mathieu-Daudé
2018-04-04 10:18 ` Peter Maydell [this message]
2018-04-04 14:25 ` [Qemu-devel] [Qemu-arm] [PATCH for-2.12 0/2] bcm2835_sdhost: fix interrupt handling Gerd Hoffmann
2018-04-05 12:34 ` Peter Maydell
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=CAFEAcA8trs8tMKBqbOLaNx4OR9H9+xO4jJQjY2+yeCNdsdCBCA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=Andrew.Baumann@microsoft.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=patches@linaro.org \
--cc=penberg@iki.fi \
--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).