From: Manivannan Sadhasivam <mani@kernel.org>
To: Zhangfei Gao <zhangfei.gao@oss.qualcomm.com>
Cc: linux-pci@vger.kernel.org, lpieralisi@kernel.org,
kwilczynski@kernel.org, robh@kernel.org, bhelgaas@google.com,
krishna.chundru@oss.qualcomm.com,
bartosz.golaszewski@oss.qualcomm.com,
deepti.jaggi@oss.qualcomm.com, yadu.mg@oss.qualcomm.com,
shengchao.guo@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: qcom: Power on pwrctrl devices for firmware-managed hosts
Date: Thu, 5 Nov 2026 20:07:18 +0530 [thread overview]
Message-ID: <auyUXp1Fgk2yC7fZ@debian> (raw)
In-Reply-To: <20261105101521.434361-1-zhangfei.gao@oss.qualcomm.com>
On Thu, Nov 05, 2026 at 06:15:21PM +0800, Zhangfei Gao wrote:
> commit b921aa3f8dec ("PCI/pwrctrl: Switch to pwrctrl create, power
> on/off, destroy APIs") switched PCI pwrctrl users to explicit create and
> power control APIs, but only added the calls to the regular DesignWare
> host initialization path.
>
> Firmware-managed hosts bypass that path and probe the ECAM host bridge
> directly. Endpoints already powered by firmware, such as NVMe devices,
> remain discoverable. Endpoints that rely on Linux pwrctrl and pwrseq,
> such as WCN7850, remain powered off and cannot be discovered.
>
NACK. For FW initialized platforms, FW should power on the Endpoints before
booting Linux.
- Mani
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2026-11-05 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 10:15 [PATCH] PCI: qcom: Power on pwrctrl devices for firmware-managed hosts Zhangfei Gao
2026-11-05 10:21 ` sashiko-bot
2026-11-05 12:34 ` Bartosz Golaszewski
2026-11-05 14:37 ` Manivannan Sadhasivam [this message]
2026-11-05 14:43 ` Bartosz Golaszewski
2026-11-06 2:24 ` Zhangfei Gao
2026-11-07 16:40 ` Manivannan Sadhasivam
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=auyUXp1Fgk2yC7fZ@debian \
--to=mani@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=bhelgaas@google.com \
--cc=deepti.jaggi@oss.qualcomm.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=robh@kernel.org \
--cc=shengchao.guo@oss.qualcomm.com \
--cc=yadu.mg@oss.qualcomm.com \
--cc=zhangfei.gao@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.