From: Rohit Agarwal <quic_rohiagar@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
<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>
Subject: Re: [PATCH v2 2/5] dt-bindings: phy: qcom,qmp-usb: Add SDX75 USB3 PHY
Date: Wed, 6 Sep 2023 10:56:05 +0530 [thread overview]
Message-ID: <1838845b-9586-6f8c-a4d6-ef052e0a12db@quicinc.com> (raw)
In-Reply-To: <ea9df6f3-dfde-ea7a-af22-2a0839d82d32@quicinc.com>
On 9/6/2023 10:52 AM, Rohit Agarwal wrote:
>
> On 9/6/2023 2:04 AM, Dmitry Baryshkov wrote:
>> On 05/09/2023 13:30, Rohit Agarwal wrote:
>>> Add dt-bindings for USB3 PHY found on Qualcomm SDX75.
>>>
>>> Signed-off-by: Rohit Agarwal <quic_rohiagar@quicinc.com>
>>> ---
>>> .../phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml | 40
>>> ++++++++++++++++++++--
>>> 1 file changed, 37 insertions(+), 3 deletions(-)
>>>
>>> diff --git
>>> a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
>>> b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
>>>
>>> index f99fbbc..5725620 100644
>>> ---
>>> a/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
>>> +++
>>> b/Documentation/devicetree/bindings/phy/qcom,sc8280xp-qmp-usb3-uni-phy.yaml
>>> @@ -20,6 +20,7 @@ properties:
>>> - qcom,qcm2290-qmp-usb3-phy
>>> - qcom,sa8775p-qmp-usb3-uni-phy
>>> - qcom,sc8280xp-qmp-usb3-uni-phy
>>> + - qcom,sdx75-qmp-usb3-uni-phy
>>
>> I think the ident is wrong here.
>
> Same. Somehow, your reply has the issue but original not able to see.
>
>>
>>> - qcom,sm6115-qmp-usb3-phy
>>> reg:
>>> @@ -38,9 +39,7 @@ properties:
>>> maxItems: 2
>>> reset-names:
>>> - items:
>>> - - const: phy
>>> - - const: phy_phy
>>> + maxItems: 2
>>> vdda-phy-supply: true
>>> @@ -75,6 +74,7 @@ allOf:
>>> contains:
>>> enum:
>>> - qcom,ipq9574-qmp-usb3-phy
>>> + - qcom,sdx75-qmp-usb3-uni-phy
>>> then:
>>> properties:
>>> clock-names:
>>> @@ -122,6 +122,40 @@ allOf:
>>> required:
>>> - power-domains
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - qcom,ipq9574-qmp-usb3-phy
>>> + - qcom,qcm2290-qmp-usb3-phy
>>> + - qcom,sa8775p-qmp-usb3-uni-phy
>>> + - qcom,sc8280xp-qmp-usb3-uni-phy
>>> + - qcom,sm6115-qmp-usb3-phy
>>> + then:
>>> + properties:
>>> + resets:
>>> + maxItems: 2
>>> + reset-names:
>>> + items:
>>> + - const: phy
>>> + - const: phy_phy
>>> +
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + contains:
>>> + enum:
>>> + - qcom,sdx75-qmp-usb3-uni-phy
>>> + then:
>>> + properties:
>>> + resets:
>>> + maxItems: 2
>>> + reset-names:
>>> + items:
>>> + - const: phy
>>> + - const: common
>>
>> Could you please point us to the actual DTS patch adding this PHY?
>> I'd say, it is highly likely that you are trying to bring in the
>> unnecessary change.
> I have not posted the dt patches yet. But sdx75 uses these resets.
> GCC_USB3PHY_PHY_BCR, GCC_USB3_PHY_BCR
>
> These are same as sdx65 and sdx55.
Ok I see in your patch
https://lore.kernel.org/linux-phy/20230824211952.1397699-17-dmitry.baryshkov@linaro.org/
you are updating the resets name. Fine, this change becomes unnecessary.
Will rebase my change on your patches.
Thanks,
Rohit.
>
> Thanks,
> Rohit.
>
>>
>>> +
>>> additionalProperties: false
>>> examples:
>>
next prev parent reply other threads:[~2023-09-06 5:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 10:30 [PATCH v2 0/5] Add USB Support on Qualcomm's SDX75 Platform Rohit Agarwal
2023-09-05 10:30 ` [PATCH v2 1/5] dt-bindings: phy: qcom,snps-eusb2-phy: Add compatible for SDX75 Rohit Agarwal
2023-09-05 10:30 ` [PATCH v2 2/5] dt-bindings: phy: qcom,qmp-usb: Add SDX75 USB3 PHY Rohit Agarwal
2023-09-05 20:34 ` Dmitry Baryshkov
2023-09-06 5:22 ` Rohit Agarwal
2023-09-06 5:26 ` Rohit Agarwal [this message]
2023-09-06 5:39 ` Dmitry Baryshkov
2023-09-06 5:45 ` Rohit Agarwal
2023-09-05 10:30 ` [PATCH v2 3/5] dt-bindings: usb: qcom,dwc3: Fix SDX65 clocks Rohit Agarwal
2023-09-05 18:17 ` Rob Herring
2023-09-05 20:35 ` Dmitry Baryshkov
2023-09-06 5:10 ` Rohit Agarwal
2023-09-06 5:38 ` Dmitry Baryshkov
2023-09-05 10:30 ` [PATCH v2 4/5] dt-bindings: usb: dwc3: Add SDX75 compatible Rohit Agarwal
2023-09-05 10:30 ` [PATCH v2 5/5] phy: qcom-qmp-usb: Add Qualcomm SDX75 USB3 PHY support Rohit Agarwal
2023-09-05 20:38 ` Dmitry Baryshkov
2023-09-06 5:35 ` Rohit Agarwal
2023-09-06 5:41 ` Dmitry Baryshkov
2023-09-06 5:44 ` Rohit Agarwal
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=1838845b-9586-6f8c-a4d6-ef052e0a12db@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=dmitry.baryshkov@linaro.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