From: "Steven J. Hill" <steven.hill@cavium.com>
To: linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-mips@linux-mips.org
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ralf Baechle <ralf@linux-mips.org>
Subject: [PATCH V8 0/2] mmc: OCTEON: Add OCTEON MMC controller.
Date: Tue, 12 Jul 2016 13:18:22 -0500 [thread overview]
Message-ID: <5785346E.8020702@cavium.com> (raw)
The OCTEON MMC controller is currently found on cn61XX and cnf71XX
devices. Device parameters are configured from device tree data.
The MMC controller can be connected to up to 4 "slots" which may be
eMMC, MMC or SD card devices. As there is a single controller, each
available slot is represented as a child node of the controller.
This MMC driver is the product of previous versions and discussions
which can be found at the below URLs.
[V7] https://patchwork.linux-mips.org/patch/12566/
https://patchwork.linux-mips.org/patch/12567/
[V6] https://patchwork.linux-mips.org/patch/12538/
https://patchwork.linux-mips.org/patch/12539/
https://patchwork.linux-mips.org/patch/12540/
[V5] https://patchwork.linux-mips.org/patch/12533/
[V4] https://patchwork.linux-mips.org/patch/9558/
[V3] https://patchwork.linux-mips.org/patch/9462/
[V2] https://patchwork.linux-mips.org/patch/9086/
[V1] https://patchwork.linux-mips.org/patch/9079/
Steven J. Hill (2):
mmc: OCTEON: Add DT bindings for OCTEON MMC controller.
mmc: OCTEON: Add host driver for OCTEON MMC controller.
.../devicetree/bindings/mmc/octeon-mmc.txt | 72 ++
drivers/mmc/host/Kconfig | 10 +
drivers/mmc/host/Makefile | 1 +
drivers/mmc/host/octeon_mmc.c | 1331 ++++++++++++++++++++
4 files changed, 1414 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mmc/octeon-mmc.txt
create mode 100644 drivers/mmc/host/octeon_mmc.c
--
1.9.1
reply other threads:[~2016-07-12 18:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5785346E.8020702@cavium.com \
--to=steven.hill@cavium.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=ulf.hansson@linaro.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).