From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Varadarajan Narayanan <quic_varada@quicinc.com>,
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,
gregkh@linuxfoundation.org, mturquette@baylibre.com,
sboyd@kernel.org, quic_wcheng@quicinc.com,
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, linux-clk@vger.kernel.org
Subject: Re: [PATCH v4 1/8] dt-bindings: phy: qcom,qusb2: Document IPQ9574 compatible
Date: Mon, 27 Mar 2023 13:02:18 +0300 [thread overview]
Message-ID: <24bcba8e-11e7-ecce-0e08-c9def6cc54e8@linaro.org> (raw)
In-Reply-To: <ed2abc0c260664c3039a4e7084ed9ebab1151a9a.1679909245.git.quic_varada@quicinc.com>
On 27/03/2023 12:30, Varadarajan Narayanan wrote:
> Document the compatible string used for the qusb2 phy in IPQ9574.
>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Varadarajan Narayanan <quic_varada@quicinc.com>
>
> ---
> Changes in v4:
> - Remove constraints not applicable to IPQ9574
I don't think this is a correct way to go
> Changes in v3:
> - Maintain the proper sorted order
>
> Changes in v2:
> - Moved ipq6018 to the proper place and placed ipq9574
> next to it as suggested by Dmitry
> ---
> Documentation/devicetree/bindings/phy/qcom,qusb2-phy.yaml | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/qcom,qusb2-phy.yaml b/Documentation/devicetree/bindings/phy/qcom,qusb2-phy.yaml
> index 7f403e7..3cb27da 100644
> --- a/Documentation/devicetree/bindings/phy/qcom,qusb2-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/qcom,qusb2-phy.yaml
> @@ -18,13 +18,14 @@ properties:
> oneOf:
> - items:
> - enum:
> + - qcom,ipq6018-qusb2-phy
> - qcom,ipq8074-qusb2-phy
> + - qcom,ipq9574-qusb2-phy
> - qcom,msm8953-qusb2-phy
> - qcom,msm8996-qusb2-phy
> - qcom,msm8998-qusb2-phy
> - qcom,qcm2290-qusb2-phy
> - qcom,sdm660-qusb2-phy
> - - qcom,ipq6018-qusb2-phy
> - qcom,sm4250-qusb2-phy
> - qcom,sm6115-qusb2-phy
> - items:
> @@ -157,9 +158,6 @@ required:
> - "#phy-cells"
> - clocks
> - clock-names
> - - vdd-supply
> - - vdda-pll-supply
> - - vdda-phy-dpdm-supply
So, how does ipq9574 power on the PHY?
> - resets
>
> allOf:
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-03-27 10:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 9:30 [PATCH v4 0/8] Enable IPQ9754 USB Varadarajan Narayanan
2023-03-27 9:30 ` [PATCH v4 1/8] dt-bindings: phy: qcom,qusb2: Document IPQ9574 compatible Varadarajan Narayanan
2023-03-27 10:02 ` Dmitry Baryshkov [this message]
2023-03-27 9:30 ` [PATCH v4 2/8] dt-bindings: phy: qcom,qmp-usb: Add IPQ9574 USB3 PHY Varadarajan Narayanan
2023-03-27 10:02 ` Dmitry Baryshkov
2023-03-30 7:10 ` Varadarajan Narayanan
2023-03-30 13:54 ` Krzysztof Kozlowski
2023-03-28 7:07 ` Krzysztof Kozlowski
2023-03-30 7:13 ` Varadarajan Narayanan
2023-03-27 9:30 ` [PATCH v4 3/8] dt-bindings: usb: dwc3: Add IPQ9574 compatible Varadarajan Narayanan
2023-03-28 7:11 ` Krzysztof Kozlowski
2023-03-30 7:15 ` Varadarajan Narayanan
2023-03-27 9:30 ` [PATCH v4 4/8] clk: qcom: gcc-ipq9574: Add USB related clocks Varadarajan Narayanan
2023-03-27 10:06 ` Dmitry Baryshkov
2023-03-27 9:30 ` [PATCH v4 5/8] phy: qcom-qusb2: add QUSB2 support for IPQ9574 Varadarajan Narayanan
2023-03-27 10:08 ` Dmitry Baryshkov
2023-03-27 9:30 ` [PATCH v4 6/8] phy: qcom: qmp: Update IPQ9574 USB Phy initialization Sequence Varadarajan Narayanan
2023-03-27 9:57 ` Dmitry Baryshkov
2023-03-30 7:17 ` Varadarajan Narayanan
2023-03-27 9:30 ` [PATCH v4 7/8] arm64: dts: qcom: ipq9574: Add USB related nodes Varadarajan Narayanan
2023-03-28 7:09 ` Krzysztof Kozlowski
2023-03-30 7:23 ` Varadarajan Narayanan
2023-03-27 9:31 ` [PATCH v4 8/8] arm64: dts: qcom: ipq9574: Enable USB Varadarajan Narayanan
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=24bcba8e-11e7-ecce-0e08-c9def6cc54e8@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_varada@quicinc.com \
--cc=quic_wcheng@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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
all inboxes | Powered by JetHome®