From: Christian Marangi <ansuelsmth@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, Jonathan Corbet <corbet@lwn.net>,
Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Christian Marangi <ansuelsmth@gmail.com>,
INAGAKI Hiroshi <musashino.open@gmail.com>,
Daniel Golle <daniel@makrotopia.org>,
Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>, Ming Lei <ming.lei@redhat.com>,
Li Lingfeng <lilingfeng3@huawei.com>,
Christian Heusel <christian@heusel.eu>,
linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
devicetree@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: [RFC PATCH 4/4] dt-bindings: mmc: Document support for partition table in mmc-card
Date: Mon, 23 Sep 2024 12:59:33 +0200 [thread overview]
Message-ID: <20240923105937.4374-5-ansuelsmth@gmail.com> (raw)
In-Reply-To: <20240923105937.4374-1-ansuelsmth@gmail.com>
Document support for defining a partition table in the mmc-card node.
This is needed if the eMMC doesn't have a partition table written and
the bootloader of the device load data by using absolute offset of the
block device. This is common on embedded device that have eMMC installed
to save space and have non removable block devices.
eMMC provide a generic disk for user data and if supported also provide
one or two additional disk (boot0 and boot1) for special usage of boot
operation where normally is stored the bootloader or boot info.
Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
---
.../devicetree/bindings/mmc/mmc-card.yaml | 75 +++++++++++++++++++
1 file changed, 75 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/mmc-card.yaml b/Documentation/devicetree/bindings/mmc/mmc-card.yaml
index fd347126449a..fab9fa5c170a 100644
--- a/Documentation/devicetree/bindings/mmc/mmc-card.yaml
+++ b/Documentation/devicetree/bindings/mmc/mmc-card.yaml
@@ -13,6 +13,10 @@ description: |
This documents describes the devicetree bindings for a mmc-host controller
child node describing a mmc-card / an eMMC.
+ It's possible to define a fixed partition table for an eMMC for the user
+ partition and one of the 2 boot partition (boot0/boot1) if supported by the
+ eMMC.
+
properties:
compatible:
const: mmc-card
@@ -26,6 +30,48 @@ properties:
Use this to indicate that the mmc-card has a broken hpi
implementation, and that hpi should not be used.
+ "#address-cells": true
+
+ "#size-cells": true
+
+patternProperties:
+ "^partitions(-boot[01])?$":
+ type: object
+
+ properties:
+ "#address-cells": true
+
+ "#size-cells": true
+
+ patternProperties:
+ "@[0-9a-f]+$":
+ type: object
+
+ properties:
+ reg:
+ description: partition's offset and size within the flash (in sector
+ block, 512byte)
+ maxItems: 1
+
+
+ label:
+ description: The label / name for this partition.
+
+ read-only:
+ description: This parameter, if present, is a hint that this partition
+ should only be mounted read-only. This is usually used for flash
+ partitions containing early-boot firmware images or data which should
+ not be clobbered.
+ type: boolean
+
+ required:
+ - reg
+ - label
+
+ additionalProperties: false
+
+ additionalProperties: false
+
required:
- compatible
- reg
@@ -42,6 +88,35 @@ examples:
compatible = "mmc-card";
reg = <0>;
broken-hpi;
+
+ #address-cells = <0>;
+ #size-cells = <0>;
+
+ partitions {
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ partition@0 {
+ label = "kernel"; /* Kernel */
+ reg = <0x0 0x10000>; /* 32 MB */
+ };
+
+ partition@3400 {
+ label = "rootfs";
+ reg = <0x3400 0x200000>; /* 1GB */
+ };
+ };
+
+ partitions-boot0 {
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ partition@0 {
+ label = "bl";
+ reg = <0x0 0x10000>; /* 32MB */
+ read-only;
+ };
+ };
};
};
--
2.45.2
next prev parent reply other threads:[~2024-09-23 11:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 10:59 [RFC PATCH 0/4] block: partition table OF support Christian Marangi
2024-09-23 10:59 ` [RFC PATCH 1/4] block: add support for defining read-only partitions Christian Marangi
2024-09-24 6:32 ` Christoph Hellwig
2024-09-23 10:59 ` [RFC PATCH 2/4] docs: block: Document support for read-only partition in cmdline part Christian Marangi
2024-09-23 10:59 ` [RFC PATCH 3/4] block: add support for partition table defined in OF Christian Marangi
2024-09-24 6:34 ` Christoph Hellwig
2024-09-24 10:17 ` Christian Marangi
2024-10-01 8:37 ` Christoph Hellwig
2024-10-01 9:26 ` Christian Marangi
2024-10-02 7:45 ` Christoph Hellwig
2024-10-02 8:22 ` Christian Marangi
2024-09-23 10:59 ` Christian Marangi [this message]
2024-09-24 22:53 ` [RFC PATCH 4/4] dt-bindings: mmc: Document support for partition table in mmc-card Rob Herring
2024-09-24 23:01 ` Christian Marangi
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=20240923105937.4374-5-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=christian@heusel.eu \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@makrotopia.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lilingfeng3@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=ming.lei@redhat.com \
--cc=miquel.raynal@bootlin.com \
--cc=musashino.open@gmail.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).