^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) mmc-card / eMMC bindings
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) ------------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4) This documents describes the devicetree bindings for a mmc-host controller
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) child node describing a mmc-card / an eMMC, see "Use of Function subnodes"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6) in mmc.txt
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8) Required properties:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) -compatible : Must be "mmc-card"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) -reg : Must be <0>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) Optional properties:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13) -broken-hpi : Use this to indicate that the mmc-card has a broken hpi
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) implementation, and that hpi should not be used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) Example:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) &mmc2 {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) pinctrl-names = "default";
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20) pinctrl-0 = <&mmc2_pins_a>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) vmmc-supply = <®_vcc3v3>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) bus-width = <8>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) non-removable;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) mmccard: mmccard@0 {
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) reg = <0>;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) compatible = "mmc-card";
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) broken-hpi;
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) };
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30) };