[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f85f117a59586dc2e5df33e11b39c69f@walle.cc>
Date: Mon, 17 Jul 2023 14:24:45 +0200
From: Michael Walle <michael@...le.cc>
To: Miquel Raynal <miquel.raynal@...tlin.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Robert Marko <robert.marko@...tura.hr>,
Luka Perkov <luka.perkov@...tura.hr>,
Randy Dunlap <rdunlap@...radead.org>,
Miquel Raynal <miquel.raynal@...tlin.com>
Subject: Re: [PATCH v6 3/3] nvmem: core: Expose cells through sysfs
Hi,
> There is one limitation though: if a layout is built as a module but is
> not properly installed in the system and loaded manually with insmod
> while the nvmem device driver was built-in, the cells won't appear in
> sysfs. But if done like that, the cells won't be usable by the built-in
> kernel drivers anyway.
What is the difference between manual loading with insmod and automatic
module loading? Or is the limitation, layout as M and device driver as Y
doesn't work?
-michael
Powered by blists - more mailing lists