From: Matthias Brugger <mbrugger@suse.com>
To: Pengpeng Hou <pengpeng@iscas.ac.cn>,
Chester Lin <chester62515@gmail.com>,
Ghennadi Procopciuc <ghennadi.procopciuc@oss.nxp.com>,
NXP S32 Linux Team <s32@nxp.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-arm-kernel@lists.infradead.org, linux-rtc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: s32g: add missing MODULE_DEVICE_TABLE()
Date: Mon, 6 Jul 2026 11:43:29 +0200 [thread overview]
Message-ID: <67fa35d6-548f-4d52-8164-d31433fd1b1c@suse.com> (raw)
In-Reply-To: <20260704122003.70108-1-pengpeng@iscas.ac.cn>
On 04/07/2026 14:20, Pengpeng Hou wrote:
> The driver has an OF match table wired to .of_match_table, but does
> not export the table with MODULE_DEVICE_TABLE().
>
> Add the missing MODULE_DEVICE_TABLE(of, ...) entry so module alias
> information is generated for OF based module autoloading.
>
> This is a source-level fix. It does not claim dynamic hardware
> reproduction; the evidence is the driver-owned match table, its use by
> the platform driver, and the missing module alias publication.
>
> Signed-off-by: Pengpeng Hou <pengpeng@iscas.ac.cn>
Reviewed-by: Matthias Brugger <mbrugger@suse.com>
> ---
> drivers/rtc/rtc-s32g.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/rtc/rtc-s32g.c b/drivers/rtc/rtc-s32g.c
> index 3a0818e972eb..86716192d10f 100644
> --- a/drivers/rtc/rtc-s32g.c
> +++ b/drivers/rtc/rtc-s32g.c
> @@ -366,6 +366,7 @@ static const struct of_device_id rtc_dt_ids[] = {
> { .compatible = "nxp,s32g2-rtc", .data = &rtc_s32g2_data },
> { /* sentinel */ },
> };
> +MODULE_DEVICE_TABLE(of, rtc_dt_ids);
>
> static DEFINE_SIMPLE_DEV_PM_OPS(s32g_rtc_pm_ops,
> s32g_rtc_suspend, s32g_rtc_resume);
>
prev parent reply other threads:[~2026-07-06 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 12:20 [PATCH] rtc: s32g: add missing MODULE_DEVICE_TABLE() Pengpeng Hou
2026-07-04 12:22 ` sashiko-bot
2026-07-06 9:43 ` Matthias Brugger [this message]
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=67fa35d6-548f-4d52-8164-d31433fd1b1c@suse.com \
--to=mbrugger@suse.com \
--cc=alexandre.belloni@bootlin.com \
--cc=chester62515@gmail.com \
--cc=ghennadi.procopciuc@oss.nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=pengpeng@iscas.ac.cn \
--cc=s32@nxp.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