From: Rohit Agarwal <quic_rohiagar@quicinc.com>
To: agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, vkoul@kernel.org, kishon@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, gregkh@linuxfoundation.org,
abel.vesa@linaro.org, quic_wcheng@quicinc.com
Cc: linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, kernel@quicinc.com,
Rohit Agarwal <quic_rohiagar@quicinc.com>
Subject: [PATCH 1/5] dt-bindings: phy: qcom,snps-eusb2-phy: Add compatible for SDX75
Date: Tue, 5 Sep 2023 10:13:44 +0530 [thread overview]
Message-ID: <1693889028-6485-2-git-send-email-quic_rohiagar@quicinc.com> (raw)
In-Reply-To: <1693889028-6485-1-git-send-email-quic_rohiagar@quicinc.com>
Add a dt-bindings compatible string for the SDX75 SoC that
uses Synopsis eUSB2 PHY.
Signed-off-by: Rohit Agarwal <quic_rohiagar@quicinc.com>
---
Documentation/devicetree/bindings/phy/qcom,snps-eusb2-phy.yaml | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/phy/qcom,snps-eusb2-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,snps-eusb2-phy.yaml
index c53bab1..c958286 100644
--- a/Documentation/devicetree/bindings/phy/qcom,snps-eusb2-phy.yaml
+++ b/Documentation/devicetree/bindings/phy/qcom,snps-eusb2-phy.yaml
@@ -14,7 +14,12 @@ description:
properties:
compatible:
- const: qcom,sm8550-snps-eusb2-phy
+ oneOf:
+ - items:
+ - enum:
+ - qcom,sdx75-snps-eusb2-phy
+ - const: qcom,sm8550-snps-eusb2-phy
+ - const: qcom,sm8550-snps-eusb2-phy
reg:
maxItems: 1
--
2.7.4
next prev parent reply other threads:[~2023-09-05 16:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 4:43 [PATCH 0/5] Add USB Support on Qualcomm's SDX75 Platform Rohit Agarwal
2023-09-05 4:43 ` Rohit Agarwal [this message]
2023-09-05 6:47 ` [PATCH 1/5] dt-bindings: phy: qcom,snps-eusb2-phy: Add compatible for SDX75 Krzysztof Kozlowski
2023-09-05 4:43 ` [PATCH 2/5] dt-bindings: phy: Add qcom,sdx75-qmp-usb3-uni schema file Rohit Agarwal
2023-09-05 6:49 ` Krzysztof Kozlowski
2023-09-05 7:08 ` Rohit Agarwal
2023-09-05 7:20 ` Krzysztof Kozlowski
2023-09-05 7:27 ` Rohit Agarwal
2023-09-05 17:48 ` Rob Herring
2023-09-05 4:43 ` [PATCH 3/5] dt-bindings: usb: dwc3: Add missing SDX65 compatible Rohit Agarwal
2023-09-05 6:49 ` Krzysztof Kozlowski
2023-09-05 6:51 ` Krzysztof Kozlowski
2023-09-05 7:10 ` Rohit Agarwal
2023-09-05 4:43 ` [PATCH 4/5] dt-bindings: usb: dwc3: Add SDX75 compatible Rohit Agarwal
2023-09-05 6:54 ` Krzysztof Kozlowski
2023-09-05 4:43 ` [PATCH 5/5] phy: qcom-qmp-usb: Add Qualcomm SDX75 USB3 PHY support Rohit Agarwal
2023-09-05 6:53 ` Krzysztof Kozlowski
2023-09-05 7:12 ` Rohit Agarwal
2023-09-05 20:30 ` Dmitry Baryshkov
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=1693889028-6485-2-git-send-email-quic_rohiagar@quicinc.com \
--to=quic_rohiagar@quicinc.com \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@quicinc.com \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.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