From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-mmc@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
Simon Horman <horms@verge.net.au>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH v3 0/3] mmc: support eMMC driver type selection with DT
Date: Sun, 15 Oct 2017 14:46:12 +0200 [thread overview]
Message-ID: <20171015124615.31391-1-wsa+renesas@sang-engineering.com> (raw)
Some of the Renesas R-Car boards need to set the eMMC driver type to type 1 to
get stable HS200/400 speeds (HS400 support not upstream yet). Because the eMMC
memories are fixed (and thus the drive type), I decided to implement the DT
setup in a similar fashion to ACPI [1]. While implementing, I realized that all
I did was not Renesas specific but generic, so I ended up putting it into the
core.
So, whenever the new property (introduced in patch 1) is used, its value will
be used regardless of a potentially implemented host driver specific
select_drive_strength callback (patch 2). An example usage can be found in
patch 3. Note that currently only eMMC is handled
A branch for the Salvator-X(S) boards can be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/topic/emmc-drive-strength
A wiki page describing my test procedure can be found here:
http://elinux.org/Tests:eMMC-fixed-drive-strength
Changes since RFC v2 are described per patch. It is mainly a rebase to mmc/next
and addressing Ulf's comments. Tested on Salvator-X (R-Car H3 ES1.0) and
Salvator-XS (R-Car H3 ES2.0).
I know that patch 3 needs to go via Simon, but I still include it here for
completeness.
Thanks,
Wolfram
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=51ced59cc02e0d08f61772c888480b9b1749cef1
Wolfram Sang (3):
dt-bindings: mmc: describe new eMMC binding for fixed driver type
mmc: parse new binding for eMMC fixed driver type
arm64: renesas: salvator: set driver type for eMMC
Documentation/devicetree/bindings/mmc/mmc.txt | 3 +++
arch/arm64/boot/dts/renesas/salvator-common.dtsi | 1 +
drivers/mmc/core/host.c | 13 ++++++++++++-
drivers/mmc/core/mmc.c | 11 ++++++++---
include/linux/mmc/host.h | 2 ++
5 files changed, 26 insertions(+), 4 deletions(-)
--
2.11.0
next reply other threads:[~2017-10-15 12:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-15 12:46 Wolfram Sang [this message]
2017-10-15 12:46 ` [PATCH v3 1/3] dt-bindings: mmc: describe new eMMC binding for fixed driver type Wolfram Sang
2017-10-16 7:45 ` Simon Horman
2017-10-20 10:03 ` Ulf Hansson
2017-10-15 12:46 ` [PATCH v3 2/3] mmc: parse new binding for eMMC " Wolfram Sang
2017-10-16 7:45 ` Simon Horman
2017-10-20 10:03 ` Ulf Hansson
2017-10-15 12:46 ` [PATCH v3 3/3] arm64: renesas: salvator: set driver type for eMMC Wolfram Sang
2017-10-16 7:46 ` Simon Horman
2017-10-20 10:03 ` Ulf Hansson
2017-10-21 8:34 ` Wolfram Sang
2017-10-29 15:16 ` Simon Horman
2017-10-29 15:23 ` Wolfram Sang
2017-10-29 15:25 ` Simon Horman
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=20171015124615.31391-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=horms@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).