From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Tingwei Zhang <quic_tingweiz@quicinc.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
<linux-kernel@vger.kernel.org>,
Trilok Soni <quic_tsoni@quicinc.com>,
Jinlong Mao <quic_jinlmao@quicinc.com>
Subject: Re: How to pass software configuration to driver built as module in boot up phase
Date: Tue, 31 Oct 2023 08:35:00 +0900 [thread overview]
Message-ID: <20231031083500.343b39efded46acf1d349628@kernel.org> (raw)
In-Reply-To: <1c001c6f-9902-4803-9406-39e3325422bf@quicinc.com>
On Mon, 30 Oct 2023 19:21:48 +0800
Tingwei Zhang <quic_tingweiz@quicinc.com> wrote:
> Hi Masami, Greg and Rafael,
>
> I have one driver that needs a bunch to software configuration like 1000
> settings. These settings can be different according to the use case.
Is it an out-of-tree driver which can not be embedded?
>
> They are required in boot up phase so we can't reply on user space to
> make the configuration.
>
> Boot config is not preferred since we'd like to build that driver as
> dynamic load Kernel module.
>
> Could you let me know if there's any mechanism in Kernel to do that?
Hm, it is interesting situation. So I made the bootconfig API and data
released after boot (only keep it in /proc/bootconfig). So I thought
module loader script can parse it and pass params to the modules.
But I did not expected that the number of params is about 1000.
Thank you,
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-10-30 23:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 11:21 How to pass software configuration to driver built as module in boot up phase Tingwei Zhang
2023-10-30 11:30 ` Greg Kroah-Hartman
2023-10-31 2:56 ` Tingwei Zhang
2023-10-31 6:58 ` Greg Kroah-Hartman
2023-10-31 10:01 ` Tingwei Zhang
2023-10-31 10:44 ` Greg Kroah-Hartman
2023-10-30 23:35 ` Masami Hiramatsu [this message]
2023-10-31 3:00 ` Tingwei Zhang
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=20231031083500.343b39efded46acf1d349628@kernel.org \
--to=mhiramat@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jinlmao@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=rafael@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