[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1477335850-14945-1-git-send-email-zach.brown@ni.com>
Date: Mon, 24 Oct 2016 14:04:08 -0500
From: Zach Brown <zach.brown@...com>
To: <ulf.hansson@...aro.org>
CC: <adrian.hunter@...el.com>, <robh+dt@...nel.org>,
<mark.rutland@....com>, <linux-mmc@...r.kernel.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<zach.brown@...com>
Subject: [RFC v3 0/2] mmc: sdhci: Ignore capability register when it comes to speeds and use DT binding instead when sdhci-cap-speed-modes-broken is set.
The first patch add documentation about a new devicetree property
sdhci-cap-speed-modes-broken.
The second patch makes the sdhci use the DT binding instead of the caps
register for determining which speed modes are supported by the controller.
This RFC is an alternative to another patch[1] set I sent up.
[1]
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1251944.html
v2:
* Removed separate OF parsing function, relying on mmc_of_parse to be called
before read_caps
* Moved check of sdhci-cap-speed-modes-broken into sdhci_read_caps.
* Added SDHCI_SUPPORT_HS400 to list of bits to clear in sdhci cap1, not
sure that's all of the them now, but I think so.
v3:
* Read "sdhci-cap-speed-modes-broken" only once.
* If caps are provided to sdhci_read_caps the speed bits are not overwritten.
Zach Brown (2):
mmc: sdhci: Add device tree property sdhci-cap-speed-modes-broken
mmc: sdhci: Ignore capability register when it comes to speeds and use
DT binding instead when sdhci-cap-speed-modes-broken is set.
Documentation/devicetree/bindings/mmc/mmc.txt | 3 +++
drivers/mmc/host/sdhci.c | 25 +++++++++++++++++++++++--
2 files changed, 26 insertions(+), 2 deletions(-)
--
2.7.4
Powered by blists - more mailing lists