[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <169021612042.3789253.5446474765514651082.robh@kernel.org>
Date: Mon, 24 Jul 2023 10:28:40 -0600
From: Rob Herring <robh@...nel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Conor Dooley <conor+dt@...nel.org>,
Andy Gross <agross@...nel.org>,
Wesley Cheng <quic_wcheng@...cinc.com>,
devicetree@...r.kernel.org, Bjorn Andersson <andersson@...nel.org>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>
Subject: Re: [PATCH 1/2] dt-bindings: usb: qcom,dwc3: drop assigned-clocks
On Sun, 23 Jul 2023 16:15:49 +0200, Krzysztof Kozlowski wrote:
> The binding does not have to specify assigned-clocks, because they are
> already allowed by core DT schema. On the other hand, fixed
> assigned-clocks in the binding will not fit different boards or SoCs.
> Exactly this is the case for Qualcomm SuperSpeed DWC3 USB SoC controller
> binding, where few boards have different assigned-clocks:
>
> ipq8074-hk10-c1.dtb: usb@...8800: assigned-clocks: [[5, 131], [5, 132], [5, 133]] is too long
> sdm660-xiaomi-lavender.dtb: usb@...8800: assigned-clocks: [[37, 92], [37, 91], [38, 64]] is too long
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> ---
> Documentation/devicetree/bindings/usb/qcom,dwc3.yaml | 9 ---------
> 1 file changed, 9 deletions(-)
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists