Tom Rini | 53633a8 | 2024-02-29 12:33:36 -0500 | [diff] [blame^] | 1 | Devicetree binding for regmap |
| 2 | |
| 3 | Optional properties: |
| 4 | |
| 5 | little-endian, |
| 6 | big-endian, |
| 7 | native-endian: See common-properties.txt for a definition |
| 8 | |
| 9 | Note: |
| 10 | Regmap defaults to little-endian register access on MMIO based |
| 11 | devices, this is by far the most common setting. On CPU |
| 12 | architectures that typically run big-endian operating systems |
| 13 | (e.g. PowerPC), registers can be defined as big-endian and must |
| 14 | be marked that way in the devicetree. |
| 15 | |
| 16 | On SoCs that can be operated in both big-endian and little-endian |
| 17 | modes, with a single hardware switch controlling both the endianness |
| 18 | of the CPU and a byteswap for MMIO registers (e.g. many Broadcom MIPS |
| 19 | chips), "native-endian" is used to allow using the same device tree |
| 20 | blob in both cases. |
| 21 | |
| 22 | Examples: |
| 23 | Scenario 1 : a register set in big-endian mode. |
| 24 | dev: dev@40031000 { |
| 25 | compatible = "syscon"; |
| 26 | reg = <0x40031000 0x1000>; |
| 27 | big-endian; |
| 28 | ... |
| 29 | }; |