From: Edward Chow <equu@openmail.cc>
To: Rob Herring <robh+dt@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lech Perczak <lech.perczak@camlingroup.com>,
Edward Chow <equu@openmail.cc>
Subject: [PATCH v2 0/2] dt-bindings: mtd: partitions: Export special values
Date: Fri, 27 Oct 2023 17:46:08 +0800 [thread overview]
Message-ID: <20231027094610.1022114-1-equu@openmail.cc> (raw)
In-Reply-To: <20231025052937.830813-1-equu@openmail.cc>
There are special "offset" and "size" values defined and documented in
linux/mtd/partitions.h:
/* consume as much as possible, leaving size after the end of partition. */
#define MTDPART_OFS_RETAIN (uint64_t)(-3)
/* the partition will start at the next erase block. */
#define MTDPART_OFS_NXTBLK (uint64_t)(-2)
/* the partition will start where the previous one ended. */
#define MTDPART_OFS_APPEND (uint64_t)(-1)
(Though not explicitly, they are compared against variables in uint64_t
in drivers/mtd/mtdpart.c, so they had better be considered as such.)
/* the partition will extend to the end of the master MTD device. */
#define MTDPART_SIZ_FULL (0)
These special values could be used to define partitions automatically
fitting to the size of the master MTD device at runtime.
However, these values used not to be exported to dt-bindings, thus
seldom used before, since they might have been only used in numeric form,
such as "(-1) (-3)" for MTDPART_OFS_RETAIN.
Now, they are exported in dt-bindings/mtd/partitions.h as 32-bit cell
values, so 2-cell addressed should be defined to use special offset values,
such as "MTDPART_OFS_SPECIAL MTDPART_OFS_RETAIN" for MTDPART_OFS_RETAIN in
linux/mtd/partitions.h. An example is added to fixed-partitions.yaml.
Edward Chow (2):
dt-bindings: mtd: partitions: Export special values
dt-bindings: mtd: partitions: Document special values
.../mtd/partitions/fixed-partitions.yaml | 30 +++++++++++++++++++
MAINTAINERS | 2 ++
include/dt-bindings/mtd/partitions.h | 15 ++++++++++
3 files changed, 47 insertions(+)
create mode 100644 include/dt-bindings/mtd/partitions.h
--
2.42.0
next prev parent reply other threads:[~2023-10-27 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 5:29 [PATCH] dt-bindings: mtd-partitions: Export special values Edward Chow
2023-10-25 7:41 ` Miquel Raynal
2023-10-25 8:20 ` Krzysztof Kozlowski
2023-10-25 12:33 ` Rob Herring
2023-10-27 9:46 ` Edward Chow [this message]
2023-10-27 9:46 ` [PATCH v2 1/2] dt-bindings: mtd: partitions: " Edward Chow
2023-10-27 9:46 ` [PATCH v2 2/2] dt-bindings: mtd: partitions: Document " Edward Chow
2023-10-27 11:06 ` Krzysztof Kozlowski
2023-10-27 12:16 ` Rob Herring
2023-10-27 11:06 ` [PATCH v2 0/2] dt-bindings: mtd: partitions: Export " Krzysztof Kozlowski
2023-10-27 11:07 ` Krzysztof Kozlowski
2023-10-27 12:11 ` Miquel Raynal
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=20231027094610.1022114-1-equu@openmail.cc \
--to=equu@openmail.cc \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lech.perczak@camlingroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--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 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).