From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
Date: Wed, 07 Mar 2018 17:24:43 -0800 [thread overview]
Message-ID: <7hy3j3fjfo.fsf@baylibre.com> (raw)
In-Reply-To: <20180302134436.18844-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Fri, 2 Mar 2018 14:44:36 +0100")
Jerome Brunet <jbrunet@baylibre.com> writes:
> 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>
Applied to v4.17/dt64 and Cc'd to stable,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@baylibre.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
Date: Wed, 07 Mar 2018 17:24:43 -0800 [thread overview]
Message-ID: <7hy3j3fjfo.fsf@baylibre.com> (raw)
In-Reply-To: <20180302134436.18844-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Fri, 2 Mar 2018 14:44:36 +0100")
Jerome Brunet <jbrunet@baylibre.com> writes:
> 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>
Applied to v4.17/dt64 and Cc'd to stable,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: Carlo Caione <carlo@caione.org>,
ellierevves@gmail.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
Date: Wed, 07 Mar 2018 17:24:43 -0800 [thread overview]
Message-ID: <7hy3j3fjfo.fsf@baylibre.com> (raw)
In-Reply-To: <20180302134436.18844-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Fri, 2 Mar 2018 14:44:36 +0100")
Jerome Brunet <jbrunet@baylibre.com> writes:
> 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>
Applied to v4.17/dt64 and Cc'd to stable,
Kevin
next prev parent reply other threads:[~2018-03-08 1:24 UTC|newest]
Thread overview: 12+ 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-02 13:44 ` Jerome Brunet
2018-03-02 13:44 ` Jerome Brunet
2018-03-08 1:24 ` Kevin Hilman [this message]
2018-03-08 1:24 ` Kevin Hilman
2018-03-08 1:24 ` Kevin Hilman
2018-03-26 20:23 ` Kevin Hilman
2018-03-26 20:23 ` Kevin Hilman
2018-03-27 6:27 ` Greg KH
2018-03-27 6:27 ` Greg KH
2018-03-28 0:10 ` Kevin Hilman
2018-03-28 0:10 ` Kevin Hilman
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=7hy3j3fjfo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.