* [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
@ 2018-03-02 13:44 ` Jerome Brunet
0 siblings, 0 replies; 12+ messages in thread
From: Jerome Brunet @ 2018-03-02 13:44 UTC (permalink / raw)
To: Kevin Hilman, Carlo Caione
Cc: ellierevves, Jerome Brunet, devicetree, linux-arm-kernel,
linux-amlogic, linux-kernel
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>
---
arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index 73a030a5ecf3..43475139576c 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -311,7 +311,7 @@
pinctrl-names = "default", "clk-gate";
bus-width = <8>;
- max-frequency = <200000000>;
+ max-frequency = <100000000>;
non-removable;
disable-wp;
cap-mmc-highspeed;
--
2.14.3
^ permalink raw reply related [flat|nested] 12+ messages in thread* [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
@ 2018-03-02 13:44 ` Jerome Brunet
0 siblings, 0 replies; 12+ messages in thread
From: Jerome Brunet @ 2018-03-02 13:44 UTC (permalink / raw)
To: linux-arm-kernel
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>
---
arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
index 73a030a5ecf3..43475139576c 100644
--- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
+++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
@@ -311,7 +311,7 @@
pinctrl-names = "default", "clk-gate";
bus-width = <8>;
- max-frequency = <200000000>;
+ max-frequency = <100000000>;
non-removable;
disable-wp;
cap-mmc-highspeed;
--
2.14.3
^ permalink raw reply related [flat|nested] 12+ messages in thread* [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
2018-03-02 13:44 ` Jerome Brunet
(?)
@ 2018-03-08 1:24 ` Kevin Hilman
-1 siblings, 0 replies; 12+ messages in thread
From: Kevin Hilman @ 2018-03-08 1:24 UTC (permalink / raw)
To: linus-amlogic
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
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
@ 2018-03-08 1:24 ` Kevin Hilman
0 siblings, 0 replies; 12+ messages in thread
From: Kevin Hilman @ 2018-03-08 1:24 UTC (permalink / raw)
To: Jerome Brunet
Cc: Carlo Caione, ellierevves, devicetree, linux-arm-kernel,
linux-amlogic, linux-kernel
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
^ permalink raw reply [flat|nested] 12+ messages in thread* [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
@ 2018-03-08 1:24 ` Kevin Hilman
0 siblings, 0 replies; 12+ messages in thread
From: Kevin Hilman @ 2018-03-08 1:24 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
2018-03-02 13:44 ` Jerome Brunet
@ 2018-03-26 20:23 ` Kevin Hilman
-1 siblings, 0 replies; 12+ messages in thread
From: Kevin Hilman @ 2018-03-26 20:23 UTC (permalink / raw)
To: linus-amlogic
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.
The mainline patch has "Cc: stable at vger.kernel.org", but it doesn't
seem to have appeared in stable yet, and I've verified that it applies
cleanly to linux-4.15.y and linux-4.14.y.
Kevin
> ---
> arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> index 73a030a5ecf3..43475139576c 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> +++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> @@ -311,7 +311,7 @@
> pinctrl-names = "default", "clk-gate";
>
> bus-width = <8>;
> - max-frequency = <200000000>;
> + max-frequency = <100000000>;
> non-removable;
> disable-wp;
> cap-mmc-highspeed;
> --
> 2.14.3
>
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
@ 2018-03-26 20:23 ` Kevin Hilman
0 siblings, 0 replies; 12+ messages in thread
From: Kevin Hilman @ 2018-03-26 20:23 UTC (permalink / raw)
To: Stable; +Cc: Carlo Caione, ellierevves, linux-amlogic, Jerome Brunet
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.
The mainline patch has "Cc: stable@vger.kernel.org", but it doesn't
seem to have appeared in stable yet, and I've verified that it applies
cleanly to linux-4.15.y and linux-4.14.y.
Kevin
> ---
> arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> index 73a030a5ecf3..43475139576c 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> +++ b/arch/arm64/boot/dts/amlogic/meson-gxbb-odroidc2.dts
> @@ -311,7 +311,7 @@
> pinctrl-names = "default", "clk-gate";
>
> bus-width = <8>;
> - max-frequency = <200000000>;
> + max-frequency = <100000000>;
> non-removable;
> disable-wp;
> cap-mmc-highspeed;
> --
> 2.14.3
>
^ permalink raw reply [flat|nested] 12+ messages in thread* [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
2018-03-26 20:23 ` Kevin Hilman
@ 2018-03-27 6:27 ` Greg KH
-1 siblings, 0 replies; 12+ messages in thread
From: Greg KH @ 2018-03-27 6:27 UTC (permalink / raw)
To: linus-amlogic
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.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
@ 2018-03-27 6:27 ` Greg KH
0 siblings, 0 replies; 12+ messages in thread
From: Greg KH @ 2018-03-27 6:27 UTC (permalink / raw)
To: Kevin Hilman
Cc: Stable, Carlo Caione, ellierevves, linux-amlogic, Jerome Brunet
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.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 12+ messages in thread* [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
2018-03-27 6:27 ` Greg KH
@ 2018-03-28 0:10 ` Kevin Hilman
-1 siblings, 0 replies; 12+ messages in thread
From: Kevin Hilman @ 2018-03-28 0:10 UTC (permalink / raw)
To: linus-amlogic
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
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: [PATCH] ARM64: dts: meson: reduce odroid-c2 eMMC maximum rate
@ 2018-03-28 0:10 ` Kevin Hilman
0 siblings, 0 replies; 12+ messages in thread
From: Kevin Hilman @ 2018-03-28 0:10 UTC (permalink / raw)
To: Greg KH; +Cc: Stable, Carlo Caione, ellierevves, linux-amlogic, Jerome Brunet
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
^ permalink raw reply [flat|nested] 12+ messages in thread