From: Samuel Holland <samuel.holland@sifive.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-clk@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: sifive: prci: fix module autoloading
Date: Wed, 10 Apr 2024 11:03:11 -0500 [thread overview]
Message-ID: <23c88f5b-177d-4698-afa8-211a2bf07597@sifive.com> (raw)
In-Reply-To: <20240410155342.224061-1-krzk@kernel.org>
On 2024-04-10 10:53 AM, Krzysztof Kozlowski wrote:
> Add MODULE_DEVICE_TABLE(), so modules could be properly autoloaded
> based on the alias from of_device_id table. Clocks are considered core
> components, so usually they are built-in, however these can be built and
> used as modules on some generic kernel.
>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> drivers/clk/sifive/sifive-prci.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/clk/sifive/sifive-prci.c b/drivers/clk/sifive/sifive-prci.c
> index 25b8e1a80ddc..700a1be9ec47 100644
> --- a/drivers/clk/sifive/sifive-prci.c
> +++ b/drivers/clk/sifive/sifive-prci.c
> @@ -611,6 +611,7 @@ static const struct of_device_id sifive_prci_of_match[] = {
> {.compatible = "sifive,fu740-c000-prci", .data = &prci_clk_fu740},
> {}
> };
> +MODULE_DEVICE_TABLE(of, sifive_prci_of_match);
>
> static struct platform_driver sifive_prci_driver = {
> .driver = {
Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
prev parent reply other threads:[~2024-04-10 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 15:53 [PATCH] clk: sifive: prci: fix module autoloading Krzysztof Kozlowski
2024-04-10 16:03 ` Samuel Holland [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=23c88f5b-177d-4698-afa8-211a2bf07597@sifive.com \
--to=samuel.holland@sifive.com \
--cc=krzk@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=paul.walmsley@sifive.com \
--cc=sboyd@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