From: Al Cooper <alcooperx@gmail.com>
To: ulf.hansson@linaro.org, adrian.hunter@intel.com,
linux-mmc@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
cernekee@gmail.com
Cc: Al Cooper <alcooperx@gmail.com>
Subject: [PATCH V5 0/2] Add SDHCI driver for Broadcom BRCMSTB/BMIPS Soc's
Date: Thu, 2 Jun 2016 14:12:47 -0400 [thread overview]
Message-ID: <1464891169-32284-1-git-send-email-alcooperx@gmail.com> (raw)
V5 - Don't create new device tree properties to disable broken UHS
modes. Use devm_clk_get() to get clk and change
clk_enable/clk_disable to clk_prepare_enable/clk_disable_unprepare
V4 - Change the DT compatible property to "brcm,bcm7425-sdhci".
Add "clocks" property to DT bindings document.
V3 - Don't add new QUIRKS to workaround Host Controller issues.
It turns out that all the issues could be solved by using
SDHCI_QUIRK_MISSING_CAPS to supply modified "caps" and "caps1"
Host Controller registers.
Al Cooper (2):
mmc: sdhci-brcmstb: Add driver for Broadcom BRCMSTB SoCs
mmc: DT: sdhci-brcmstb: Add device tree bindings
.../devicetree/bindings/mmc/brcm,bcm7425-sdhci.txt | 32 +++++
MAINTAINERS | 7 ++
drivers/mmc/host/Kconfig | 11 ++
drivers/mmc/host/Makefile | 1 +
drivers/mmc/host/sdhci-brcmstb.c | 137 +++++++++++++++++++++
5 files changed, 188 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mmc/brcm,bcm7425-sdhci.txt
create mode 100644 drivers/mmc/host/sdhci-brcmstb.c
--
1.9.0.138.g2de3478
next reply other threads:[~2016-06-02 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 18:12 Al Cooper [this message]
2016-06-02 18:12 ` [PATCH V5 1/2] mmc: sdhci-brcmstb: Add driver for Broadcom BRCMSTB SoCs Al Cooper
2016-06-02 18:12 ` [PATCH V5 2/2] mmc: DT: sdhci-brcmstb: Add device tree bindings Al Cooper
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=1464891169-32284-1-git-send-email-alcooperx@gmail.com \
--to=alcooperx@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=cernekee@gmail.com \
--cc=linux-mmc@vger.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).