From: Krzysztof Kozlowski <krzk@kernel.org>
To: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 3/3] power: sequencing: pwrseq-pcie-m2: Add QCC2072 BT PCI device ID
Date: Thu, 23 Jul 2026 21:22:03 +0200 [thread overview]
Message-ID: <9cc5af16-d95e-4f10-8b4a-5e29c136079c@kernel.org> (raw)
In-Reply-To: <20260703-eliza_evk-v1-3-7624440bd76d@oss.qualcomm.com>
On 03/07/2026 14:38, Krishna Chaitanya Chundru wrote:
> Add the Qualcomm QCC2072 Bluetooth device (PCI ID 0x1112) to the
> pwrseq_m2_pci_ids table so the M.2 power sequencer can create the
> serdev node for its BT interface on enumeration.
>
> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> ---
> drivers/power/sequencing/pwrseq-pcie-m2.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/power/sequencing/pwrseq-pcie-m2.c b/drivers/power/sequencing/pwrseq-pcie-m2.c
> index b5ed80d03953..4aac52062fae 100644
> --- a/drivers/power/sequencing/pwrseq-pcie-m2.c
> +++ b/drivers/power/sequencing/pwrseq-pcie-m2.c
> @@ -190,6 +190,8 @@ static const struct pci_device_id pwrseq_m2_pci_ids[] = {
> .driver_data = (kernel_ulong_t)"qcom,wcn6855-bt" },
> { PCI_DEVICE(PCI_VENDOR_ID_QCOM, 0x1107),
> .driver_data = (kernel_ulong_t)"qcom,wcn7850-bt" },
> + { PCI_DEVICE(PCI_VENDOR_ID_QCOM, 0x1112),
> + .driver_data = (kernel_ulong_t)"qcom,qcc2072-bt" },
Bartosz,
Please push back on this. This is undocumented (indirect) compatible.
This cannot get accepted to kernel in such form.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-07-23 19:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 12:38 [PATCH 0/3] arm64: dts: qcom: eliza-evk: Enable PCIe0 and PCIe1 with M.2 and TC9563 switch Krishna Chaitanya Chundru
2026-07-03 12:38 ` [PATCH 1/3] arm64: dts: qcom: eliza-evk: Add PCIe0 with M.2 E key connector Krishna Chaitanya Chundru
2026-07-03 15:07 ` Konrad Dybcio
2026-07-03 12:38 ` [PATCH 2/3] arm64: dts: qcom: eliza-evk: Add PCIe1 with TC9563 PCIe switch Krishna Chaitanya Chundru
2026-07-03 15:09 ` Konrad Dybcio
2026-07-06 5:22 ` Krishna Chaitanya Chundru
2026-07-06 8:28 ` Konrad Dybcio
2026-07-06 10:33 ` Manivannan Sadhasivam
2026-07-04 4:07 ` Xilin Wu
2026-07-06 5:24 ` Krishna Chaitanya Chundru
2026-07-06 6:43 ` Xilin Wu
2026-07-03 12:38 ` [PATCH 3/3] power: sequencing: pwrseq-pcie-m2: Add QCC2072 BT PCI device ID Krishna Chaitanya Chundru
2026-07-23 19:22 ` Krzysztof Kozlowski [this message]
2026-07-24 7:38 ` Bartosz Golaszewski
2026-07-06 10:27 ` (subset) [PATCH 0/3] arm64: dts: qcom: eliza-evk: Enable PCIe0 and PCIe1 with M.2 and TC9563 switch Bartosz Golaszewski
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=9cc5af16-d95e-4f10-8b4a-5e29c136079c@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mani@kernel.org \
--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
all inboxes | Powered by JetHome®