From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Stanimir Varbanov <svarbanov@mm-sol.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Krzysztof Wilczy??ski <kw@linux.com>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-phy@lists.infradead.org
Subject: Re: [PATCH v5 4/5] PCI: qcom: Add interconnect support to 2.7.0/1.9.0 ops
Date: Tue, 22 Feb 2022 15:46:30 -0800 [thread overview]
Message-ID: <YhV11gk/9+q0AVsb@ripper> (raw)
In-Reply-To: <527f0365-1544-ad73-cf49-b839ae629340@linaro.org>
On Fri 04 Feb 06:38 PST 2022, Dmitry Baryshkov wrote:
> On 03/02/2022 18:57, Bjorn Andersson wrote:
> > On Sat 18 Dec 06:10 PST 2021, Dmitry Baryshkov wrote:
> >
> > > Add optional interconnect support for the 2.7.0/1.9.0 hosts. Set the
> > > bandwidth according to the values from the downstream driver.
> > >
> >
> > What memory transactions will travel this path? I would expect there to
> > be two different paths involved, given the rather low bw numbers I
> > presume this is the config path?
>
> I think so. Downstream votes on this path for most of the known SoCs. Two
> spotted omissions are ipq8074 and qcs404.
>
Sorry, missed your reply on this one.
> >
> > Is there no vote for the data path?
>
> CNSS devices can vote additionally on the MASTER_PCI to memory paths:
> For sm845 (45 = MASTER_PCIE):
> qcom,msm-bus,vectors-KBps =
> <45 512 0 0>,
> <45 512 600000 800000>; /* ~4.6Gbps (MCS12) */
>
> On sm8150/sm8250 qca bindings do not contain a vote, but wil6210 does (100 =
> MASTER_PCIE_1):
> qcom,msm-bus,vectors-KBps =
> <100 512 0 0>,
> <100 512 600000 800000>; /* ~4.6Gbps (MCS12) */
This is PCIe -> DDR, so I think we should interconnect-names this path
"pci-ddr". I also see that on at least some platforms the value depends
on PCIe Gen. So perhaps we should start by just picking these values for
now and then follow up with something where we add the numbers in an
opp-table based on Gen?
>
> For sm8450 there are two paths used by cnss:
> <&pcie_noc MASTER_PCIE_0 &pcie_noc SLAVE_ANOC_PCIE_GEM_NOC>,
> <&gem_noc MASTER_ANOC_PCIE_GEM_NOC &mc_virt SLAVE_EBI1>;
>
> with multiple entries per each path.
>
> So, I'm not sure about these values.
>
That seems to be PCIe to master and then a separate segment for the
memory NoC to DDR. That's odd. I think we should attempt to just do:
<&pcie_noc MASTER_PCIE_0 &mc_virt SLAVE_EBI1>
As a single path for "pci-ddr"
> >
> > > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > > ---
> > > drivers/pci/controller/dwc/pcie-qcom.c | 11 +++++++++++
> > > 1 file changed, 11 insertions(+)
> > >
> > > diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
> > > index d8d400423a0a..55ac3caa6d7d 100644
> > > --- a/drivers/pci/controller/dwc/pcie-qcom.c
> > > +++ b/drivers/pci/controller/dwc/pcie-qcom.c
> > > @@ -12,6 +12,7 @@
> > > #include <linux/crc8.h>
> > > #include <linux/delay.h>
> > > #include <linux/gpio/consumer.h>
> > > +#include <linux/interconnect.h>
> > > #include <linux/interrupt.h>
> > > #include <linux/io.h>
> > > #include <linux/iopoll.h>
> > > @@ -167,6 +168,7 @@ struct qcom_pcie_resources_2_7_0 {
> > > struct clk *pipe_clk_src;
> > > struct clk *phy_pipe_clk;
> > > struct clk *ref_clk_src;
> > > + struct icc_path *path;
> > > };
> > > union qcom_pcie_resources {
> > > @@ -1121,6 +1123,10 @@ static int qcom_pcie_get_resources_2_7_0(struct qcom_pcie *pcie)
> > > if (IS_ERR(res->pci_reset))
> > > return PTR_ERR(res->pci_reset);
> > > + res->path = devm_of_icc_get(dev, "pci");
> >
> > The paths are typically identified using a string of the form
> > <source>-<destination>.
> >
> >
> > I don't see the related update to the DT binding for the introduction of
> > the interconnect.
> >
> > Regards,
> > Bjorn
> >
> > > + if (IS_ERR(res->path))
> > > + return PTR_ERR(res->path);
> > > +
> > > res->supplies[0].supply = "vdda";
> > > res->supplies[1].supply = "vddpe-3v3";
> > > ret = devm_regulator_bulk_get(dev, ARRAY_SIZE(res->supplies),
> > > @@ -1183,6 +1189,9 @@ static int qcom_pcie_init_2_7_0(struct qcom_pcie *pcie)
> > > if (pcie->cfg->pipe_clk_need_muxing)
> > > clk_set_parent(res->pipe_clk_src, res->phy_pipe_clk);
> > > + if (res->path)
> > > + icc_set_bw(res->path, 500, 800);
But that said, these numbers doesn't resemble the numbers you show
above and they don't make sense for the "data path". So perhaps this is
a separate "pci-config" path?
Regards,
Bjorn
> > > +
> > > ret = clk_bulk_prepare_enable(res->num_clks, res->clks);
> > > if (ret < 0)
> > > goto err_disable_regulators;
> > > @@ -1241,6 +1250,8 @@ static void qcom_pcie_deinit_2_7_0(struct qcom_pcie *pcie)
> > > struct qcom_pcie_resources_2_7_0 *res = &pcie->res.v2_7_0;
> > > clk_bulk_disable_unprepare(res->num_clks, res->clks);
> > > + if (res->path)
> > > + icc_set_bw(res->path, 0, 0);
> > > /* Set TCXO as clock source for pcie_pipe_clk_src */
> > > if (pcie->cfg->pipe_clk_need_muxing)
> > > --
> > > 2.34.1
> > >
>
>
> --
> With best wishes
> Dmitry
next prev parent reply other threads:[~2022-02-22 23:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 14:10 [PATCH v5 0/5] qcom: add support for PCIe on SM8450 platform Dmitry Baryshkov
2021-12-18 14:10 ` [PATCH v5 1/5] dt-bindings: pci: qcom: Document PCIe bindings for SM8450 Dmitry Baryshkov
2021-12-21 14:59 ` Rob Herring
2021-12-21 15:43 ` Dmitry Baryshkov
2021-12-21 19:52 ` Rob Herring
2021-12-21 21:09 ` Dmitry Baryshkov
2021-12-21 23:35 ` Rob Herring
2022-02-03 17:11 ` Bjorn Andersson
2021-12-18 14:10 ` [PATCH v5 2/5] PCI: qcom: Remove redundancy between qcom_pcie and qcom_pcie_cfg Dmitry Baryshkov
2022-02-03 15:47 ` Bjorn Andersson
2021-12-18 14:10 ` [PATCH v5 3/5] PCI: qcom: Add ddrss_sf_tbu flag Dmitry Baryshkov
2022-02-03 15:52 ` Bjorn Andersson
2021-12-18 14:10 ` [PATCH v5 4/5] PCI: qcom: Add interconnect support to 2.7.0/1.9.0 ops Dmitry Baryshkov
2022-02-03 15:57 ` Bjorn Andersson
2022-02-04 14:38 ` Dmitry Baryshkov
2022-02-11 16:12 ` Lorenzo Pieralisi
2022-02-22 23:47 ` Bjorn Andersson
2022-02-23 9:31 ` Lorenzo Pieralisi
2022-02-23 10:15 ` Dmitry Baryshkov
2022-02-22 23:46 ` Bjorn Andersson [this message]
2022-02-22 23:49 ` Bjorn Andersson
2022-02-23 8:37 ` Dmitry Baryshkov
2021-12-18 14:10 ` [PATCH v5 5/5] PCI: qcom: Add SM8450 PCIe support Dmitry Baryshkov
2022-02-03 17:10 ` Bjorn Andersson
2022-02-03 11:54 ` [PATCH v5 0/5] qcom: add support for PCIe on SM8450 platform Lorenzo Pieralisi
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=YhV11gk/9+q0AVsb@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kishon@ti.com \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh+dt@kernel.org \
--cc=svarbanov@mm-sol.com \
--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;
as well as URLs for NNTP newsgroup(s).