From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: linux-kernel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
linux-arm-msm@vger.kernel.org,
Kishon Vijay Abraham I <kishon@kernel.org>,
linux-phy@lists.infradead.org,
Bjorn Andersson <andersson@kernel.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
devicetree@vger.kernel.org, Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH 1/4] dt-bindings: phy: qcom,usb-snps-femto-v2: use fallback compatibles
Date: Tue, 3 Jan 2023 18:43:31 -0600 [thread overview]
Message-ID: <167279301050.163217.7817410182620857350.robh@kernel.org> (raw)
In-Reply-To: <20221223161835.112079-1-krzysztof.kozlowski@linaro.org>
On Fri, 23 Dec 2022 17:18:32 +0100, Krzysztof Kozlowski wrote:
> Document SoC-specific compatibles with generic fallback (e.g.
> qcom,usb-snps-hs-7nm-phy) already used in DTSI. Add SoC-specific
> compatibles for PHY on SDX55 and SDX65.
>
> This disallows usage of the qcom,usb-snps-hs-5nm-phy and
> qcom,usb-snps-hs-7nm-phy generic compatibles alone. Do not touch
> remaining two compatibles - qcom,usb-snps-femto-v2-phy and
> qcom,sc8180x-usb-hs-phy - because there are no upstream users, so not
> sure what was the intention for them.
>
> This fixes warnings like:
>
> sa8295p-adp.dtb: phy@88e5000: compatible: 'oneOf' conditional failed, one must be fixed:
> ['qcom,sc8280xp-usb-hs-phy', 'qcom,usb-snps-hs-5nm-phy'] is too long
> 'qcom,sc8280xp-usb-hs-phy' is not one of ['qcom,sm8150-usb-hs-phy', 'qcom,sm8250-usb-hs-phy', 'qcom,sm8350-usb-hs-phy', 'qcom,sm8450-usb-hs-phy']
> 'qcom,usb-snps-hs-7nm-phy' was expected
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../bindings/phy/qcom,usb-snps-femto-v2.yaml | 33 +++++++++++--------
> 1 file changed, 20 insertions(+), 13 deletions(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2023-01-04 0:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 16:18 [PATCH 1/4] dt-bindings: phy: qcom,usb-snps-femto-v2: use fallback compatibles Krzysztof Kozlowski
2022-12-23 16:18 ` [PATCH 2/4] ARM: dts: qcom: sdx55: add specific compatible for USB HS PHY Krzysztof Kozlowski
2022-12-23 16:21 ` Konrad Dybcio
2022-12-23 16:18 ` [PATCH 3/4] ARM: dts: qcom: sdx65: " Krzysztof Kozlowski
2022-12-23 16:20 ` Konrad Dybcio
2022-12-24 13:12 ` Krzysztof Kozlowski
2022-12-27 11:14 ` Konrad Dybcio
2022-12-27 11:29 ` Krzysztof Kozlowski
2022-12-23 16:18 ` [PATCH 4/4] arm64: dts: qcom: sm8350: align MMC node names with DT schema Krzysztof Kozlowski
2022-12-23 16:20 ` Konrad Dybcio
2022-12-29 17:23 ` (subset) [PATCH 1/4] dt-bindings: phy: qcom,usb-snps-femto-v2: use fallback compatibles Bjorn Andersson
2023-01-04 0:43 ` Rob Herring [this message]
2023-01-13 18:10 ` Vinod Koul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=167279301050.163217.7817410182620857350.robh@kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=quic_wcheng@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox