From: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>
To: Peter Geis <pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
"Leonidas P . Papadakos"
<papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] arm64: dts: rockchip: fix rk3328 sdmmc0 write errors
Date: Sat, 16 Mar 2019 21:00:09 +0100 [thread overview]
Message-ID: <4066857.vsuxPprcTe@phil> (raw)
In-Reply-To: <20190313190229.16962-1-pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Am Mittwoch, 13. März 2019, 20:02:30 CET schrieb Peter Geis:
> Various rk3328 based boards experience occasional sdmmc0 write errors.
> This is due to the rk3328.dtsi tx drive levels being set to 4ma, vs
> 8ma per the rk3328 datasheet default settings.
>
> Fix this by setting the tx signal pins to 8ma.
> Inspiration from tonymac32's patch,
> https://github.com/ayufan-rock64/linux-kernel/commit/dc1212b347e0da17c5460bcc0a56b07d02bac3f8
>
> Fixes issues on the rk3328-roc-cc and the rk3328-rock64 (as per the
> above commit message).
>
> Tested on the rk3328-roc-cc board.
>
> Signed-off-by: Peter Geis <pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
applied as fix for 5.1 after adding Fixes and Cc-stable-tags
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Peter Geis <pgwipeout@gmail.com>
Cc: linux-rockchip@lists.infradead.org,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org,
"Leonidas P . Papadakos" <papadakospan@gmail.com>
Subject: Re: [PATCH] arm64: dts: rockchip: fix rk3328 sdmmc0 write errors
Date: Sat, 16 Mar 2019 21:00:09 +0100 [thread overview]
Message-ID: <4066857.vsuxPprcTe@phil> (raw)
In-Reply-To: <20190313190229.16962-1-pgwipeout@gmail.com>
Am Mittwoch, 13. März 2019, 20:02:30 CET schrieb Peter Geis:
> Various rk3328 based boards experience occasional sdmmc0 write errors.
> This is due to the rk3328.dtsi tx drive levels being set to 4ma, vs
> 8ma per the rk3328 datasheet default settings.
>
> Fix this by setting the tx signal pins to 8ma.
> Inspiration from tonymac32's patch,
> https://github.com/ayufan-rock64/linux-kernel/commit/dc1212b347e0da17c5460bcc0a56b07d02bac3f8
>
> Fixes issues on the rk3328-roc-cc and the rk3328-rock64 (as per the
> above commit message).
>
> Tested on the rk3328-roc-cc board.
>
> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
applied as fix for 5.1 after adding Fixes and Cc-stable-tags
Thanks
Heiko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-16 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 19:02 [PATCH] arm64: dts: rockchip: fix rk3328 sdmmc0 write errors Peter Geis
2019-03-13 19:02 ` Peter Geis
[not found] ` <20190313190229.16962-1-pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-03-16 20:00 ` Heiko Stuebner [this message]
2019-03-16 20:00 ` Heiko Stuebner
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=4066857.vsuxPprcTe@phil \
--to=heiko-4mtyjxux2i+zqb+pc5nmwq@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=papadakospan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pgwipeout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=robin.murphy-5wv7dgnIgG8@public.gmane.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.