mirror of
https://github.com/Evolution-X-Devices/kernel_xiaomi_sm8450-devicetrees
synced 2026-01-27 20:28:49 +00:00
b0e5152a74
Add devicetree bindings snapshot to the devicetree project.
This snapshot is taken as of the
'commit 5fba1b18cfc72e264e5f3ce49020ed322aa6ac9f ("Merge 5.6-rc3
into android-mainline")' of the kernel project.
Change-Id: Ia087ab2b7d4a2616ea446a69683a8b5b821d0448
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;
|
|
...
|
|
};
|