diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2024-11-19 23:37:56 +0300 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2024-11-19 23:37:56 +0300 |
commit | 1a93226619dc5798dacee0734a5f1f886b358953 (patch) | |
tree | c5b1287cadf7db2c28fa9e6f46030078eaa78722 | |
parent | ad52c55e1d3a2e85e05e47b6d7056c662a9c0246 (diff) | |
parent | 53205a7903666d35709954d9fb7370a8150d5e0e (diff) | |
download | linux-1a93226619dc5798dacee0734a5f1f886b358953.tar.xz |
Merge tag 'opp-updates-6.13' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/vireshk/pm
Merge OPP (Operating Performance Points) Updates for 6.13 from Viresh
Kumar:
"- Describe opp-supported-hw property for ti-cpu (Dhruva Gole).
- Remove unused declarations in header file (Zhang Zekun)."
* tag 'opp-updates-6.13' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/vireshk/pm:
dt-bindings: opp: operating-points-v2-ti-cpu: Describe opp-supported-hw
OPP: Remove unused declarations in header file
-rw-r--r-- | Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml | 20 | ||||
-rw-r--r-- | drivers/opp/opp.h | 2 |
2 files changed, 19 insertions, 3 deletions
diff --git a/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml b/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml index fd0c8d5c5f3e..624d1f3f1382 100644 --- a/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml +++ b/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml @@ -45,7 +45,25 @@ patternProperties: clock-latency-ns: true opp-hz: true opp-microvolt: true - opp-supported-hw: true + opp-supported-hw: + items: + items: + - description: + The revision of the SoC the OPP is supported by. + This can be easily obtained from the datasheet of the + part being ordered/used. For example, it will be 0x01 for SR1.0 + + - description: + The eFuse bits that indicate the particular OPP is available. + The device datasheet has a table talking about Device Speed Grades. + This table is to be sorted with only the unique elements of the + MAXIMUM OPERATING FREQUENCY starting from the first row which + tells the lowest OPP, to the highest. The corresponding bits + need to be set based on N elements of speed grade the device supports. + So, if there are 3 possible unique MAXIMUM OPERATING FREQUENCY + in the table, then BIT(0) | (1) | (2) will be set, which means + the value shall be 0x7. + opp-suspend: true turbo-mode: true diff --git a/drivers/opp/opp.h b/drivers/opp/opp.h index cff1fabd1ae3..882e32f121d3 100644 --- a/drivers/opp/opp.h +++ b/drivers/opp/opp.h @@ -262,9 +262,7 @@ int _opp_add(struct device *dev, struct dev_pm_opp *new_opp, struct opp_table *o int _opp_add_v1(struct opp_table *opp_table, struct device *dev, struct dev_pm_opp_data *data, bool dynamic); void _dev_pm_opp_cpumask_remove_table(const struct cpumask *cpumask, int last_cpu); struct opp_table *_add_opp_table_indexed(struct device *dev, int index, bool getclk); -void _put_opp_list_kref(struct opp_table *opp_table); void _required_opps_available(struct dev_pm_opp *opp, int count); -void _update_set_required_opps(struct opp_table *opp_table); static inline bool lazy_linking_pending(struct opp_table *opp_table) { |