From: Niklas Cassel <cassel@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Shawn Lin" <shawn.lin@rock-chips.com>,
"Niklas Cassel" <cassel@kernel.org>,
linux-pci@vger.kernel.org
Subject: [PATCH] PCI: dwc: Add rockchip to the RAS DES allowed vendor list
Date: Tue, 25 Feb 2025 15:56:58 +0100 [thread overview]
Message-ID: <20250225145657.944925-2-cassel@kernel.org> (raw)
Add PCI_VENDOR_ID_ROCKCHIP to the list of RAS DES vendor specific ids.
Tested using the RAS DES DWC debugfs changes that was merged recently.
drivers/perf/dwc_pcie_pmu.c driver has not been tested, but considering
RAS DES works in DWC debugfs, I see no reason why RAS DES shouldn't work
in drivers/perf/dwc_pcie_pmu.c.
Signed-off-by: Niklas Cassel <cassel@kernel.org>
---
Note: this depends on DWC debugfs patches that are queued up in branch
controller/dwc and the PCI_VENDOR_ID_ROCKCHIP patch on branch
controller/rockchip.
include/linux/pcie-dwc.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/pcie-dwc.h b/include/linux/pcie-dwc.h
index 6436e7fadc75..15d27a509769 100644
--- a/include/linux/pcie-dwc.h
+++ b/include/linux/pcie-dwc.h
@@ -28,6 +28,8 @@ static const struct dwc_pcie_vsec_id dwc_pcie_rasdes_vsec_ids[] = {
.vsec_id = 0x02, .vsec_rev = 0x4 },
{ .vendor_id = PCI_VENDOR_ID_QCOM,
.vsec_id = 0x02, .vsec_rev = 0x4 },
+ { .vendor_id = PCI_VENDOR_ID_ROCKCHIP,
+ .vsec_id = 0x02, .vsec_rev = 0x4 },
{ .vendor_id = PCI_VENDOR_ID_SAMSUNG,
.vsec_id = 0x02, .vsec_rev = 0x4 },
{} /* terminator */
--
2.48.1
next reply other threads:[~2025-02-25 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 14:56 Niklas Cassel [this message]
2025-02-26 14:36 ` [PATCH] PCI: dwc: Add rockchip to the RAS DES allowed vendor list Krzysztof Wilczyński
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=20250225145657.944925-2-cassel@kernel.org \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=shawn.lin@rock-chips.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