diff options
| author | Daniel Golle <daniel@makrotopia.org> | 2023-12-19 05:33:48 +0300 |
|---|---|---|
| committer | Richard Weinberger <richard@nod.at> | 2024-02-26 00:42:23 +0300 |
| commit | 3ce485803da1b79b2692b6d0c2792829292ad838 (patch) | |
| tree | 6892ea7d9480d76040e81983f1a2808635f6037b /MAINTAINERS | |
| parent | 51932f9fc4871619e93abf4de6f1282ec23d936c (diff) | |
| download | linux-3ce485803da1b79b2692b6d0c2792829292ad838.tar.xz | |
mtd: ubi: provide NVMEM layer over UBI volumes
In an ideal world we would like UBI to be used where ever possible on a
NAND chip. And with UBI support in ARM Trusted Firmware and U-Boot it
is possible to achieve an (almost-)all-UBI flash layout. Hence the need
for a way to also use UBI volumes to store board-level constants, such
as MAC addresses and calibration data of wireless interfaces.
Add UBI volume NVMEM driver module exposing UBI volumes as NVMEM
providers. Allow UBI devices to have a "volumes" firmware subnode with
volumes which may be compatible with "nvmem-cells".
Access to UBI volumes via the NVMEM interface at this point is
read-only, and it is slow, opening and closing the UBI volume for each
access due to limitations of the NVMEM provider API.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Signed-off-by: Richard Weinberger <richard@nod.at>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions