Lines Matching +full:mode +full:- +full:flag
1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/mmc/mmc-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Ulf Hansson <ulf.hansson@linaro.org>
25 "#address-cells":
30 "#size-cells":
37 broken-cd:
38 $ref: /schemas/types.yaml#/definitions/flag
42 cd-gpios:
47 non-removable:
48 $ref: /schemas/types.yaml#/definitions/flag
50 Non-removable slot (like eMMC); assume always present.
56 # low." Therefore, using the "cd-inverted" property means, that the
58 # inserted. Similar logic applies to the "wp-inverted" property.
61 # ways: as GPIOs, specified in cd-gpios and wp-gpios properties, or
63 # using *-inverted properties. GPIO polarity can also be specified
64 # using the GPIO_ACTIVE_LOW flag. This creates an ambiguity in the
67 # example leaving the GPIO_ACTIVE_LOW flag clear and specifying the
68 # respective *-inverted property property results in a
69 # double-inversion and actually means the "normal" line polarity is
71 wp-inverted:
72 $ref: /schemas/types.yaml#/definitions/flag
76 cd-inverted:
77 $ref: /schemas/types.yaml#/definitions/flag
83 bus-width:
90 max-frequency:
93 - for eMMC, the maximum supported frequency is 200MHz,
94 - for SD/SDIO cards the SDR104 mode has a max supported
96 - some mmc host controllers do support a max frequency upto
104 disable-wp:
105 $ref: /schemas/types.yaml#/definitions/flag
107 When set, no physical write-protect line is present. This
109 dedicated write-protect detection logic. If a GPIO is always used
110 for the write-protect detection logic, it is sufficient to not
111 specify the wp-gpios property in the absence of a write-protect
114 wp-gpios:
117 GPIO to use for the write-protect detection.
119 cd-debounce-delay-ms:
124 no-1-8-v:
125 $ref: /schemas/types.yaml#/definitions/flag
130 cap-sd-highspeed:
131 $ref: /schemas/types.yaml#/definitions/flag
133 SD high-speed timing is supported.
135 cap-mmc-highspeed:
136 $ref: /schemas/types.yaml#/definitions/flag
138 MMC high-speed timing is supported.
140 sd-uhs-sdr12:
141 $ref: /schemas/types.yaml#/definitions/flag
145 sd-uhs-sdr25:
146 $ref: /schemas/types.yaml#/definitions/flag
150 sd-uhs-sdr50:
151 $ref: /schemas/types.yaml#/definitions/flag
155 sd-uhs-sdr104:
156 $ref: /schemas/types.yaml#/definitions/flag
160 sd-uhs-ddr50:
161 $ref: /schemas/types.yaml#/definitions/flag
165 cap-power-off-card:
166 $ref: /schemas/types.yaml#/definitions/flag
170 cap-mmc-hw-reset:
171 $ref: /schemas/types.yaml#/definitions/flag
175 cap-sdio-irq:
176 $ref: /schemas/types.yaml#/definitions/flag
180 full-pwr-cycle:
181 $ref: /schemas/types.yaml#/definitions/flag
185 full-pwr-cycle-in-suspend:
186 $ref: /schemas/types.yaml#/definitions/flag
190 mmc-ddr-1_2v:
191 $ref: /schemas/types.yaml#/definitions/flag
193 eMMC high-speed DDR mode (1.2V I/O) is supported.
195 mmc-ddr-1_8v:
196 $ref: /schemas/types.yaml#/definitions/flag
198 eMMC high-speed DDR mode (1.8V I/O) is supported.
200 mmc-ddr-3_3v:
201 $ref: /schemas/types.yaml#/definitions/flag
203 eMMC high-speed DDR mode (3.3V I/O) is supported.
205 mmc-hs200-1_2v:
206 $ref: /schemas/types.yaml#/definitions/flag
208 eMMC HS200 mode (1.2V I/O) is supported.
210 mmc-hs200-1_8v:
211 $ref: /schemas/types.yaml#/definitions/flag
213 eMMC HS200 mode (1.8V I/O) is supported.
215 mmc-hs400-1_2v:
216 $ref: /schemas/types.yaml#/definitions/flag
218 eMMC HS400 mode (1.2V I/O) is supported.
220 mmc-hs400-1_8v:
221 $ref: /schemas/types.yaml#/definitions/flag
223 eMMC HS400 mode (1.8V I/O) is supported.
225 mmc-hs400-enhanced-strobe:
226 $ref: /schemas/types.yaml#/definitions/flag
228 eMMC HS400 enhanced strobe mode is supported
230 no-mmc-hs400:
231 $ref: /schemas/types.yaml#/definitions/flag
243 no-sdio:
244 $ref: /schemas/types.yaml#/definitions/flag
249 no-sd:
250 $ref: /schemas/types.yaml#/definitions/flag
254 no-mmc:
255 $ref: /schemas/types.yaml#/definitions/flag
260 fixed-emmc-driver-type:
262 For non-removable eMMC, enforce this driver type. The value is
269 post-power-on-delay-ms:
271 It was invented for MMC pwrseq-simple which could be referred to
272 mmc-pwrseq-simple.yaml. But now it\'s reused as a tunable delay
274 regardless of whether pwrseq-simple is used. Default to 10ms if
278 supports-cqe:
279 $ref: /schemas/types.yaml#/definitions/flag
284 disable-cqe-dcmd:
285 $ref: /schemas/types.yaml#/definitions/flag
291 keep-power-in-suspend:
292 $ref: /schemas/types.yaml#/definitions/flag
296 wakeup-source:
297 $ref: /schemas/types.yaml#/definitions/flag
301 vmmc-supply:
305 vqmmc-supply:
309 be modeled as a "regulator-fixed" with a GPIO line for
312 mmc-pwrseq:
315 System-on-Chip designs may specify a specific MMC power
320 "^.*@[0-9]+$":
338 - minimum: 0
346 - reg
348 "^clk-phase-(legacy|sd-hs|mmc-(hs|hs[24]00|ddr52)|uhs-(sdr(12|25|50|104)|ddr50))$":
349 $ref: /schemas/types.yaml#/definitions/uint32-array
358 controller while switching to particular speed mode. These values
362 cd-debounce-delay-ms: [ cd-gpios ]
363 fixed-emmc-driver-type: [ non-removable ]
368 - |
370 #address-cells = <1>;
371 #size-cells = <0>;
373 pinctrl-names = "default";
374 pinctrl-0 = <&mmc3_pins_a>;
375 vmmc-supply = <®_vmmc3>;
376 bus-width = <4>;
377 non-removable;
378 mmc-pwrseq = <&sdhci0_pwrseq>;
382 compatible = "brcm,bcm4329-fmac";
383 interrupt-parent = <&pio>;
385 interrupt-names = "host-wake";