linux

iv/linux

History

Martin Botka 83d4e04431 dt-bindings: opp: Describe H616 OPPs and opp-supported-hw

Compared to the existing Allwinner H6 OPP scheme, the H616 uses a
similar NVMEM based mechanism to determine the silicon revision, which
is required to select the right frequency / voltage pair for the OPPs.
However it limits the maximum frequency for some speed bins, also seems
to not support all frequencies in all speed bins, which requires us to
introduce the opp-supported-hw property.

Add this property to the list of allowed properties, also drop the
requirement for the revision specific opp-microvolt properties, since
they might not be needed if using opp-supported-hw.

Also use to opportunity to adjust some wording, and drop a sentence
referring to the Linux driver and the OPP subsystem.

Shorten the existing example and add another example, showcasing the
opp-supported-hw property.

Signed-off-by: Martin Botka <martin.botka@somainline.org>
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

2024-04-19 12:34:27 +05:30

allwinner,sun50i-h6-operating-points.yaml

dt-bindings: opp: Describe H616 OPPs and opp-supported-hw

2024-04-19 12:34:27 +05:30

operating-points-v2-ti-cpu.yaml

dt-bindings: cpufreq: Convert ti-cpufreq to json schema

2023-08-21 11:23:34 +05:30

opp-v1.yaml

dt-bindings: drop redundant part of title (end, part three)

2022-12-16 11:41:49 -06:00

opp-v2-base.yaml

dt-bindings: opp: drop maxItems from inner items