From: Johan Hovold <johan@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: "Johan Hovold" <johan+linaro@kernel.org>,
"Stanimir Varbanov" <svarbanov@mm-sol.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konrad.dybcio@somainline.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Krishna chaitanya chundru" <quic_krichai@quicinc.com>,
quic_vbadigan@quicinc.com, "Brian Masney" <bmasney@redhat.com>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] PCI: qcom: Add basic interconnect support
Date: Wed, 2 Nov 2022 09:44:56 +0100 [thread overview]
Message-ID: <Y2IuCFtbiw4H+T0C@hovoldconsulting.com> (raw)
In-Reply-To: <Y2IshhNv6JlhCbkp@hovoldconsulting.com>
On Wed, Nov 02, 2022 at 09:38:31AM +0100, Johan Hovold wrote:
> On Tue, Nov 01, 2022 at 08:05:29PM +0530, Manivannan Sadhasivam wrote:
> > On Fri, Oct 21, 2022 at 08:46:16AM +0200, Johan Hovold wrote:
> > > On Qualcomm platforms like SC8280XP and SA8540P, interconnect bandwidth
> > > must be requested before enabling interconnect clocks.
> > >
> > > Add basic support for managing an optional "pcie-mem" interconnect path
> > > by setting a low constraint before enabling clocks and updating it after
> > > the link is up.
> > >
> > > Note that it is not possible for a controller driver to set anything but
> > > a maximum peak bandwidth as expected average bandwidth will vary with
> > > use case and actual use (and power policy?). This very much remains an
> > > unresolved problem with the interconnect framework.
> > >
> > > Also note that no constraint is set for the SC8280XP/SA8540P "cpu-pcie"
> > > path for now as it is not clear what an appropriate constraint would be
> > > (and the system does not crash when left unspecified).
> > > + }
> > > +
> > > + /*
> > > + * Some Qualcomm platforms require interconnect bandwidth constraints
> > > + * to be set before enabling interconnect clocks.
> > > + *
> > > + * Set an initial peak bandwidth corresponding to single-lane Gen 1
> > > + * for the pcie-mem path.
> > > + */
> > > + ret = icc_set_bw(pcie->icc_mem, 0, MBps_to_icc(250));
> > > + if (ret) {
> > > + dev_err(pci->dev, "failed to set interconnect bandwidth: %d\n",
> > > + ret);
> >
> > Move "ret);" to prior line. No need to keep up within 80 columns.
>
> 80 chars is still a soft limit and in this case there's no real gain in
> terms of readability from breaking it.
>
> But sure, I can remove the line break.
After looking at the result, I changed my mind here and will stick to
the 80 char limit.
Johan
prev parent reply other threads:[~2022-11-02 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 6:46 [PATCH v2 0/2] PCI: qcom: Add basic interconnect support Johan Hovold
2022-10-21 6:46 ` [PATCH v2 1/2] dt-bindings: PCI: qcom: Add SC8280XP/SA8540P interconnects Johan Hovold
2022-10-24 16:58 ` Rob Herring
2022-11-01 14:37 ` Manivannan Sadhasivam
2022-10-21 6:46 ` [PATCH v2 2/2] PCI: qcom: Add basic interconnect support Johan Hovold
2022-11-01 11:38 ` Georgi Djakov
2022-11-01 14:35 ` Manivannan Sadhasivam
2022-11-02 8:38 ` Johan Hovold
2022-11-02 8:44 ` Johan Hovold [this message]
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=Y2IuCFtbiw4H+T0C@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=bmasney@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.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=mani@kernel.org \
--cc=quic_krichai@quicinc.com \
--cc=quic_vbadigan@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=svarbanov@mm-sol.com \
/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