From: Yicong Yang <yangyicong@huawei.com>
To: <will@kernel.org>, <mark.rutland@arm.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <jonathan.cameron@huawei.com>, <linuxarm@huawei.com>,
<yangyicong@hisilicon.com>
Subject: [PATCH] perf/smmuv3: Add platform id table for module auto loading
Date: Mon, 7 Aug 2023 20:22:33 +0800 [thread overview]
Message-ID: <20230807122233.28563-1-yangyicong@huawei.com> (raw)
From: Yicong Yang <yangyicong@hisilicon.com>
On ACPI based system the device is probed by the name directly. If the
driver is configured as module it can only be loaded manually. Add the
platform id table as well as the module alias then the driver will be
loaded automatically by the udev or others once the device added.
Signed-off-by: Yicong Yang <yangyicong@hisilicon.com>
---
drivers/perf/arm_smmuv3_pmu.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/perf/arm_smmuv3_pmu.c b/drivers/perf/arm_smmuv3_pmu.c
index 25a269d431e4..f27c5f585524 100644
--- a/drivers/perf/arm_smmuv3_pmu.c
+++ b/drivers/perf/arm_smmuv3_pmu.c
@@ -946,7 +946,14 @@ static const struct of_device_id smmu_pmu_of_match[] = {
MODULE_DEVICE_TABLE(of, smmu_pmu_of_match);
#endif
+static const struct platform_device_id smmu_pmu_platform_match[] = {
+ { "arm-smmu-v3-pmcg", 0 },
+ {}
+};
+MODULE_DEVICE_TABLE(platform, smmu_pmu_platform_match);
+
static struct platform_driver smmu_pmu_driver = {
+ .id_table = smmu_pmu_platform_match,
.driver = {
.name = "arm-smmu-v3-pmcg",
.of_match_table = of_match_ptr(smmu_pmu_of_match),
--
2.24.0
next reply other threads:[~2023-08-07 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 12:22 Yicong Yang [this message]
2023-08-09 2:45 ` Liang Li
2023-08-09 5:47 ` Barry Song
2023-08-09 6:31 ` Yicong Yang
2023-08-09 12:11 ` Liang Li
2023-08-11 10:14 ` Yicong Yang
2023-08-12 5:24 ` Barry Song
2023-08-12 5:31 ` Barry Song
2023-08-14 8:51 ` Yicong Yang
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=20230807122233.28563-1-yangyicong@huawei.com \
--to=yangyicong@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.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
all inboxes | Powered by JetHome®