From: Daniel Golle <daniel@makrotopia.org>
To: Richard Weinberger <richard@nod.at>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: [PATCH 0/6] mtd: ubi: allow UBI volumes to provide NVMEM
Date: Mon, 31 Jul 2023 20:10:47 +0100 [thread overview]
Message-ID: <cover.1690823629.git.daniel@makrotopia.org> (raw)
The series is a follow-up and contains all patches of the previous
series "mtd: ubi: behave like a good MTD citizen"[1] which was meant in
preparation for implementing the NVMEM provider.
The goal is to support embedded Linux devices which got NVMEM bits
stored inside a UBI volume. Representing the UBI volume in the Device
Tree, adding a phandle to be referenced by NVMEM consumers allows such
devices to come up with their correct MAC addresses and device-specific
Wi-Fi calibration data loaded.
In order to be available for other drivers, attaching UBI devices has
to be moved from late_initcall (which is too late for other drivers) to
happen earlier. As an alternative to the existing kernel cmdline
parameter the Device Tree property 'compatible = "linux,ubi";' inside
an MTD partition can be used to have that MTD device attached as UBI
device. MTD partitions which serve as UBI devices may have a "volumes"
firmware subnode with volumes which may be compatible with
"nvmem-cells".
In this way, other drivers (think: Ethernet, Wi-Fi) can resolve and
acquire NVMEM bits using the usual device tree phandle, just this time
the NVMEM content is read from a UBI volume.
[1]: https://patchwork.ozlabs.org/project/linux-mtd/list/?series=353177&state=%2A&archive=both
Daniel Golle (6):
mtd: ubi: block: don't return on error when removing
mtd: ubi: block: use notifier to create ubiblock from parameter
mtd: ubi: attach MTD partition from device-tree
mtd: ubi: introduce pre-removal notification for UBI volumes
mtd: ubi: populate ubi volume fwnode
mtd: ubi: provide NVMEM layer over UBI volumes
drivers/mtd/ubi/Kconfig | 12 +++
drivers/mtd/ubi/Makefile | 1 +
drivers/mtd/ubi/block.c | 186 +++++++++++++++++++++++---------------
drivers/mtd/ubi/build.c | 160 ++++++++++++++++++++++++---------
drivers/mtd/ubi/cdev.c | 4 +-
drivers/mtd/ubi/nvmem.c | 189 +++++++++++++++++++++++++++++++++++++++
drivers/mtd/ubi/ubi.h | 6 +-
drivers/mtd/ubi/vmt.c | 36 ++++++++
include/linux/mtd/ubi.h | 2 +
9 files changed, 477 insertions(+), 119 deletions(-)
create mode 100644 drivers/mtd/ubi/nvmem.c
--
2.41.0
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Golle <daniel@makrotopia.org>
To: Richard Weinberger <richard@nod.at>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: [PATCH 0/6] mtd: ubi: allow UBI volumes to provide NVMEM
Date: Mon, 31 Jul 2023 20:10:47 +0100 [thread overview]
Message-ID: <cover.1690823629.git.daniel@makrotopia.org> (raw)
The series is a follow-up and contains all patches of the previous
series "mtd: ubi: behave like a good MTD citizen"[1] which was meant in
preparation for implementing the NVMEM provider.
The goal is to support embedded Linux devices which got NVMEM bits
stored inside a UBI volume. Representing the UBI volume in the Device
Tree, adding a phandle to be referenced by NVMEM consumers allows such
devices to come up with their correct MAC addresses and device-specific
Wi-Fi calibration data loaded.
In order to be available for other drivers, attaching UBI devices has
to be moved from late_initcall (which is too late for other drivers) to
happen earlier. As an alternative to the existing kernel cmdline
parameter the Device Tree property 'compatible = "linux,ubi";' inside
an MTD partition can be used to have that MTD device attached as UBI
device. MTD partitions which serve as UBI devices may have a "volumes"
firmware subnode with volumes which may be compatible with
"nvmem-cells".
In this way, other drivers (think: Ethernet, Wi-Fi) can resolve and
acquire NVMEM bits using the usual device tree phandle, just this time
the NVMEM content is read from a UBI volume.
[1]: https://patchwork.ozlabs.org/project/linux-mtd/list/?series=353177&state=%2A&archive=both
Daniel Golle (6):
mtd: ubi: block: don't return on error when removing
mtd: ubi: block: use notifier to create ubiblock from parameter
mtd: ubi: attach MTD partition from device-tree
mtd: ubi: introduce pre-removal notification for UBI volumes
mtd: ubi: populate ubi volume fwnode
mtd: ubi: provide NVMEM layer over UBI volumes
drivers/mtd/ubi/Kconfig | 12 +++
drivers/mtd/ubi/Makefile | 1 +
drivers/mtd/ubi/block.c | 186 +++++++++++++++++++++++---------------
drivers/mtd/ubi/build.c | 160 ++++++++++++++++++++++++---------
drivers/mtd/ubi/cdev.c | 4 +-
drivers/mtd/ubi/nvmem.c | 189 +++++++++++++++++++++++++++++++++++++++
drivers/mtd/ubi/ubi.h | 6 +-
drivers/mtd/ubi/vmt.c | 36 ++++++++
include/linux/mtd/ubi.h | 2 +
9 files changed, 477 insertions(+), 119 deletions(-)
create mode 100644 drivers/mtd/ubi/nvmem.c
--
2.41.0
next reply other threads:[~2023-07-31 19:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 19:10 Daniel Golle [this message]
2023-07-31 19:10 ` [PATCH 0/6] mtd: ubi: allow UBI volumes to provide NVMEM Daniel Golle
2023-07-31 19:11 ` [PATCH 1/6] mtd: ubi: block: don't return on error when removing Daniel Golle
2023-07-31 19:11 ` Daniel Golle
2023-07-31 19:11 ` [PATCH 2/6] mtd: ubi: block: use notifier to create ubiblock from parameter Daniel Golle
2023-07-31 19:11 ` Daniel Golle
2023-07-31 19:12 ` [PATCH 3/6] mtd: ubi: attach MTD partition from device-tree Daniel Golle
2023-07-31 19:12 ` Daniel Golle
2023-07-31 19:13 ` [PATCH 4/6] mtd: ubi: introduce pre-removal notification for UBI volumes Daniel Golle
2023-07-31 19:13 ` Daniel Golle
2023-07-31 19:13 ` [PATCH 5/6] mtd: ubi: populate ubi volume fwnode Daniel Golle
2023-07-31 19:13 ` Daniel Golle
2023-07-31 19:14 ` [PATCH 6/6] mtd: ubi: provide NVMEM layer over UBI volumes Daniel Golle
2023-07-31 19:14 ` Daniel Golle
2023-07-31 21:54 ` Randy Dunlap
2023-07-31 21:54 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1690823629.git.daniel@makrotopia.org \
--to=daniel@makrotopia.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.