From: Niklas Cassel <cassel@kernel.org>
To: manivannan.sadhasivam@oss.qualcomm.com
Cc: "Manivannan Sadhasivam" <mani@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, "Chen-Yu Tsai" <wens@kernel.org>,
"Brian Norris" <briannorris@chromium.org>,
"Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>,
"Alex Elder" <elder@riscstar.com>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v3 6/7] PCI: qcom: Drop the assert_perst() callbacks
Date: Tue, 30 Dec 2025 13:31:44 +0100 [thread overview]
Message-ID: <aVPGMJkleqTJezpX@ryzen> (raw)
In-Reply-To: <20251229-pci-pwrctrl-rework-v3-6-c7d5918cd0db@oss.qualcomm.com>
On Mon, Dec 29, 2025 at 10:56:57PM +0530, Manivannan Sadhasivam via B4 Relay wrote:
> From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
>
> Now that the TC9563 Pwrctrl driver is converted to use the new Pwrctrl
> design, there is no need for these assert_perst() callbacks. With the new
> design, TC9563 will be powered on before PERST# deassert. So explicit
> PERST# handling from the TC9563 driver is not needed.
The commit message is a little bit confusing IMO.
The explicit PERST# handling in the TC9563 driver was removed in the
previous commit, so perhaps it is better to not mention TC9563 driver
explicitly (all pwrctrl drivers need to stop using the assert_perst(),
that TC9563 was the only pwrctrl driver user of this API is a detail).
Perhaps phrase the commit message something like:
""
Previously, the controller drivers probed first, toggled PERST#, and
enabled link training and scanned the bus. By the time the pwrctrl driver
probe got called, link training was already enabled by the controller driver.
The pwrctrl drivers thus had to call the .assert_perst() callback, to assert
PERST#, power on the needed resources, and then call the .assert_perst()
callback to deassert PERST#.
Now when all pwrctrl drivers have been converted to new pwrctrl design,
there is no need for the .assert_perst() callback in the controller drivers,
because with the new design, the actual work by the pwrctrl driver will have
been done before the controller driver enumerates the bus. There is thus no
longer any need for .assert_perst() callbacks in the controller drivers.
""
Perhaps also split this commit in two.
Because with the "PCI: qcom:" prefix it is not clear that you are also
removing the callbacks from pci.h
So perhaps create a second patch with only "PCI: " prefix:
""
Now when all .assert_callback() implementations have been removed from
the controller drivers, drop the .assert_callback callback from pci.h.
""
Kind regards,
Niklas
next prev parent reply other threads:[~2025-12-30 12:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 17:26 [PATCH v3 0/7] PCI/pwrctrl: Major rework to integrate pwrctrl devices with controller drivers Manivannan Sadhasivam via B4 Relay
2025-12-29 17:26 ` [PATCH v3 1/7] PCI/pwrctrl: tc9563: Use put_device() instead of i2c_put_adapter() Manivannan Sadhasivam via B4 Relay
2026-01-02 13:42 ` Bartosz Golaszewski
2025-12-29 17:26 ` [PATCH v3 2/7] PCI/pwrctrl: Add 'struct pci_pwrctrl::power_{on/off}' callbacks Manivannan Sadhasivam via B4 Relay
2026-01-02 13:58 ` Bartosz Golaszewski
2025-12-29 17:26 ` [PATCH v3 3/7] PCI/pwrctrl: Add APIs for explicitly creating and destroying pwrctrl devices Manivannan Sadhasivam via B4 Relay
2026-01-02 13:46 ` Bartosz Golaszewski
2025-12-29 17:26 ` [PATCH v3 4/7] PCI/pwrctrl: Add APIs to power on/off the " Manivannan Sadhasivam via B4 Relay
2025-12-29 17:26 ` [PATCH v3 5/7] PCI/pwrctrl: Switch to the new pwrctrl APIs Manivannan Sadhasivam via B4 Relay
2026-01-02 13:56 ` Bartosz Golaszewski
2025-12-29 17:26 ` [PATCH v3 6/7] PCI: qcom: Drop the assert_perst() callbacks Manivannan Sadhasivam via B4 Relay
2025-12-30 12:31 ` Niklas Cassel [this message]
2025-12-30 12:42 ` Niklas Cassel
2025-12-29 17:26 ` [PATCH v3 7/7] PCI: qcom: Rename PERST# assert/deassert helpers for uniformity Manivannan Sadhasivam via B4 Relay
2026-01-02 13:58 ` Bartosz Golaszewski
2025-12-30 10:35 ` [PATCH v3 0/7] PCI/pwrctrl: Major rework to integrate pwrctrl devices with controller drivers Niklas Cassel
2025-12-30 10:52 ` Manivannan Sadhasivam
2025-12-30 11:31 ` Niklas Cassel
2025-12-30 12:33 ` Manivannan Sadhasivam
2025-12-30 12:35 ` Niklas Cassel
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=aVPGMJkleqTJezpX@ryzen \
--to=cassel@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=bhelgaas@google.com \
--cc=brgl@bgdev.pl \
--cc=briannorris@chromium.org \
--cc=elder@riscstar.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=kwilczynski@kernel.org \
--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=manivannan.sadhasivam@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=wens@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