xref: /openbmc/linux/Documentation/devicetree/bindings/mmc/sdhci-omap.txt (revision 83a1b4cc80fa0d167c71b75ed727da9627d03928)
1* TI OMAP SDHCI Controller
2
3Refer to mmc.txt for standard MMC bindings.
4
5For UHS devices which require tuning, the device tree should have a "cpu_thermal" node which maps to the appropriate thermal zone. This is used to get the temperature of the zone during tuning.
6
7Required properties:
8- compatible: Should be "ti,dra7-sdhci" for DRA7 and DRA72 controllers
9	      Should be "ti,k2g-sdhci" for K2G
10- ti,hwmods: Must be "mmc<n>", <n> is controller instance starting 1
11	     (Not required for K2G).
12- pinctrl-names: Should be subset of "default", "hs", "sdr12", "sdr25", "sdr50",
13		 "ddr50-rev11", "sdr104-rev11", "ddr50", "sdr104",
14		 "ddr_1_8v-rev11", "ddr_1_8v" or "ddr_3_3v", "hs200_1_8v-rev11",
15		 "hs200_1_8v",
16- pinctrl-<n> : Pinctrl states as described in bindings/pinctrl/pinctrl-bindings.txt
17
18Optional properties:
19- dmas:		List of DMA specifiers with the controller specific format as described
20		in the generic DMA client binding. A tx and rx specifier is required.
21- dma-names:	List of DMA request names. These strings correspond 1:1 with the
22		DMA specifiers listed in dmas. The string naming is to be "tx"
23		and "rx" for TX and RX DMA requests, respectively.
24
25Example:
26	mmc1: mmc@4809c000 {
27		compatible = "ti,dra7-sdhci";
28		reg = <0x4809c000 0x400>;
29		ti,hwmods = "mmc1";
30		bus-width = <4>;
31		vmmc-supply = <&vmmc>; /* phandle to regulator node */
32		dmas = <&sdma 61 &sdma 62>;
33		dma-names = "tx", "rx";
34	};
35