Messages in this thread |  | | Date | Mon, 4 May 2026 12:23:57 +0200 | | From | Krzysztof Kozlowski <> | | Subject | Re: [PATCH 1/2] dt-bindings: cpufreq: qcom-hw: Document Shikra CPUFREQ Hardware |
| |
On Fri, May 01, 2026 at 12:45:44PM +0530, Imran Shaik wrote: > The Qualcomm Shikra cpufreq hardware is functionally identical to EPSS, > but supports only up to 12 frequency lookup table (LUT) entries. Introduce > qcom,cpufreq-epss-lite to represent this constrained EPSS variant.
The entire point of having a generic compatible is that it MUST match all devices. If it does not, then it is pointless to push that generic compatible.
I am speaking about qcom,cpufreq-epss.
That's nothing new, I was arguing about it already, but now you have confirmation of the mess introduced by generic compatibles. Solution is not to add more generic compatibles, because what will be next? qcom,cpufreq-epss-lighter? qcom,cpufreq-epss-more-lite? qcom,cpufreq-epss-high?
Same was here: https://lore.kernel.org/all/20240828203721.2751904-17-quic_nkela@quicinc.com/
So that's second time I object and do object for every new instance. No to generic compatibles, they are proven to be wrong at least for Qualcomm.
Best regards, Krzysztof
|  |