From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM: dts: rockchip: add veyron-minnie board
Date: Thu, 03 Dec 2015 15:00:33 +0100 [thread overview]
Message-ID: <2137537.DBrTyHZKX9@diego> (raw)
In-Reply-To: <566020EC.7060606@rock-chips.com>
Hi Caesar, Shawn,
Am Donnerstag, 3. Dezember 2015, 19:01:00 schrieb Caesar Wang:
> ? 2015?12?03? 18:44, Heiko St?bner ??:
> > Am Donnerstag, 3. Dezember 2015, 18:27:27 schrieb Caesar Wang:
> >> .....but,
> >> reboot long long test, that's seem mmc tune has a issue.
> >>
> >> 2.630892] mmcblk0: error -84 transferring data, sector 0, nr 8, cmd
> >>
> >> response 0x900, card status 0x0
> >> [ 2.631006] mmcblk0: error -110 sending status command, retrying
> >> [ 2.631018] mmcblk0: error -84 transferring data, sector 1, nr 7, cmd
> >> response 0x900, card status 0x0
> >> [ 2.631703] mmcblk0: unable to read partition table
> >> ...
> >
> > Could you try if what we do on Minnie fixes that error (disabling tuning
> > for now) - i.e. adding the following to the Mickey dts:
> >
> > &emmc {
> >
> > /delete-property/mmc-hs200-1_8v;
> >
> > };
>
> Yep, maybe we remove this node firstly but someone fix the emmc tune issues.
yep, that is definitly the plan. I've now also done more than a dozen reboot
tests on my brain board including running hdparm-speedtests on the emmc there.
Tuning and all reads did run without any hickups, so this really seems to be
somehow limited.
> >> Anyway, the dts is good to support mickey machine.
> >> I think the mmc tune is not prefect in mainline.
> >
> > yeah, it seems we still have some issues.
> >
> > Although it seems only the disney-mice seem affected ;-) [minnie and
> > mickey]. Pinky, Brain, Speedy, Jaq all seem to work somehow - at least I
> > haven't gotten any reports about that
>
> Cc shawn,
> Maybe, Shawn at RK has the interesting in debuging this issue.:-)
Strangely on the ChromeOS kernel tuning on Minnie seems to work ok. I already
checked the code somewhat and the core handling seems to be the same - like
the phase clocks and the tuning algorithm.
The only slight difference is that mainline is using mmc_send_tuning() instead
of building the packet by hand.
But at least on my Minnie the phases the emmc gets tuned to are always
differing somehow: (mainline: 216-218, chromeos: 198-201) while on my jerry
the variance is not as big (mainline 176, chromeos: 172).
Some more comparisons I did on Minnie:
sdmmc: phase 197 on both mainline and chromeos
wifi: around phase 214 on mainline and 204 on chromeos
So at least the sdmmc host seems pretty stable in its phase and the difference
on wifi is smaller than with the emmc - not sure if that helps though :-)
I'll also try to look more into that issue, but would be glad to hear other
bright ideas :-)
Thanks
Heiko
next prev parent reply other threads:[~2015-12-03 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 17:14 [PATCH 1/3] ARM: dts: rockchip: make sure edp_24m is associated to xin24m on veyron Heiko Stübner
2015-12-01 17:16 ` [PATCH 2/3] ARM: dts: rockchip: add veyron-brain board Heiko Stübner
2015-12-02 18:26 ` Brian Norris
2015-12-01 17:16 ` [PATCH 3/3] ARM: dts: rockchip: add veyron-minnie board Heiko Stübner
2015-12-01 17:19 ` Heiko Stübner
2015-12-02 18:31 ` Brian Norris
2015-12-03 10:27 ` Caesar Wang
2015-12-03 10:44 ` Heiko Stübner
2015-12-03 11:01 ` Caesar Wang
2015-12-03 14:00 ` Heiko Stübner [this message]
2015-12-03 15:43 ` [PATCH 1/3] ARM: dts: rockchip: make sure edp_24m is associated to xin24m on veyron Heiko Stübner
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=2137537.DBrTyHZKX9@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).