[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cover.1711048433.git.daniel@makrotopia.org>
Date: Thu, 21 Mar 2024 19:31:48 +0000
From: Daniel Golle <daniel@...rotopia.org>
To: 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>,
Daniel Golle <daniel@...rotopia.org>,
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: [PATCH 0/8] block: implement NVMEM provider
On embedded devices using an eMMC it is common that one or more (hw/sw)
partitions on the eMMC are used to store MAC addresses and Wi-Fi
calibration EEPROM data.
Implement an NVMEM provider backed by a block device as typically the
NVMEM framework is used to have kernel drivers read and use binary data
from EEPROMs, efuses, flash memory (MTD), ...
In order to be able to reference hardware partitions on an eMMC, add code
to bind each hardware partition to a specific firmware subnode.
Overall, this enables uniform handling across practially all flash
storage types used for this purpose (MTD, UBI, and now also MMC).
As part of this series it was necessary to define a device tree schema
for block devices and partitions on them, which (similar to how it now
works also for UBI volumes) can be matched by one or more properties.
---
This series has previously been submitted as RFC on July 19th 2023[1]
and most of the basic idea did not change since. Another round of RFC
was submitted on March 5th 2024[2] which has received overall positive
feedback and only minor corrections have been done since (see
changelog below).
[1]: https://patchwork.kernel.org/project/linux-block/list/?series=767565
[2]: https://patchwork.kernel.org/project/linux-block/list/?series=832705
Changes since RFC:
* Use 'partuuid' instead of reserved 'uuid' keyword to match against
PARTUUID.
* Simplify blk_nvmem_init(void) function.
Daniel Golle (8):
dt-bindings: block: add basic bindings for block devices
block: partitions: populate fwnode
block: add new genhd flag GENHD_FL_NVMEM
block: implement NVMEM provider
dt-bindings: mmc: mmc-card: add block device nodes
mmc: core: set card fwnode_handle
mmc: block: set fwnode of disk devices
mmc: block: set GENHD_FL_NVMEM
.../bindings/block/block-device.yaml | 22 +++
.../devicetree/bindings/block/partition.yaml | 51 ++++++
.../devicetree/bindings/block/partitions.yaml | 20 +++
.../devicetree/bindings/mmc/mmc-card.yaml | 45 +++++
MAINTAINERS | 5 +
block/Kconfig | 9 +
block/Makefile | 1 +
block/blk-nvmem.c | 169 ++++++++++++++++++
block/partitions/core.c | 41 +++++
drivers/mmc/core/block.c | 8 +
drivers/mmc/core/bus.c | 2 +
include/linux/blkdev.h | 2 +
12 files changed, 375 insertions(+)
create mode 100644 Documentation/devicetree/bindings/block/block-device.yaml
create mode 100644 Documentation/devicetree/bindings/block/partition.yaml
create mode 100644 Documentation/devicetree/bindings/block/partitions.yaml
create mode 100644 block/blk-nvmem.c
--
2.44.0
Powered by blists - more mailing lists