From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Bjorn Andersson" <andersson@kernel.org>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Johan Hovold" <johan+linaro@kernel.org>,
"Marijn Suijten" <marijn.suijten@somainline.org>,
"Bjorn Andersson" <quic_bjorande@quicinc.com>
Subject: Re: [PATCH v3 2/2] PCI: qcom: properly implement RC shutdown/power up
Date: Wed, 27 Mar 2024 22:27:15 +0100 [thread overview]
Message-ID: <fc72ee13-db3d-423a-9ac2-15b13f42ef5e@linaro.org> (raw)
In-Reply-To: <20240327212050.GA1538555@bhelgaas>
On 27.03.2024 10:20 PM, Bjorn Helgaas wrote:
> On Wed, Mar 27, 2024 at 08:49:09PM +0100, Konrad Dybcio wrote:
>> Currently, we've only been minimizing the power draw while keeping the
>> RC up at all times. This is suboptimal, as it draws a whole lot of power
>> and prevents the SoC from power collapsing.
>>
>> Implement full shutdown and re-initialization to allow for powering off
>> the controller.
>>
>> This is mainly intended for SC8280XP with a broken power rail setup,
>> which requires a full RC shutdown/reinit in order to reach SoC-wide
>> power collapse, but sleeping is generally better than not sleeping and
>> less destructive suspend can be implemented later for platforms that
>> support it.
>
> Second try (first at
> https://lore.kernel.org/all/20240212213216.GA1145794@bhelgaas/):
>
> - Capitalize subject lines to match history (sorry, I didn't mention
> the first time)
>
> - Drop or replace "properly" with something specific
>
> - "... minimizing power draw while keeping RC up at all times ...
> draws a whole lot of power" doesn't quite make sense to me
>
> - Reword or explain "power collapse"
>
> - No COMPILE_TEST provision (maybe it turned out to be impractical?)
>
> - Magic delay numbers below with no citation or explanation. Even a
> short comment could be a hint about how to verify and potentially
> change in the future. A #define for readl_poll_timeout() would be
> helpful as a place for a comment and because the name could
> include "_US" to show the units.
>
> - Add "()" after function names in comments
Sorry Bjorn, I came back to this series after some time and didn't revisit
your message. I'll be sure not to forget the next time around.
Konrad
prev parent reply other threads:[~2024-03-27 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 19:49 [PATCH v3 0/2] Qualcomm PCIe RC shutdown & reinit Konrad Dybcio
2024-03-27 19:49 ` [PATCH v3 1/2] PCI: qcom: reshuffle reset logic in 2_7_0 .init Konrad Dybcio
2024-03-27 19:49 ` [PATCH v3 2/2] PCI: qcom: properly implement RC shutdown/power up Konrad Dybcio
2024-03-27 21:20 ` Bjorn Helgaas
2024-03-27 21:27 ` Konrad Dybcio [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=fc72ee13-db3d-423a-9ac2-15b13f42ef5e@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=johan+linaro@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=marijn.suijten@somainline.org \
--cc=p.zabel@pengutronix.de \
--cc=quic_bjorande@quicinc.com \
--cc=robh@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