Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.36 as permitted sender) client-ip=23.128.96.36;
Date:   Tue, 31 Oct 2023 08:35:00 +0900
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
Message-Id: <20231031083500.343b39efded46acf1d349628@kernel.org>
In-Reply-To: <1c001c6f-9902-4803-9406-39e3325422bf@quicinc.com>
References: <1c001c6f-9902-4803-9406-39e3325422bf@quicinc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

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>