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 5/5] phy: qcom-qmp-usb: Add Qualcomm SDX75 USB3 PHY support
Date: Wed, 6 Sep 2023 11:05:31 +0530 [thread overview]
Message-ID: <0d76f851-ef7a-2d09-a344-9ec31ba581a5@quicinc.com> (raw)
In-Reply-To: <8aefd8f9-cfe9-4011-a24b-ebb13d28faa0@linaro.org>
On 9/6/2023 2:08 AM, Dmitry Baryshkov wrote:
> On 05/09/2023 13:30, Rohit Agarwal wrote:
>> Add support for USB3 QMP PHY found in SDX75 platform.
>>
>> Signed-off-by: Rohit Agarwal <quic_rohiagar@quicinc.com>
>> ---
>> drivers/phy/qualcomm/phy-qcom-qmp-usb.c | 158
>> ++++++++++++++++++++++++++++++++
>> 1 file changed, 158 insertions(+)
>>
>> diff --git a/drivers/phy/qualcomm/phy-qcom-qmp-usb.c
>> b/drivers/phy/qualcomm/phy-qcom-qmp-usb.c
>> index 0130bb8..57b8b5b 100644
>> --- a/drivers/phy/qualcomm/phy-qcom-qmp-usb.c
>> +++ b/drivers/phy/qualcomm/phy-qcom-qmp-usb.c
>> @@ -23,6 +23,7 @@
>> #include "phy-qcom-qmp-pcs-misc-v3.h"
>> #include "phy-qcom-qmp-pcs-usb-v4.h"
>> #include "phy-qcom-qmp-pcs-usb-v5.h"
>> +#include "phy-qcom-qmp-pcs-usb-v6.h"
>> /* QPHY_SW_RESET bit */
>> #define SW_RESET BIT(0)
>> @@ -858,6 +859,134 @@ static const struct qmp_phy_init_tbl
>> sdx65_usb3_uniphy_rx_tbl[] = {
>
> [skipped the tables]
>
>> @@ -1556,6 +1685,32 @@ static const struct qmp_phy_cfg
>> sdx65_usb3_uniphy_cfg = {
>> .has_pwrdn_delay = true,
>> };
>> +static const struct qmp_phy_cfg sdx75_usb3_uniphy_cfg = {
>> + .lanes = 1,
>> + .offsets = &qmp_usb_offsets_v5,
>
> v6?
Since the offsets for v5 and v6 are same, I did not introduce a new
struct with the same values.
Please correct me if I have to introduce v6 offsets.
>
>> +
>> + .serdes_tbl = sdx75_usb3_uniphy_serdes_tbl,
>> + .serdes_tbl_num = ARRAY_SIZE(sdx75_usb3_uniphy_serdes_tbl),
>> + .tx_tbl = sdx75_usb3_uniphy_tx_tbl,
>> + .tx_tbl_num = ARRAY_SIZE(sdx75_usb3_uniphy_tx_tbl),
>> + .rx_tbl = sdx75_usb3_uniphy_rx_tbl,
>> + .rx_tbl_num = ARRAY_SIZE(sdx75_usb3_uniphy_rx_tbl),
>> + .pcs_tbl = sdx75_usb3_uniphy_pcs_tbl,
>> + .pcs_tbl_num = ARRAY_SIZE(sdx75_usb3_uniphy_pcs_tbl),
>> + .pcs_usb_tbl = sdx75_usb3_uniphy_pcs_usb_tbl,
>> + .pcs_usb_tbl_num = ARRAY_SIZE(sdx75_usb3_uniphy_pcs_usb_tbl),
>> + .clk_list = qmp_v4_sdx55_usbphy_clk_l,
>> + .num_clks = ARRAY_SIZE(qmp_v4_sdx55_usbphy_clk_l),
>> + .reset_list = msm8996_usb3phy_reset_l,
>> + .num_resets = ARRAY_SIZE(msm8996_usb3phy_reset_l),
>
> Clocks and resets are gone in
> https://lore.kernel.org/linux-phy/20230824211952.1397699-1-dmitry.baryshkov@linaro.org/
>
Sure.
>> + .vreg_list = qmp_phy_vreg_l,
>> + .num_vregs = ARRAY_SIZE(qmp_phy_vreg_l),
>> + .regs = qmp_v5_usb3phy_regs_layout,
>
> This must be v6, if the rest of the PHY is using v6 register names.
Same, Shall I introduce v6 struct?
Thanks,
Rohit.
>
>> + .pcs_usb_offset = 0x1000,
>> +
>> + .has_pwrdn_delay = true,
>> +};
>> +
>> static const struct qmp_phy_cfg sm8350_usb3_uniphy_cfg = {
>> .lanes = 1,
>> @@ -2256,6 +2411,9 @@ static const struct of_device_id
>> qmp_usb_of_match_table[] = {
>> .compatible = "qcom,sdx65-qmp-usb3-uni-phy",
>> .data = &sdx65_usb3_uniphy_cfg,
>> }, {
>> + .compatible = "qcom,sdx75-qmp-usb3-uni-phy",
>> + .data = &sdx75_usb3_uniphy_cfg,
>> + }, {
>> .compatible = "qcom,sm6115-qmp-usb3-phy",
>> .data = &qcm2290_usb3phy_cfg,
>> }, {
>
next prev parent reply other threads:[~2023-09-06 5:35 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
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 [this message]
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=0d76f851-ef7a-2d09-a344-9ec31ba581a5@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