From: linus.luessing@c0d3.blue (Linus Lüssing)
To: linus-amlogic@lists.infradead.org
Subject: [RFC PATCH] ARM: dts: meson8b-odroidc1: add microSD support
Date: Sat, 17 Mar 2018 18:11:25 +0100 [thread overview]
Message-ID: <20180317171125.GK2681@otheros> (raw)
In-Reply-To: <CAFBinCDZCkrB2aWvjtwaF-DSa5Zs_gmDKei_+wB4g3nxau8kbg@mail.gmail.com>
Hi Martin,
Sorry for the late reply.
On Mon, Mar 12, 2018 at 10:00:17PM +0100, Martin Blumenstingl wrote:
> >> Not sure whether this error message could potentially point to some
> >> error in the changes in here.
> > these errors may be a problem with the meson-mx-sdio (MMC) driver
> > can you please show the output of /sys/kernel/debug/mmc0/ios ?
> some users on IRC have successfully tested this patch (together with
> the two patches from my series which fix the GPIO handling)
> can you please re-send this patch so Kevin can queue it for the next
> development cycle?
Glad to hear! I also just retried it with a 4.16-rc5 kernel and
your latest fixes and microSD still works for me, too :-).
Regarding the error message, I can't reproduce it anymore. With
the 4.16-rc5 kernel I did not see it. Nevertheless, here's the
output of mmc/ios:
-----
$ cat /sys/kernel/debug/mmc0/ios
clock: 50000000 Hz
actual clock: 39843750 Hz
vdd: 21 (3.3 ~ 3.4 V)
bus mode: 2 (push-pull)
chip select: 0 (don't care)
power mode: 2 (on)
bus width: 2 (4 bits)
timing spec: 2 (sd high-speed)
signal voltage: 0 (3.30 V)
driver type: 0 (driver type B)
-----
Out of curiousity, is the "actual clock" supposed to be so
much lower than "clock"?
Anyway, will resend the patch without the "RFC" now.
Regards, Linus
next prev parent reply other threads:[~2018-03-17 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 4:23 [RFC PATCH] ARM: dts: meson8b-odroidc1: add microSD support Linus Lüssing
2018-01-28 20:33 ` Martin Blumenstingl
2018-03-12 21:00 ` Martin Blumenstingl
2018-03-17 17:11 ` Linus Lüssing [this message]
2018-03-18 23:00 ` Martin Blumenstingl
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=20180317171125.GK2681@otheros \
--to=linus.luessing@c0d3.blue \
--cc=linus-amlogic@lists.infradead.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