Thread (15 messages) 15 messages, 5 authors, 2011-11-19

[PATCH 2/4] mmc: omap: adapt the hsmmc driver to device tree

From: Olof Johansson <hidden>
Date: 2011-11-04 21:28:16
Also in: linux-devicetree, linux-mmc, linux-omap

On Fri, Nov 4, 2011 at 2:25 PM, Cousson, Benoit [off-list ref] wrote:
Hi Olof,

On 11/4/2011 9:04 PM, Olof Johansson wrote:
quoted
On Fri, Nov 04, 2011 at 05:20:39PM +0530, Rajendra Nayak wrote:
quoted
Define dt bindings for the ti-omap-hsmmc, and adapt
the driver to extract data (which was earlier passed as
platform_data) from device tree node.

Signed-off-by: Rajendra Nayak<redacted>
---
?.../devicetree/bindings/mmc/ti-omap-hsmmc.txt ? ? ?| ? 50 +++++++++
?drivers/mmc/host/omap_hsmmc.c ? ? ? ? ? ? ? ? ? ? ?| ?117
++++++++++++++++++++
?2 files changed, 167 insertions(+), 0 deletions(-)
?create mode 100644
Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
diff --git a/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
b/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
new file mode 100644
index 0000000..370af1b
--- /dev/null
+++ b/Documentation/devicetree/bindings/mmc/ti-omap-hsmmc.txt
@@ -0,0 +1,50 @@
+* TI Highspeed MMC host controller for OMAP
+
+The Highspeed MMC Host Controller on TI OMAP family
+provides an interface for MMC, SD, and SDIO types of memory cards.
+
+Required properties:
+- compatible: Should be "ti,omap-hsmmc<n>", "ti,omap2-hsmmc";
+n is controller instance starting 0, for OMAP2/3 controllers
No, no, no. You should not have to specify the unit-address in the
compatible
field. They are all programmed the same way, right?
AFAIR, 2 instances contain a DMA engine, but that should anyway be detected
using a "ti,had-dma-engine" extra property and not like that.
Yep, it should be described by properties instead, such that future
products won't need new bindings unless they add new hardware features
(i.e. just new combinations of existing features should just work,
more or less).
quoted
I didn't think hwmod bindings were settled on yet?
Why did you think that?

That binding was pretty straightforward and mandatory for starting any OMAP
device tree migration until we have the proper reg-names, irq-names and
dma-names generic binding.

Did you had any concern with that binding?
Nope, just wasn't sure if it had settled down since I hadn't followed
it closely. No concerns.


-Olof
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help