From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH/RFT] mmc: meson-gx: include tx phase in the tuning process
Date: Wed, 27 Sep 2017 18:24:20 +0200 [thread overview]
Message-ID: <1506529460.16686.45.camel@baylibre.com> (raw)
In-Reply-To: <d9c99f1e-bfe4-cdf7-bbfa-fc54837552e2@gmail.com>
On Tue, 2017-09-19 at 20:54 +0200, Heiner Kallweit wrote:
> > > Unfortunately this still doesn't fix the issue here.
> > > Tuning rx and tx clk sequentially assumes both are independent, what they
> > > IMHO are not. So meybe we have to check all combinations of rx/tx clk
> > > phase.
> >
> > Interesting, I would be curious to know what tuning value you ended with,
> > compared to the "hard-coded' working value you have set.
> >
> > You can get that fairly easily now, using CCF in debugfs, in
> > <debugfs>/clk/clk_summary, the different phase are reported
> >
>
> This gives me:
>
> core phase: 180
> rx phase: 0
> tx phase: 270
>
> And I end up with a corrupted root file system.
You should have had tuning on both the Rx and Tx phase and yet, you end up with
the default values ... that's strange
I should be able to get my hands on 16GB emmc module for this platform soon.
Let's see ...
next prev parent reply other threads:[~2017-09-27 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 13:14 Problems after recent changes to meson-gx-mmc driver Heiner Kallweit
2017-09-09 14:05 ` Jerome Brunet
2017-09-09 19:53 ` Heiner Kallweit
2017-09-09 20:20 ` Heiner Kallweit
2017-09-10 15:08 ` Jerome Brunet
2017-09-10 16:20 ` Heiner Kallweit
2017-09-10 16:48 ` Jerome Brunet
2017-09-18 13:44 ` [PATCH/RFT] mmc: meson-gx: include tx phase in the tuning process Jerome Brunet
2017-09-18 19:11 ` Heiner Kallweit
2017-09-19 11:08 ` Jerome Brunet
2017-09-19 18:54 ` Heiner Kallweit
2017-09-27 16:24 ` Jerome Brunet [this message]
2017-10-02 12:30 ` Jerome Brunet
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=1506529460.16686.45.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--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;
as well as URLs for NNTP newsgroup(s).