1275876e2SXiubo LiDevice-Tree binding for regmap 2275876e2SXiubo Li 3275876e2SXiubo LiThe endianness mode of CPU & Device scenarios: 4275876e2SXiubo LiIndex Device Endianness properties 5275876e2SXiubo Li--------------------------------------------------- 6275876e2SXiubo Li1 BE 'big-endian' 7275876e2SXiubo Li2 LE 'little-endian' 8275876e2SXiubo Li 9275876e2SXiubo LiFor one device driver, which will run in different scenarios above 10275876e2SXiubo Lion different SoCs using the devicetree, we need one way to simplify 11275876e2SXiubo Lithis. 12275876e2SXiubo Li 13275876e2SXiubo LiRequired properties: 14275876e2SXiubo Li- {big,little}-endian: these are boolean properties, if absent 15275876e2SXiubo Li meaning that the CPU and the Device are in the same endianness mode, 16275876e2SXiubo Li these properties are for register values and all the buffers only. 17275876e2SXiubo Li 18275876e2SXiubo LiExamples: 19275876e2SXiubo LiScenario 1 : CPU in LE mode & device in LE mode. 20275876e2SXiubo Lidev: dev@40031000 { 21275876e2SXiubo Li compatible = "name"; 22275876e2SXiubo Li reg = <0x40031000 0x1000>; 23275876e2SXiubo Li ... 24275876e2SXiubo Li}; 25275876e2SXiubo Li 26275876e2SXiubo LiScenario 2 : CPU in LE mode & device in BE mode. 27275876e2SXiubo Lidev: dev@40031000 { 28275876e2SXiubo Li compatible = "name"; 29275876e2SXiubo Li reg = <0x40031000 0x1000>; 30275876e2SXiubo Li ... 31275876e2SXiubo Li big-endian; 32275876e2SXiubo Li}; 33275876e2SXiubo Li 34275876e2SXiubo LiScenario 3 : CPU in BE mode & device in BE mode. 35275876e2SXiubo Lidev: dev@40031000 { 36275876e2SXiubo Li compatible = "name"; 37275876e2SXiubo Li reg = <0x40031000 0x1000>; 38275876e2SXiubo Li ... 39275876e2SXiubo Li}; 40275876e2SXiubo Li 41275876e2SXiubo LiScenario 4 : CPU in BE mode & device in LE mode. 42275876e2SXiubo Lidev: dev@40031000 { 43275876e2SXiubo Li compatible = "name"; 44275876e2SXiubo Li reg = <0x40031000 0x1000>; 45275876e2SXiubo Li ... 46275876e2SXiubo Li little-endian; 47275876e2SXiubo Li}; 48