[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e170642d-9ae8-4d5a-90d9-2837f1bcef9b@acm.org>
Date: Thu, 21 Mar 2024 12:44:19 -0700
From: Bart Van Assche <bvanassche@....org>
To: Daniel Golle <daniel@...rotopia.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>, Ulf Hansson <ulf.hansson@...aro.org>,
Jens Axboe <axboe@...nel.dk>, Dave Chinner <dchinner@...hat.com>,
Jan Kara <jack@...e.cz>, Thomas Weißschuh
<linux@...ssschuh.net>, Damien Le Moal <dlemoal@...nel.org>,
Li Lingfeng <lilingfeng3@...wei.com>, Christian Brauner
<brauner@...nel.org>, Christian Heusel <christian@...sel.eu>,
Min Li <min15.li@...sung.com>, Adrian Hunter <adrian.hunter@...el.com>,
Avri Altman <avri.altman@....com>, Hannes Reinecke <hare@...e.de>,
Christian Loehle <CLoehle@...erstone.com>, Bean Huo <beanhuo@...ron.com>,
Yeqi Fu <asuk4.q@...il.com>, Victor Shih <victor.shih@...esyslogic.com.tw>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
Dominique Martinet <dominique.martinet@...ark-techno.com>,
"Ricardo B. Marliere" <ricardo@...liere.net>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org,
linux-block@...r.kernel.org
Subject: Re: [PATCH 4/8] block: implement NVMEM provider
On 3/21/24 12:34, Daniel Golle wrote:
> On embedded devices using an eMMC it is common that one or more partitions
> on the eMMC are used to store MAC addresses and Wi-Fi calibration EEPROM
> data. Allow referencing the partition in device tree for the kernel and
> Wi-Fi drivers accessing it via the NVMEM layer.
Why to store calibration data in a partition instead of in a file on a
filesystem?
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8c88f362feb55..242a0a139c00a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3662,6 +3662,11 @@ L: linux-mtd@...ts.infradead.org
> S: Maintained
> F: drivers/mtd/devices/block2mtd.c
>
> +BLOCK NVMEM DRIVER
> +M: Daniel Golle <daniel@...rotopia.org>
> +S: Maintained
> +F: block/blk-nvmem.c
Why to add this functionality to the block layer instead of somewhere
in the drivers/ directory?
Thanks,
Bart.
Powered by blists - more mailing lists