From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> To: Abel Vesa <abel.vesa@linaro.org> Cc: Andy Gross <agross@kernel.org>, Bjorn Andersson <andersson@kernel.org>, Konrad Dybcio <konrad.dybcio@linaro.org>, "vkoul@kernel.org" <vkoul@kernel.org>, Kishon Vijay Abraham I <kishon@kernel.org>, Rob Herring <robh@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, Neil Armstrong <neil.armstrong@linaro.org> Subject: Re: [PATCH 07/10] phy: qualcomm: qmp-pcie: Add support for SM8550 g3x2 and g4x2 PCIEs Date: Tue, 17 Jan 2023 16:08:10 +0200 [thread overview] Message-ID: <f7ce2f70-9764-9be9-64fa-b60fc7e72cc8@linaro.org> (raw) In-Reply-To: <Y8apUXpfAyaMMmH/@linaro.org> On 17/01/2023 15:57, Abel Vesa wrote: > On 23-01-01 22:15:55, Dmitry Baryshkov wrote: >> On 16/11/2022 14:01, Abel Vesa wrote: >>> Add the SM8550 both g4 and g3 configurations. In addition, there is a >>> new "lane shared" table that needs to be configured for g4, along with >>> the No-CSR list of resets. >>> >>> Co-developed-by: Neil Armstrong <neil.armstrong@linaro.org> >>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org> >>> Signed-off-by: Abel Vesa <abel.vesa@linaro.org> >>> --- >>> drivers/phy/qualcomm/phy-qcom-qmp-pcie.c | 354 +++++++++++++++++++++++ >>> 1 file changed, 354 insertions(+) >>> >>> diff --git a/drivers/phy/qualcomm/phy-qcom-qmp-pcie.c b/drivers/phy/qualcomm/phy-qcom-qmp-pcie.c >>> index 47cccc4b35b2..87c7c20dfc8d 100644 >>> --- a/drivers/phy/qualcomm/phy-qcom-qmp-pcie.c >>> +++ b/drivers/phy/qualcomm/phy-qcom-qmp-pcie.c >> >> [skipped tables] >> >>> @@ -1473,6 +1701,8 @@ struct qmp_pcie_offsets { >>> struct qmp_phy_cfg_tbls { >>> const struct qmp_phy_init_tbl *serdes; >>> int serdes_num; >>> + const struct qmp_phy_init_tbl *ln_shrd_serdes; >>> + int ln_shrd_serdes_num; >>> const struct qmp_phy_init_tbl *tx; >>> int tx_num; >>> const struct qmp_phy_init_tbl *rx; >>> @@ -1510,6 +1740,9 @@ struct qmp_phy_cfg { >>> /* resets to be requested */ >>> const char * const *reset_list; >>> int num_resets; >>> + /* no CSR resets to be requested */ >>> + const char * const *nocsr_reset_list; >>> + int num_nocsr_resets; >> >> Is there any difference between 'no CSR' resets and the plain ones? Can we >> handle them in a single array instead? > > Yes, on power on, only the 'No CSR' are necessary to be deasserted. > > So we need to differentiate between 'No CSR' and the rest. Ack. > >> >>> /* regulators to be requested */ >>> const char * const *vreg_list; >>> int num_vregs; [skipped] >>> @@ -2502,6 +2847,9 @@ static int qmp_pcie_parse_dt_legacy(struct qmp_pcie *qmp, struct device_node *np >>> return PTR_ERR(qmp->rx2); >>> qmp->pcs_misc = devm_of_iomap(dev, np, 5, NULL); >>> + >>> + if (cfg->has_ln_shrd_serdes_tbl) >>> + qmp->ln_shrd_serdes = devm_of_iomap(dev, np, 6, NULL); >> >> I think we also need to check the returned value. Also, I think we can drop >> the conditional check here. we don't have to validate the DT, so if the reg >> is present in DT, then it's present. If not, it's not required. > > Yeah, but I was trying to make sure that if there is a new type of reg > for some upcomming SoC, we don't take that as ln_shrd. That's why the check > was added. > > I'll add the returned value check though. This is the parse_dt_legacy() function. I think we can leave it as is and support sm8550 only using the new style of parsing. > >> >>> } else { >>> qmp->pcs_misc = devm_of_iomap(dev, np, 3, NULL); >>> } >>> @@ -2729,6 +3077,12 @@ static const struct of_device_id qmp_pcie_of_match_table[] = { >>> }, { >>> .compatible = "qcom,sm8450-qmp-gen4x2-pcie-phy", >>> .data = &sm8450_qmp_gen4x2_pciephy_cfg, >>> + }, { >>> + .compatible = "qcom,sm8550-qmp-gen3x2-pcie-phy", >>> + .data = &sm8550_qmp_gen3x2_pciephy_cfg, >>> + }, { >>> + .compatible = "qcom,sm8550-qmp-gen4x2-pcie-phy", >>> + .data = &sm8550_qmp_gen4x2_pciephy_cfg, >>> }, >>> { }, >>> }; >> >> -- >> With best wishes >> Dmitry >> -- With best wishes Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> To: Abel Vesa <abel.vesa@linaro.org> Cc: Andy Gross <agross@kernel.org>, Bjorn Andersson <andersson@kernel.org>, Konrad Dybcio <konrad.dybcio@linaro.org>, "vkoul@kernel.org" <vkoul@kernel.org>, Kishon Vijay Abraham I <kishon@kernel.org>, Rob Herring <robh@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org, Neil Armstrong <neil.armstrong@linaro.org> Subject: Re: [PATCH 07/10] phy: qualcomm: qmp-pcie: Add support for SM8550 g3x2 and g4x2 PCIEs Date: Tue, 17 Jan 2023 16:08:10 +0200 [thread overview] Message-ID: <f7ce2f70-9764-9be9-64fa-b60fc7e72cc8@linaro.org> (raw) In-Reply-To: <Y8apUXpfAyaMMmH/@linaro.org> On 17/01/2023 15:57, Abel Vesa wrote: > On 23-01-01 22:15:55, Dmitry Baryshkov wrote: >> On 16/11/2022 14:01, Abel Vesa wrote: >>> Add the SM8550 both g4 and g3 configurations. In addition, there is a >>> new "lane shared" table that needs to be configured for g4, along with >>> the No-CSR list of resets. >>> >>> Co-developed-by: Neil Armstrong <neil.armstrong@linaro.org> >>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org> >>> Signed-off-by: Abel Vesa <abel.vesa@linaro.org> >>> --- >>> drivers/phy/qualcomm/phy-qcom-qmp-pcie.c | 354 +++++++++++++++++++++++ >>> 1 file changed, 354 insertions(+) >>> >>> diff --git a/drivers/phy/qualcomm/phy-qcom-qmp-pcie.c b/drivers/phy/qualcomm/phy-qcom-qmp-pcie.c >>> index 47cccc4b35b2..87c7c20dfc8d 100644 >>> --- a/drivers/phy/qualcomm/phy-qcom-qmp-pcie.c >>> +++ b/drivers/phy/qualcomm/phy-qcom-qmp-pcie.c >> >> [skipped tables] >> >>> @@ -1473,6 +1701,8 @@ struct qmp_pcie_offsets { >>> struct qmp_phy_cfg_tbls { >>> const struct qmp_phy_init_tbl *serdes; >>> int serdes_num; >>> + const struct qmp_phy_init_tbl *ln_shrd_serdes; >>> + int ln_shrd_serdes_num; >>> const struct qmp_phy_init_tbl *tx; >>> int tx_num; >>> const struct qmp_phy_init_tbl *rx; >>> @@ -1510,6 +1740,9 @@ struct qmp_phy_cfg { >>> /* resets to be requested */ >>> const char * const *reset_list; >>> int num_resets; >>> + /* no CSR resets to be requested */ >>> + const char * const *nocsr_reset_list; >>> + int num_nocsr_resets; >> >> Is there any difference between 'no CSR' resets and the plain ones? Can we >> handle them in a single array instead? > > Yes, on power on, only the 'No CSR' are necessary to be deasserted. > > So we need to differentiate between 'No CSR' and the rest. Ack. > >> >>> /* regulators to be requested */ >>> const char * const *vreg_list; >>> int num_vregs; [skipped] >>> @@ -2502,6 +2847,9 @@ static int qmp_pcie_parse_dt_legacy(struct qmp_pcie *qmp, struct device_node *np >>> return PTR_ERR(qmp->rx2); >>> qmp->pcs_misc = devm_of_iomap(dev, np, 5, NULL); >>> + >>> + if (cfg->has_ln_shrd_serdes_tbl) >>> + qmp->ln_shrd_serdes = devm_of_iomap(dev, np, 6, NULL); >> >> I think we also need to check the returned value. Also, I think we can drop >> the conditional check here. we don't have to validate the DT, so if the reg >> is present in DT, then it's present. If not, it's not required. > > Yeah, but I was trying to make sure that if there is a new type of reg > for some upcomming SoC, we don't take that as ln_shrd. That's why the check > was added. > > I'll add the returned value check though. This is the parse_dt_legacy() function. I think we can leave it as is and support sm8550 only using the new style of parsing. > >> >>> } else { >>> qmp->pcs_misc = devm_of_iomap(dev, np, 3, NULL); >>> } >>> @@ -2729,6 +3077,12 @@ static const struct of_device_id qmp_pcie_of_match_table[] = { >>> }, { >>> .compatible = "qcom,sm8450-qmp-gen4x2-pcie-phy", >>> .data = &sm8450_qmp_gen4x2_pciephy_cfg, >>> + }, { >>> + .compatible = "qcom,sm8550-qmp-gen3x2-pcie-phy", >>> + .data = &sm8550_qmp_gen3x2_pciephy_cfg, >>> + }, { >>> + .compatible = "qcom,sm8550-qmp-gen4x2-pcie-phy", >>> + .data = &sm8550_qmp_gen4x2_pciephy_cfg, >>> }, >>> { }, >>> }; >> >> -- >> With best wishes >> Dmitry >> -- With best wishes Dmitry -- linux-phy mailing list linux-phy@lists.infradead.org https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2023-01-17 14:08 UTC|newest] Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-16 12:01 [PATCH 00/10] phy: qualcomm: Add support for SM8550 Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2022-11-16 12:01 ` [PATCH 01/10] phy: qcom-qmp: qserdes-com: Add v6 register offsets Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2022-11-24 17:54 ` Vinod Koul 2022-11-24 17:54 ` Vinod Koul 2022-11-16 12:01 ` [PATCH 02/10] dt-bindings: phy: Add QMP UFS PHY comptible for SM8550 Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2022-11-16 13:46 ` Johan Hovold 2022-11-16 13:46 ` Johan Hovold 2022-11-16 12:01 ` [PATCH 03/10] phy: qcom-qmp-ufs: Add SM8550 support Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2022-11-17 15:36 ` kernel test robot 2022-11-17 15:36 ` kernel test robot 2022-11-24 17:55 ` Vinod Koul 2022-11-24 17:55 ` Vinod Koul 2022-11-16 12:01 ` [PATCH 04/10] dt-bindings: phy: qcom,qmp-usb: Document SM8550 compatible Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2022-11-16 13:46 ` Johan Hovold 2022-11-16 13:46 ` Johan Hovold 2023-01-23 10:19 ` Johan Hovold 2023-01-23 10:19 ` Johan Hovold 2023-01-23 10:48 ` Abel Vesa 2023-01-23 10:48 ` Abel Vesa 2023-01-23 10:49 ` Johan Hovold 2023-01-23 10:49 ` Johan Hovold 2022-11-16 12:01 ` [PATCH 05/10] phy: qualcomm: qmp-usb: Add support for SM8550 Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2022-11-17 16:17 ` kernel test robot 2022-11-17 16:17 ` kernel test robot 2022-11-24 17:56 ` Vinod Koul 2022-11-24 17:56 ` Vinod Koul 2022-11-16 12:01 ` [PATCH 06/10] dt-bindings: phy: qcom,qmp-pcie: Document SM8550 compatible Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2022-11-16 13:47 ` Johan Hovold 2022-11-16 13:47 ` Johan Hovold 2022-11-16 12:01 ` [PATCH 07/10] phy: qualcomm: qmp-pcie: Add support for SM8550 g3x2 and g4x2 PCIEs Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2023-01-01 20:15 ` Dmitry Baryshkov 2023-01-01 20:15 ` Dmitry Baryshkov 2023-01-17 13:57 ` Abel Vesa 2023-01-17 13:57 ` Abel Vesa 2023-01-17 14:08 ` Dmitry Baryshkov [this message] 2023-01-17 14:08 ` Dmitry Baryshkov 2022-11-16 12:01 ` [PATCH 08/10] dt-bindings: phy: Add qcom,snps-eusb2-phy schema file Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2022-11-16 15:29 ` Rob Herring 2022-11-16 15:29 ` Rob Herring 2022-11-16 15:44 ` Rob Herring 2022-11-16 15:44 ` Rob Herring 2022-11-16 12:01 ` [PATCH 09/10] phy: qualcomm: Add QCOM SNPS eUSB2 driver Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2022-11-24 18:01 ` Vinod Koul 2022-11-24 18:01 ` Vinod Koul 2022-11-16 12:01 ` [PATCH 10/10] phy: qualcomm: phy-qcom-snps-eusb2: Add support for eUSB2 repeater Abel Vesa 2022-11-16 12:01 ` Abel Vesa 2022-11-17 1:43 ` kernel test robot 2022-11-17 1:43 ` kernel test robot
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=f7ce2f70-9764-9be9-64fa-b60fc7e72cc8@linaro.org \ --to=dmitry.baryshkov@linaro.org \ --cc=abel.vesa@linaro.org \ --cc=agross@kernel.org \ --cc=andersson@kernel.org \ --cc=devicetree@vger.kernel.org \ --cc=kishon@kernel.org \ --cc=konrad.dybcio@linaro.org \ --cc=krzysztof.kozlowski@linaro.org \ --cc=linux-arm-msm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-phy@lists.infradead.org \ --cc=neil.armstrong@linaro.org \ --cc=robh@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.