qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Pekka Enberg <penberg@iki.fi>
Subject: Re: [Qemu-devel] [RFC PATCH] hw: arm: Add basic support for cprman (clock subsystem)
Date: Mon, 16 Jul 2018 15:22:50 -0700	[thread overview]
Message-ID: <20180716222250.GA20320@roeck-us.net> (raw)
In-Reply-To: <CAFEAcA_Vd46APz_czOP+OfB1nkGvGjuf=EPbB57TkkXKWkNxwQ@mail.gmail.com>

On Mon, Jul 16, 2018 at 03:07:13PM +0100, Peter Maydell wrote:
> On 16 July 2018 at 14:51, Guenter Roeck <linux@roeck-us.net> wrote:
> > In this context, I can't get mmc to work with ToT Linux on raspi3.
> >
> > / # mount /dev/mmcblk0 /mnt
> > [   47.099074] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware
> > interrupt.
> > [   57.339803] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware
> > interrupt.
> > [   57.390449] mmc0: Problem switching card into high-speed mode!
> > [   67.581559] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware
> > interrupt.
> > [   67.587832] print_req_error: I/O error, dev mmcblk0, sector 2
> > [   67.588908] Buffer I/O error on dev mmcblk0, logical block 1, lost sync
> > page write
> > [   67.610307] EXT4-fs (mmcblk0): I/O error while writing superblock
> > [   67.620842] EXT4-fs (mmcblk0): mount failed
> > [   77.819114] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware
> > interrupt.
> > [   88.058917] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware
> > interrupt.
> > [   98.298937] sdhost-bcm2835 3f202000.mmc: timeout waiting for hardware
> > interrupt.
> > [   98.303554] print_req_error: I/O error, dev mmcblk0, sector 2
> > [   98.306044] Buffer I/O error on dev mmcblk0, logical block 1, lost sync
> > page write
> >
> > Any idea what the problem might be ?
> 
> Same thing again -- no hardware documentation for that sd controller.
> We took our best guess about what the behaviour is supposed to be
> for raising hardware interrupts in commit f3d9fe8f959643 earlier
> this year, but that was (as the commit message notes) pure guesswork
> based largely on what the Linux driver was doing. Somebody would have
> to look at what exactly this version of the kernel is expecting the
> hardware to do and try to reverse-engineer what the model needs to do
> that it isn't currently...
> 

This failed for me with all kernel versions I tried, starting with 4.14.y.

I'll send a patch in a minute. It is just as much guesswork as before,
but AFAICS it does work.

Guenter

  reply	other threads:[~2018-07-16 22:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15 22:06 [Qemu-devel] [RFC PATCH] hw: arm: Add basic support for cprman (clock subsystem) Guenter Roeck
2018-07-16  9:08 ` Peter Maydell
2018-07-16 13:51   ` Guenter Roeck
2018-07-16 14:07     ` Peter Maydell
2018-07-16 22:22       ` Guenter Roeck [this message]
2018-07-16 14:33 ` Peter Maydell
2018-07-16 16:14   ` Guenter Roeck
2018-07-17  1:53 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2018-07-17  4:07   ` Guenter Roeck
2018-10-10 13:25     ` Philippe Mathieu-Daudé
2018-10-10 15:02       ` Guenter Roeck

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=20180716222250.GA20320@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=penberg@iki.fi \
    --cc=peter.maydell@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).