From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
Date: Tue, 27 Mar 2018 17:10:02 -0700 [thread overview]
Message-ID: <7htvt1oyat.fsf@baylibre.com> (raw)
In-Reply-To: <20180327062714.GB28908@kroah.com> (Greg KH's message of "Tue, 27 Mar 2018 08:27:14 +0200")
Greg KH <gregkh@linuxfoundation.org> writes:
> On Mon, Mar 26, 2018 at 01:23:44PM -0700, Kevin Hilman wrote:
>> On Fri, Mar 2, 2018 at 5:44 AM, Jerome Brunet <jbrunet@baylibre.com> wrote:
>> > Different modules maybe installed by the user on the eMMC connector
>> > of the odroid-c2. While the red modules are working without an issue,
>> > it seems some black modules (apparently Samsung based) are having
>> > issue at 200MHz
>> >
>> > While the tuning algorithm introduced in v4.14 enables high speed modes
>> > on every other tested designs, it seems a problem remains for this
>> > particular combination of board and eMMC module.
>> >
>> > Lowering the maximum frequency of the eMMC on this board until we can
>> > figure out a better solution.
>> >
>> > Fixes: d341ca88eead ("mmc: meson-gx: rework tuning function")
>> > Suggested-by: Ellie Reeves <ellierevves@gmail.com>
>> > Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
>>
>> Now in mainline as commit c04ffa71ff49 upstream.
>
> Really? I do not see it in Linus's tree, are you sure about that?
>
> $ git show c04ffa71ff49
> fatal: ambiguous argument 'c04ffa71ff49': unknown revision or path not in the working tree.
Oops, you're right. It's still in arm-soc, not yet in mainline. Sorry
for the noise.
Kevin
prev parent reply other threads:[~2018-03-28 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 13:44 [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate Jerome Brunet
2018-03-08 1:24 ` Kevin Hilman
2018-03-26 20:23 ` Kevin Hilman
2018-03-27 6:27 ` Greg KH
2018-03-28 0:10 ` Kevin Hilman [this message]
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=7htvt1oyat.fsf@baylibre.com \
--to=khilman@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