From: Jerome Brunet <jbrunet@baylibre.com>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
Kevin Hilman <khilman@baylibre.com>
Subject: Re: eMMC tuning issue on Odroid C2 and a possible solution
Date: Thu, 12 Oct 2017 22:05:45 +0200 [thread overview]
Message-ID: <1507838745.16356.270.camel@baylibre.com> (raw)
In-Reply-To: <fa52e311-bafe-0a6a-1b85-ac8f40db62ed@gmail.com>
On Thu, 2017-10-12 at 21:49 +0200, Heiner Kallweit wrote:
> > The result of the tuning does not depends on starting point, so I don't
> > really
> > understand how it would significantly change things.
> >
>
> I think it depends on the tx phase starting point.
>
If the result of the tuning is not independent of the starting, instead of just
telling me, it is fairly easy for you to give actual result, like I asked you:
> > Ok, starting from Rx:0 Tx:270 then tuning gives you Tx:300 Rx:90
> > And what different did it gives you starting Rx:0/Tx:0 ?
And if the result are indeed vastly different, let's debug and get a real
explanation.
> Tuning does:
> rx phase tuning
> tx phase tuning
> rx phase tuning
>
> Result of each step depends on result of previous step.
Again, we don't agree.
> So also the initial
> rx phase tuning result depends on the starting point of tx phase.
The first Rx tuning is there only to get a sane starting point for the tx tuning
,as explained in the code. This is the reason why is not done when re-tuning.
next prev parent reply other threads:[~2017-10-12 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 20:46 eMMC tuning issue on Odroid C2 and a possible solution Heiner Kallweit
2017-10-12 15:22 ` Jerome Brunet
2017-10-12 18:17 ` Heiner Kallweit
2017-10-12 19:34 ` Jerome Brunet
2017-10-12 19:49 ` Heiner Kallweit
2017-10-12 20:05 ` Jerome Brunet [this message]
2017-10-12 20:29 ` Heiner Kallweit
2017-10-12 20:59 ` Jerome Brunet
2017-10-12 21:04 ` Heiner Kallweit
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=1507838745.16356.270.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=hkallweit1@gmail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-mmc@vger.kernel.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