Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.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 16:20:50 -0500	[thread overview]
Message-ID: <20240327212050.GA1538555@bhelgaas> (raw)
In-Reply-To: <20240210-topic-8280_pcie-v3-2-ee7af6f892a0@linaro.org>

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

Bjorn

  reply	other threads:[~2024-03-27 21:20 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 [this message]
2024-03-27 21:27     ` Konrad Dybcio

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=20240327212050.GA1538555@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=johan+linaro@kernel.org \
    --cc=konrad.dybcio@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=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