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>,
Dirk Behme <dirk.behme@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [PATCH v3 0/6] tmio: add support for eMMC with 8 bit bus width
Date: Mon, 19 Sep 2016 22:57:44 +0200 [thread overview]
Message-ID: <20160919205750.4766-1-wsa+renesas@sang-engineering.com> (raw)
This series enables SDHI instances on R-Car Gen3 to access eMMC with 8 bit bus
width. I think the patch descriptions speak for themselves.
I decided to not protect this new feature with a flag because it needs
specifically to be enabled by setting the bus width to 8. No legacy platform
does that.
Note that I decided to use the pattern that pinctrl-0 is 3.3v and
pinctrl-1 is 1.8v, although the eMMC is fixed at 1.8v. I tried a few ways to
only use pinctrl-0 being 1.8v here, but they all ended up to be confusing for
users IMO, so I sticked to the most consistent solution after all.
Changes since V2:
* correct node name for sd2_uhs in both devicetrees
Changes since V1:
* merged the two distinct series (drivers + DTS) into one: patches 1-4 are for
Ulf, I will ping Simon for patches 5+6 when the time is ready.
* DTS now contains 'non-removable' and we have a software workaround for now.
These patches are based on top of Simon's sdr104-v7 patches but they apply to
current mmc/next as well. A branch can be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git renesas/topic/sdhi-8bit-emmc
Please review, comment, apply...
Wolfram
Wolfram Sang (6):
mmc: add define for R1 response without CRC
mmc: rtsx_pci: use new macro for R1 without CRC
mmc: rtsx_usb: use new macro for R1 without CRC
mmc: tmio: add eMMC support
arm64: dts: r8a7795: salvator: enable on-board eMMC
arm64: dts: r8a7796: salvator: enable on board eMMC
arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 43 +++++++++++++++++++++
arch/arm64/boot/dts/renesas/r8a7796-salvator-x.dts | 44 +++++++++++++++++++++-
drivers/mmc/host/rtsx_pci_sdmmc.c | 2 +-
drivers/mmc/host/rtsx_usb_sdmmc.c | 2 +-
drivers/mmc/host/tmio_mmc.h | 3 ++
drivers/mmc/host/tmio_mmc_pio.c | 38 +++++++++++++------
include/linux/mmc/core.h | 3 ++
7 files changed, 120 insertions(+), 15 deletions(-)
--
2.9.3
next reply other threads:[~2016-09-19 20:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 20:57 Wolfram Sang [this message]
2016-09-19 20:57 ` [PATCH v3 1/6] mmc: add define for R1 response without CRC Wolfram Sang
2016-09-20 9:25 ` Jaehoon Chung
2016-09-21 6:00 ` Wolfram Sang
2016-09-22 3:58 ` Jaehoon Chung
2016-09-19 20:57 ` [PATCH v3 2/6] mmc: rtsx_pci: use new macro for R1 " Wolfram Sang
2016-09-20 9:29 ` Jaehoon Chung
2016-09-21 6:03 ` Wolfram Sang
2016-09-19 20:57 ` [PATCH v3 3/6] mmc: rtsx_usb: " Wolfram Sang
2016-09-19 20:57 ` [PATCH v3 4/6] mmc: tmio: add eMMC support Wolfram Sang
2016-09-20 9:35 ` Jaehoon Chung
2016-09-21 6:07 ` Wolfram Sang
2016-09-19 20:57 ` [PATCH v3 5/6] arm64: dts: r8a7795: salvator: enable on-board eMMC Wolfram Sang
2016-09-19 20:57 ` [PATCH v3 6/6] arm64: dts: r8a7796: salvator: enable on board eMMC Wolfram Sang
2016-09-22 9:40 ` [PATCH v3 0/6] tmio: add support for eMMC with 8 bit bus width Ulf Hansson
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=20160919205750.4766-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=dirk.behme@gmail.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).