From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: rockchip: Bump sd card pin drive strength up on firefly boards
Date: Fri, 22 Jan 2016 14:33:13 +0100 [thread overview]
Message-ID: <1922254.O59ZZAW3Pv@phil> (raw)
In-Reply-To: <1453381033-3479-1-git-send-email-w.egorov@phytec.de>
Am Donnerstag, 21. Januar 2016, 13:57:13 schrieb Wadim Egorov:
> It seems some firefly boards need 12mA drive strength for sdmmc.
> Using 4mA/8mA drive strength will cause the kernel to fail to recognize
> the sd card correctly.
> Increased the sdmmc lines drive strength from 4mA to 12mA.
>
> Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
applied to my dts32 branch for 4.6.
As I said somewhere on IRC before, it might be worthwhile to bump the
default drive-strength at some point, but so far it seems the minimal needed
values seem to diverge (8mA on Veyron, 12ma [4mA on mine] on firefly and
seemingly 4mA working fine on the Rock2). So I guess we'll postpone that a
bit more until we have more datapoints ;-)
Heiko
prev parent reply other threads:[~2016-01-22 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 12:57 [PATCH] ARM: dts: rockchip: Bump sd card pin drive strength up on firefly boards Wadim Egorov
2016-01-22 13:33 ` Heiko Stuebner [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=1922254.O59ZZAW3Pv@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@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