[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <99bda06f-8e2f-4f51-88f2-d99187e29b92@linaro.org>
Date: Wed, 27 Mar 2024 13:14:27 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Odelu Kukatla <quic_okukatla@...cinc.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>, Georgi Djakov <djakov@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: Kees Cook <keescook@...omium.org>, cros-qcom-dts-watchers@...omium.org,
"Gustavo A . R . Silva" <gustavoars@...nel.org>,
linux-arm-msm@...r.kernel.org, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org, quic_rlaggysh@...cinc.com,
quic_mdtipton@...cinc.com
Subject: Re: [PATCH v4 3/4] dt-bindings: interconnect: add clock property to
enable QOS on SC7280
On 27/03/2024 12:35, Odelu Kukatla wrote:
>>> maxItems: 1
>>>
>>> + clocks:
>>> + minItems: 1
>>> + maxItems: 2
>>
>> Why is this flexible? Nothing in commit msg explains that. I gave the
>> same talk twice, gave there examples, yet it is not enough...
>>
>
> Clocks property is optional, and can be either 1 or 2 or none.
> I think "minItems: 1" should be removed. If no clock property is mentioned in node that means no clock is required to be enabled for QoS configuration.
>
> I will add back specific number of clocks based on interconnect compatible similar to what i did in v3.
Just be sure you read the example I gave you.
Best regards,
Krzysztof
Powered by blists - more mailing lists