threeeye
bc1d038eac
Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
30 lines
907 B
Plaintext
30 lines
907 B
Plaintext
Devicetree binding for regmap
|
|
|
|
Optional properties:
|
|
|
|
little-endian,
|
|
big-endian,
|
|
native-endian: See common-properties.txt for a definition
|
|
|
|
Note:
|
|
Regmap defaults to little-endian register access on MMIO based
|
|
devices, this is by far the most common setting. On CPU
|
|
architectures that typically run big-endian operating systems
|
|
(e.g. PowerPC), registers can be defined as big-endian and must
|
|
be marked that way in the devicetree.
|
|
|
|
On SoCs that can be operated in both big-endian and little-endian
|
|
modes, with a single hardware switch controlling both the endianness
|
|
of the CPU and a byteswap for MMIO registers (e.g. many Broadcom MIPS
|
|
chips), "native-endian" is used to allow using the same device tree
|
|
blob in both cases.
|
|
|
|
Examples:
|
|
Scenario 1 : a register set in big-endian mode.
|
|
dev: dev@40031000 {
|
|
compatible = "syscon";
|
|
reg = <0x40031000 0x1000>;
|
|
big-endian;
|
|
...
|
|
};
|