On 9/4/2024 11:53 PM, Krzysztof Kozlowski wrote:
> On 04/09/2024 19:12, Raviteja Laggyshetty wrote:
>> Add Epoch Subsystem (EPSS) L3 interconnect provider binding on
>> SA8775P SoCs.
>>
>> Signed-off-by: Raviteja Laggyshetty <quic_rlaggysh@xxxxxxxxxxx>
>> ---
>> Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml b/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml
>> index 21dae0b92819..de2c59ddc94a 100644
>> --- a/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml
>> +++ b/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml
>> @@ -33,6 +33,8 @@ properties:
>> - qcom,sm6375-cpucp-l3
>> - qcom,sm8250-epss-l3
>> - qcom,sm8350-epss-l3
>> + - qcom,sa8775p-epss-l3-cl0
>> + - qcom,sa8775p-epss-l3-cl1
>
> Your device driver change suggests that cl0 is compatible with other
> variants.
>
> And what about generic fallback here? Can it be used and device will be
> operating correctly?
>
Falling back to "qcom,epss-l3" won't work because we need to vote into perf state register.
I am introducing a new fallback compatible "qcom,epss-l3-perf" for perf voting, which can be used for upcoming qcs8300.
epss_l3_cl0: interconnect@18590000 {
compatible = "qcom,sa8775p-epss-l3", "qcom,epss-l3-perf";
};
> Best regards,
> Krzysztof
>
