1Device-Tree binding for regmap 2 3The endianness mode of CPU & Device scenarios: 4Index Device Endianness properties 5--------------------------------------------------- 61 BE 'big-endian' 72 LE 'little-endian' 83 Native 'native-endian' 9 10For one device driver, which will run in different scenarios above 11on different SoCs using the devicetree, we need one way to simplify 12this. 13 14Optional properties: 15- {big,little,native}-endian: these are boolean properties, if absent 16 then the implementation will choose a default based on the device 17 being controlled. These properties are for register values and all 18 the buffers only. Native endian means that the CPU and device have 19 the same endianness. 20 21Examples: 22Scenario 1 : CPU in LE mode & device in LE mode. 23dev: dev@40031000 { 24 compatible = "name"; 25 reg = <0x40031000 0x1000>; 26 ... 27}; 28 29Scenario 2 : CPU in LE mode & device in BE mode. 30dev: dev@40031000 { 31 compatible = "name"; 32 reg = <0x40031000 0x1000>; 33 ... 34 big-endian; 35}; 36 37Scenario 3 : CPU in BE mode & device in BE mode. 38dev: dev@40031000 { 39 compatible = "name"; 40 reg = <0x40031000 0x1000>; 41 ... 42}; 43 44Scenario 4 : CPU in BE mode & device in LE mode. 45dev: dev@40031000 { 46 compatible = "name"; 47 reg = <0x40031000 0x1000>; 48 ... 49 little-endian; 50}; 51