1*88364387SHung-ying TyanChrome OS CROS_EC Binding 2*88364387SHung-ying Tyan====================== 3*88364387SHung-ying Tyan 4*88364387SHung-ying TyanThe device tree node which describes the operation of the CROS_EC interface 5*88364387SHung-ying Tyanis as follows: 6*88364387SHung-ying Tyan 7*88364387SHung-ying TyanRequired properties : 8*88364387SHung-ying Tyan- compatible = "google,cros-ec" 9*88364387SHung-ying Tyan 10*88364387SHung-ying TyanOptional properties : 11*88364387SHung-ying Tyan- spi-max-frequency : Sets the maximum frequency (in Hz) for SPI bus 12*88364387SHung-ying Tyan operation 13*88364387SHung-ying Tyan- i2c-max-frequency : Sets the maximum frequency (in Hz) for I2C bus 14*88364387SHung-ying Tyan operation 15*88364387SHung-ying Tyan- ec-interrupt : Selects the EC interrupt, defined as a GPIO according 16*88364387SHung-ying Tyan to the platform 17*88364387SHung-ying Tyan- optimise-flash-write : Boolean property - if present then flash blocks 18*88364387SHung-ying Tyan containing all 0xff will not be written, since we assume that the EC 19*88364387SHung-ying Tyan uses that pattern for erased blocks 20*88364387SHung-ying Tyan 21*88364387SHung-ying TyanThe CROS_EC node should appear as a subnode of the interrupt that connects it 22*88364387SHung-ying Tyanto the EC (e.g. i2c, spi, lpc). The reg property (as usual) will indicate 23*88364387SHung-ying Tyanthe unit address on that bus. 24*88364387SHung-ying Tyan 25*88364387SHung-ying Tyan 26*88364387SHung-ying TyanExample 27*88364387SHung-ying Tyan======= 28*88364387SHung-ying Tyan 29*88364387SHung-ying Tyan spi@131b0000 { 30*88364387SHung-ying Tyan cros-ec@0 { 31*88364387SHung-ying Tyan reg = <0>; 32*88364387SHung-ying Tyan compatible = "google,cros-ec"; 33*88364387SHung-ying Tyan spi-max-frequency = <5000000>; 34*88364387SHung-ying Tyan ec-interrupt = <&gpio 174 1>; 35*88364387SHung-ying Tyan optimise-flash-write; 36*88364387SHung-ying Tyan status = "disabled"; 37*88364387SHung-ying Tyan }; 38*88364387SHung-ying Tyan }; 39