From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: "Sushrut Shree Trivedi" <sushrut.trivedi@oss.qualcomm.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"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>,
cros-qcom-dts-watchers@chromium.org,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] PCI: dwc: Program device-id
Date: Fri, 28 Nov 2025 12:05:49 +0100 [thread overview]
Message-ID: <b85c25f1-65b3-4277-82b1-402daef6fe8d@oss.qualcomm.com> (raw)
In-Reply-To: <20251127-program-device-id-v1-0-31ad36beda2c@quicinc.com>
On 11/27/25 4:30 PM, Sushrut Shree Trivedi wrote:
> For some controllers, HW doesn't program the correct device-id
> leading to incorrect identification in lspci. For ex, QCOM
> controller SC7280 uses same device id as SM8250. This would
> cause issues while applying controller specific quirks.
Is this the only instance where this happened?
Konrad
next prev parent reply other threads:[~2025-11-28 11:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 15:30 [PATCH 0/2] PCI: dwc: Program device-id Sushrut Shree Trivedi
2025-11-27 15:30 ` [PATCH 1/2] " Sushrut Shree Trivedi
2025-11-28 1:03 ` Shawn Lin
2025-11-29 7:34 ` Manivannan Sadhasivam
2025-11-30 2:43 ` Shawn Lin
2025-11-30 15:05 ` Manivannan Sadhasivam
2025-11-29 7:28 ` Manivannan Sadhasivam
2025-11-27 15:30 ` [PATCH 2/2] arm64: dts: qcom: sc7280: Add PCIe device-id Sushrut Shree Trivedi
2025-11-28 11:05 ` Konrad Dybcio [this message]
2025-12-01 12:26 ` [PATCH 0/2] PCI: dwc: Program device-id Rob Herring
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=b85c25f1-65b3-4277-82b1-402daef6fe8d@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=jingoohan1@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--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=robh@kernel.org \
--cc=sushrut.trivedi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox