[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240923105937.4374-1-ansuelsmth@gmail.com>
Date: Mon, 23 Sep 2024 12:59:29 +0200
From: Christian Marangi <ansuelsmth@...il.com>
To: Jens Axboe <axboe@...nel.dk>,
Jonathan Corbet <corbet@....net>,
Ulf Hansson <ulf.hansson@...aro.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Christian Marangi <ansuelsmth@...il.com>,
INAGAKI Hiroshi <musashino.open@...il.com>,
Daniel Golle <daniel@...rotopia.org>,
Christian Brauner <brauner@...nel.org>,
Al Viro <viro@...iv.linux.org.uk>,
Ming Lei <ming.lei@...hat.com>,
Li Lingfeng <lilingfeng3@...wei.com>,
Christian Heusel <christian@...sel.eu>,
linux-block@...r.kernel.org,
linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-mmc@...r.kernel.org,
devicetree@...r.kernel.org,
Miquel Raynal <miquel.raynal@...tlin.com>,
Lorenzo Bianconi <lorenzo@...nel.org>
Subject: [RFC PATCH 0/4] block: partition table OF support
Hi,
this is an initial proposal to complete support for manually defining
partition table.
Some background on this. Many OEM on embedded device (modem, router...)
are starting to migrate from NOR/NAND flash to eMMC. The reason for this
is that OEM are starting to require more and more space for the firmware
and price difference is becoming so little that using eMMC is only benefits
and no cons.
Given these reason, OEM are also using very custom way to provide a
partition table and doesn't relay on common method like writing a table
on the eMMC.
One way that is commonly used is to hardcode the partition table and
pass it to the system via various way (cmdline, special glue driver,
block2mtd...)
This way is also used on Android where the partition table
is passed from the bootloader via cmdline.
One reason to use this method is to save space on the device and to
permit more flexibility on partition handling.
What this series does is complete support for this feature.
It's possible to use the cmdline to define a partition table similar
to how it's done for MTD but this is problematic for a number of device
where tweaking the cmdline is not possible. This series adds OF support
to make it possible to define a partition table in the Device Tree.
We implement a similar schema to the MTD fixed-partition, where we define
a "label" and a "reg" with "offset" and "size".
A new block partition parser is introduced that check if the block device
have an OF node attached and check if a fixed-partition table is defined.
If a correct node is found, then partition table is filled. cmdline will
still have priority to this new parser.
Some block device also implement boot1 and boot2 additional disk. Similar
to the cmdline parser, these disk can have OF support using the
"partitions-boot0" and "partitions-boot1" additional node.
It's also completed support for declaring partition as read-only as this
feature was introduced but never finished in the cmdline parser.
Posting as RFC for any comments or additional checks on OF parser code.
I hope this solution is better accepted as downstream this is becoming
a real problem with a growing number of strange solution for the simple
task of providing a fixed partition table.
Christian Marangi (4):
block: add support for defining read-only partitions
docs: block: Document support for read-only partition in cmdline part
block: add support for partition table defined in OF
dt-bindings: mmc: Document support for partition table in mmc-card
Documentation/block/cmdline-partition.rst | 5 +-
.../devicetree/bindings/mmc/mmc-card.yaml | 75 ++++++++++++++++
block/blk.h | 1 +
block/partitions/Kconfig | 8 ++
block/partitions/Makefile | 1 +
block/partitions/cmdline.c | 3 +
block/partitions/core.c | 3 +
block/partitions/of.c | 85 +++++++++++++++++++
8 files changed, 180 insertions(+), 1 deletion(-)
create mode 100644 block/partitions/of.c
--
2.45.2
Powered by blists - more mailing lists