1*4882a593Smuzhiyunmmc-card / eMMC bindings 2*4882a593Smuzhiyun------------------------ 3*4882a593Smuzhiyun 4*4882a593SmuzhiyunThis documents describes the devicetree bindings for a mmc-host controller 5*4882a593Smuzhiyunchild node describing a mmc-card / an eMMC, see "Use of Function subnodes" 6*4882a593Smuzhiyunin mmc.txt 7*4882a593Smuzhiyun 8*4882a593SmuzhiyunRequired properties: 9*4882a593Smuzhiyun-compatible : Must be "mmc-card" 10*4882a593Smuzhiyun-reg : Must be <0> 11*4882a593Smuzhiyun 12*4882a593SmuzhiyunOptional properties: 13*4882a593Smuzhiyun-broken-hpi : Use this to indicate that the mmc-card has a broken hpi 14*4882a593Smuzhiyun implementation, and that hpi should not be used 15*4882a593Smuzhiyun 16*4882a593SmuzhiyunExample: 17*4882a593Smuzhiyun 18*4882a593Smuzhiyun&mmc2 { 19*4882a593Smuzhiyun pinctrl-names = "default"; 20*4882a593Smuzhiyun pinctrl-0 = <&mmc2_pins_a>; 21*4882a593Smuzhiyun vmmc-supply = <®_vcc3v3>; 22*4882a593Smuzhiyun bus-width = <8>; 23*4882a593Smuzhiyun non-removable; 24*4882a593Smuzhiyun 25*4882a593Smuzhiyun mmccard: mmccard@0 { 26*4882a593Smuzhiyun reg = <0>; 27*4882a593Smuzhiyun compatible = "mmc-card"; 28*4882a593Smuzhiyun broken-hpi; 29*4882a593Smuzhiyun }; 30*4882a593Smuzhiyun}; 31