From: Mayank Rana <quic_mrana@quicinc.com>
To: <neil.armstrong@linaro.org>, <jingoohan1@gmail.com>,
<manivannan.sadhasivam@linaro.org>, <will@kernel.org>,
<lpieralisi@kernel.org>, <kw@linux.com>, <robh@kernel.org>,
<bhelgaas@google.com>, <krzk@kernel.org>
Cc: <linux-pci@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_krichai@quicinc.com>
Subject: Re: [PATCH v3 4/4] PCI: qcom: Add Qualcomm SA8255p based PCIe root complex functionality
Date: Thu, 7 Nov 2024 09:45:37 -0800 [thread overview]
Message-ID: <7cfc0657-e8f4-45a8-95e2-668476ffce17@quicinc.com> (raw)
In-Reply-To: <a1f03a33-22b2-4023-8185-d15abc72bc8a@linaro.org>
On 11/7/2024 12:45 AM, neil.armstrong@linaro.org wrote:
> Hi,
>
> On 06/11/2024 23:13, Mayank Rana wrote:
>> On SA8255p ride platform, PCIe root complex is firmware managed as well
>> configured into ECAM compliant mode. This change adds functionality to
>> enable resource management (system resource as well PCIe controller and
>> PHY configuration) through firmware, and enumerating ECAM compliant root
>> complex.
>>
>> Signed-off-by: Mayank Rana <quic_mrana@quicinc.com>
>> ---
>> drivers/pci/controller/dwc/Kconfig | 1 +
>> drivers/pci/controller/dwc/pcie-qcom.c | 116 +++++++++++++++++++++++--
>> 2 files changed, 108 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/pci/controller/dwc/Kconfig
>> b/drivers/pci/controller/dwc/Kconfig
>> index b6d6778b0698..0fe76bd39d69 100644
>> --- a/drivers/pci/controller/dwc/Kconfig
>> +++ b/drivers/pci/controller/dwc/Kconfig
>> @@ -275,6 +275,7 @@ config PCIE_QCOM
>> select PCIE_DW_HOST
>> select CRC8
>> select PCIE_QCOM_COMMON
>> + select PCI_HOST_COMMON
>> help
>> Say Y here to enable PCIe controller support on Qualcomm SoCs.
>> The
>> PCIe controller uses the DesignWare core plus Qualcomm-specific
>> diff --git a/drivers/pci/controller/dwc/pcie-qcom.c
>> b/drivers/pci/controller/dwc/pcie-qcom.c
>> index ef44a82be058..2cb74f902baf 100644
>> --- a/drivers/pci/controller/dwc/pcie-qcom.c
>> +++ b/drivers/pci/controller/dwc/pcie-qcom.c
>> @@ -21,7 +21,9 @@
>> #include <linux/limits.h>
>> #include <linux/init.h>
>> #include <linux/of.h>
>> +#include <linux/of_pci.h>
>> #include <linux/pci.h>
>> +#include <linux/pci-ecam.h>
>> #include <linux/pm_opp.h>
>> #include <linux/pm_runtime.h>
>> #include <linux/platform_device.h>
>> @@ -254,10 +256,12 @@ struct qcom_pcie_ops {
>> * @ops: qcom PCIe ops structure
>> * @override_no_snoop: Override NO_SNOOP attribute in TLP to enable
>> cache
>> * snooping
>> + * @firmware_managed: Set if PCIe root complex is firmware managed
>> */
>> struct qcom_pcie_cfg {
>> const struct qcom_pcie_ops *ops;
>> bool override_no_snoop;
>> + bool firmware_managed;
>> bool no_l0s;
>> };
>> @@ -1415,6 +1419,10 @@ static const struct qcom_pcie_cfg cfg_sc8280xp = {
>> .no_l0s = true,
>> };
>> +static const struct qcom_pcie_cfg cfg_fw_managed = {
>> + .firmware_managed = true,
>> +};
>> +
>> static const struct dw_pcie_ops dw_pcie_ops = {
>> .link_up = qcom_pcie_link_up,
>> .start_link = qcom_pcie_start_link,
>> @@ -1566,6 +1574,51 @@ static irqreturn_t
>> qcom_pcie_global_irq_thread(int irq, void *data)
>> return IRQ_HANDLED;
>> }
>> +static void qcom_pci_free_msi(void *ptr)
>> +{
>> + struct dw_pcie_rp *pp = (struct dw_pcie_rp *)ptr;
>> +
>> + if (pp && pp->has_msi_ctrl)
>> + dw_pcie_free_msi(pp);
>> +}
>> +
>> +static int qcom_pcie_ecam_host_init(struct pci_config_window *cfg)
>> +{
>> + struct device *dev = cfg->parent;
>> + struct dw_pcie_rp *pp;
>> + struct dw_pcie *pci;
>> + int ret;
>> +
>> + pci = devm_kzalloc(dev, sizeof(*pci), GFP_KERNEL);
>> + if (!pci)
>> + return -ENOMEM;
>> +
>> + pci->dev = dev;
>> + pp = &pci->pp;
>> + pci->dbi_base = cfg->win;
>> + pp->num_vectors = MSI_DEF_NUM_VECTORS;
>> +
>> + ret = dw_pcie_msi_host_init(pp);
>> + if (ret)
>> + return ret;
>> +
>> + pp->has_msi_ctrl = true;
>> + dw_pcie_msi_init(pp);
>> +
>> + ret = devm_add_action_or_reset(dev, qcom_pci_free_msi, pp);
>> + return ret;
>> +}
>> +
>> +/* ECAM ops */
>> +const struct pci_ecam_ops pci_qcom_ecam_ops = {
>> + .init = qcom_pcie_ecam_host_init,
>> + .pci_ops = {
>> + .map_bus = pci_ecam_map_bus,
>> + .read = pci_generic_config_read,
>> + .write = pci_generic_config_write,
>> + }
>> +};
>> +
>> static int qcom_pcie_probe(struct platform_device *pdev)
>> {
>> const struct qcom_pcie_cfg *pcie_cfg;
>> @@ -1580,11 +1633,52 @@ static int qcom_pcie_probe(struct
>> platform_device *pdev)
>> char *name;
>> pcie_cfg = of_device_get_match_data(dev);
>> - if (!pcie_cfg || !pcie_cfg->ops) {
>> - dev_err(dev, "Invalid platform data\n");
>> + if (!pcie_cfg) {
>> + dev_err(dev, "No platform data\n");
>> + return -EINVAL;
>> + }
>> +
>> + if (!pcie_cfg->firmware_managed && !pcie_cfg->ops) {
>> + dev_err(dev, "No platform ops\n");
>> return -EINVAL;
>> }
>> + pm_runtime_enable(dev);
>> + ret = pm_runtime_get_sync(dev);
>> + if (ret < 0)
>> + goto err_pm_runtime_put;
>> +
>> + if (pcie_cfg->firmware_managed) {
>> + struct pci_host_bridge *bridge;
>> + struct pci_config_window *cfg;
>> +
>> + bridge = devm_pci_alloc_host_bridge(dev, 0);
>> + if (!bridge) {
>> + ret = -ENOMEM;
>> + goto err_pm_runtime_put;
>> + }
>> +
>> + of_pci_check_probe_only();
>> + /* Parse and map our Configuration Space windows */
>> + cfg = gen_pci_init(dev, bridge, &pci_qcom_ecam_ops);
>> + if (IS_ERR(cfg)) {
>> + ret = PTR_ERR(cfg);
>> + goto err_pm_runtime_put;
>> + }
>> +
>> + bridge->sysdata = cfg;
>> + bridge->ops = (struct pci_ops *)&pci_qcom_ecam_ops.pci_ops;
>> + bridge->msi_domain = true;
>> +
>> + ret = pci_host_probe(bridge);
>> + if (ret) {
>> + dev_err(dev, "pci_host_probe() failed:%d\n", ret);
>> + goto err_pm_runtime_put;
>> + }
>> +
>> + return ret;
>> + }
>> +
>> pcie = devm_kzalloc(dev, sizeof(*pcie), GFP_KERNEL);
>> if (!pcie)
>> return -ENOMEM;
>> @@ -1593,11 +1687,6 @@ static int qcom_pcie_probe(struct
>> platform_device *pdev)
>> if (!pci)
>> return -ENOMEM;
>> - pm_runtime_enable(dev);
>> - ret = pm_runtime_get_sync(dev);
>> - if (ret < 0)
>> - goto err_pm_runtime_put;
>> -
>> pci->dev = dev;
>> pci->ops = &dw_pcie_ops;
>> pp = &pci->pp;
>> @@ -1739,9 +1828,13 @@ static int qcom_pcie_probe(struct
>> platform_device *pdev)
>> static int qcom_pcie_suspend_noirq(struct device *dev)
>> {
>> - struct qcom_pcie *pcie = dev_get_drvdata(dev);
>> + struct qcom_pcie *pcie;
>> int ret = 0;
>> + if (of_device_is_compatible(dev->of_node, "qcom,pcie-sa8255p"))
>
> Can't you use if (pcie_cfg->firmware_managed) here instead ?
yes, although with firmware managed mode, struct qcom_pcie *pcie is not
allocated, and just
to get access to pcie_cfg for this check, I took this approach. I am
thiking to do allocating struct qcom_pcie *pcie and using it in future
if we need more other related functionality which needs usage of this
structure for functionality like global interrupt etc.
Although if you still prefer to allocate struct qcom_pcie based memory
to access pcie_cfg, then I can consider to update in next patchset.
Please suggest.
>> + return 0;
>> +
>> + pcie = dev_get_drvdata(dev);
>> /*
>> * Set minimum bandwidth required to keep data path functional
>> during
>> * suspend.
>> @@ -1795,9 +1888,13 @@ static int qcom_pcie_suspend_noirq(struct
>> device *dev)
>> static int qcom_pcie_resume_noirq(struct device *dev)
>> {
>> - struct qcom_pcie *pcie = dev_get_drvdata(dev);
>> + struct qcom_pcie *pcie;
>> int ret;
>> + if (of_device_is_compatible(dev->of_node, "qcom,pcie-sa8255p"))
>
> Ditto
>
>> + return 0;
>> +
>> + pcie = dev_get_drvdata(dev);
>> if (pm_suspend_target_state != PM_SUSPEND_MEM) {
>> ret = icc_enable(pcie->icc_cpu);
>> if (ret) {
>> @@ -1830,6 +1927,7 @@ static const struct of_device_id
>> qcom_pcie_match[] = {
>> { .compatible = "qcom,pcie-ipq8074-gen3", .data = &cfg_2_9_0 },
>> { .compatible = "qcom,pcie-msm8996", .data = &cfg_2_3_2 },
>> { .compatible = "qcom,pcie-qcs404", .data = &cfg_2_4_0 },
>> + { .compatible = "qcom,pcie-sa8255p", .data = &cfg_fw_managed },
>> { .compatible = "qcom,pcie-sa8540p", .data = &cfg_sc8280xp },
>> { .compatible = "qcom,pcie-sa8775p", .data = &cfg_1_34_0},
>> { .compatible = "qcom,pcie-sc7280", .data = &cfg_1_9_0 },
>
> Thanks,
> Neil
Regards,
Mayank
next prev parent reply other threads:[~2024-11-07 17:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 22:13 [PATCH v3 0/4] Add Qualcomm SA8255p based firmware managed PCIe root complex Mayank Rana
2024-11-06 22:13 ` [PATCH v3 1/4] PCI: dwc: Export dwc MSI controller related APIs Mayank Rana
2024-11-15 9:14 ` Manivannan Sadhasivam
2024-11-15 18:15 ` Mayank Rana
2024-11-06 22:13 ` [PATCH v3 2/4] PCI: host-generic: Export gen_pci_init() API to allow ECAM creation Mayank Rana
2024-11-15 9:17 ` Manivannan Sadhasivam
2024-11-15 18:16 ` Mayank Rana
2024-11-06 22:13 ` [PATCH v3 3/4] dt-bindings: PCI: qcom,pcie-sa8255p: Document ECAM compliant PCIe root complex Mayank Rana
2024-11-07 9:35 ` Krzysztof Kozlowski
2024-11-07 17:39 ` Mayank Rana
2024-11-15 10:55 ` Manivannan Sadhasivam
2024-11-06 22:13 ` [PATCH v3 4/4] PCI: qcom: Add Qualcomm SA8255p based PCIe root complex functionality Mayank Rana
2024-11-07 8:45 ` neil.armstrong
2024-11-07 17:45 ` Mayank Rana [this message]
2024-11-08 10:22 ` neil.armstrong
2024-11-15 11:21 ` Manivannan Sadhasivam
2024-11-15 18:17 ` Mayank Rana
2024-11-09 23:45 ` kernel test robot
2024-11-15 11:25 ` Manivannan Sadhasivam
2024-11-15 18:28 ` Mayank Rana
2024-11-19 17:14 ` Manivannan Sadhasivam
2024-11-15 11:28 ` [PATCH v3 0/4] Add Qualcomm SA8255p based firmware managed PCIe root complex Manivannan Sadhasivam
2024-11-15 18:31 ` Mayank Rana
2024-11-19 17:10 ` Manivannan Sadhasivam
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=7cfc0657-e8f4-45a8-95e2-668476ffce17@quicinc.com \
--to=quic_mrana@quicinc.com \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=krzk@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_krichai@quicinc.com \
--cc=robh@kernel.org \
--cc=will@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