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)
25 lines
880 B
Plaintext
25 lines
880 B
Plaintext
Binding for Texas Instruments clockdomain.
|
|
|
|
Binding status: Unstable - ABI compatibility may be broken in the future
|
|
|
|
This binding uses the common clock binding[1] in consumer role.
|
|
Every clock on TI SoC belongs to one clockdomain, but software
|
|
only needs this information for specific clocks which require
|
|
their parent clockdomain to be controlled when the clock is
|
|
enabled/disabled. This binding doesn't define a new clock
|
|
binding type, it is used to group existing clock nodes under
|
|
hardware hierarchy.
|
|
|
|
[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
|
|
|
|
Required properties:
|
|
- compatible : shall be "ti,clockdomain"
|
|
- #clock-cells : from common clock binding; shall be set to 0.
|
|
- clocks : link phandles of clocks within this domain
|
|
|
|
Examples:
|
|
dss_clkdm: dss_clkdm {
|
|
compatible = "ti,clockdomain";
|
|
clocks = <&dss1_alwon_fck_3430es2>, <&dss_ick_3430es2>;
|
|
};
|