From: Ronak Raheja <ronak.raheja@oss.qualcomm.com>
To: vkoul@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
robh@kernel.org, neil.armstrong@linaro.org,
gregkh@linuxfoundation.org
Cc: dmitry.baryshkov@oss.qualcomm.com,
konrad.dybcio@oss.qualcomm.com, abel.vesa@oss.qualcomm.com,
wesley.cheng@oss.qualcomm.com,
krzysztof.kozlowski@oss.qualcomm.com,
ronak.raheja@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/4] dt-bindings: phy: qcom,m31-eusb2-phy: Document M31 eUSB2 PHY for Hawi
Date: Mon, 27 Apr 2026 14:42:15 -0700 [thread overview]
Message-ID: <20260427214217.2735240-3-ronak.raheja@oss.qualcomm.com> (raw)
In-Reply-To: <20260427214217.2735240-1-ronak.raheja@oss.qualcomm.com>
Document the M31 eUSB2 PHY for Hawi which handles the USB2 path. Use
fallback to indicate the compatibility of the M31 eUSB2 PHY on the Hawi
with that on the SM8750.
Signed-off-by: Ronak Raheja <ronak.raheja@oss.qualcomm.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
---
Documentation/devicetree/bindings/phy/qcom,m31-eusb2-phy.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/phy/qcom,m31-eusb2-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,m31-eusb2-phy.yaml
index cd6b84213a7c..c0e7e2963ce6 100644
--- a/Documentation/devicetree/bindings/phy/qcom,m31-eusb2-phy.yaml
+++ b/Documentation/devicetree/bindings/phy/qcom,m31-eusb2-phy.yaml
@@ -19,6 +19,7 @@ properties:
- items:
- enum:
- qcom,glymur-m31-eusb2-phy
+ - qcom,hawi-m31-eusb2-phy
- qcom,kaanapali-m31-eusb2-phy
- const: qcom,sm8750-m31-eusb2-phy
- const: qcom,sm8750-m31-eusb2-phy
--
2.34.1
next prev parent reply other threads:[~2026-04-27 21:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 21:42 [PATCH v2 0/4] phy: qcom: Introduce USB support for Hawi Ronak Raheja
2026-04-27 21:42 ` [PATCH 1/4] dt-bindings: phy: qcom,sc8280xp-qmp-usb43dp-phy: Add Hawi QMP PHY Ronak Raheja
2026-04-27 21:42 ` Ronak Raheja [this message]
2026-04-27 21:42 ` [PATCH 3/4] dt-bindings: usb: qcom,snps-dwc3: Add Hawi compatible Ronak Raheja
2026-04-27 21:42 ` [PATCH 4/4] phy: qualcomm: qmp-combo: Add support for Hawi SoC Ronak Raheja
2026-04-28 8:32 ` Abel Vesa
2026-04-28 11:40 ` Dmitry Baryshkov
2026-04-29 7:28 ` Ronak Raheja
-- strict thread matches above, loose matches on Subject: below --
2026-04-25 6:59 [PATCH 0/4] phy: qcom: Introduce USB support for Hawi Ronak Raheja
2026-04-25 7:00 ` [PATCH 2/4] dt-bindings: phy: qcom,m31-eusb2-phy: Document M31 eUSB2 PHY " Ronak Raheja
2026-04-25 10:31 ` Krzysztof Kozlowski
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=20260427214217.2735240-3-ronak.raheja@oss.qualcomm.com \
--to=ronak.raheja@oss.qualcomm.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
--cc=wesley.cheng@oss.qualcomm.com \
/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