[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac34c454-4800-4057-9a50-e0c5db1d3806@kernel.org>
Date: Wed, 24 Jul 2024 08:27:03 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Varadarajan Narayanan <quic_varada@...cinc.com>, andersson@...nel.org,
mturquette@...libre.com, sboyd@...nel.org, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, gregkh@...uxfoundation.org,
konrad.dybcio@...aro.org, djakov@...nel.org, quic_wcheng@...cinc.com,
quic_kathirav@...cinc.com, linux-arm-msm@...r.kernel.org,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH v4 2/5] dt-bindings: usb: qcom,dwc3: Update ipq5332 clock
details
On 23/07/2024 11:03, Varadarajan Narayanan wrote:
> USB uses icc-clk framework to enable the NoC interface clock.
> Hence the 'iface' clock is removed from the list of clocks.
> Update the clock-names list accordingly.
But the clock is still there and is still used by this block. This looks
like adjusting hardware per Linux implementation.
Why suddenly this clock was removed from this hardware?
>
> Signed-off-by: Varadarajan Narayanan <quic_varada@...cinc.com>
> ---
> .../devicetree/bindings/usb/qcom,dwc3.yaml | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> index efde47a5b145..6c5f962bbcf9 100644
> --- a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> +++ b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> @@ -220,6 +220,22 @@ allOf:
> - const: sleep
> - const: mock_utmi
>
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - qcom,ipq5332-dwc3
> + then:
> + properties:
> + clocks:
> + maxItems: 3
> + clock-names:
> + items:
> + - const: core
> + - const: sleep
> + - const: mock_utmi
So this is the same as first case. Just put it there. It's your task to
check if you are duplicating a case, not reviewer's...
Best regards,
Krzysztof
Powered by blists - more mailing lists