From: Jonas Gorski <jonas.gorski@gmail.com>
To: devicetree@vger.kernel.org, linux-mtd@lists.infradead.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Richard Weinberger <richard@nod.at>,
Marek Vasut <marek.vasut@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: [PATCH V2 0/5] mtd: bcm63xxpart: add device tree support
Date: Thu, 28 Mar 2019 15:19:05 +0100 [thread overview]
Message-ID: <20190328141910.5723-1-jonas.gorski@gmail.com> (raw)
This patchset adds appropriate bindings for parsing various bcm963xx NOR
flash layouts found in the wild.
The image header is quite limited, and only has fixed fields for the
offsets and sizes of the kernel and rootfs partitions. If any additional
partitions exist, they need to be described externally, e.g. through
fixed partition layouts.
The first two patches add the bindings for the full flash parser for the
"common" case: first erase block bootloader, last erase block nvram,
reminder available for firmware.
The third patch splits out the image header parsing into its own parser.
Then patches four and five add bindings for the split out parser, to
support non-trivial cases with additional partitions, or a non-standard
offset of the firmware partition.
These patches have been in used since a while in OpenWrt.
Changes V1 -> V2:
* dropped the second example from brcm,bcm963xx-imagetag.txt
* added reviewed bys from Rob Herring
Jonas Gorski (5):
dt-bindings: mtd: describe the simple BCM963XX NOR flash layout
mtd: bcm63xxpart: add of_match_table support
mtd: bcm63xxpart: move imagetag parsing to its own parser
dt-bindings: mtd: describe BCM963XX ImageTag format and usage
mtd: parser_imagetag: add of_match_table support
.../brcm,bcm963xx-cfe-nor-partitions.txt | 24 +++
.../mtd/partitions/brcm,bcm963xx-imagetag.txt | 45 +++++
drivers/mtd/Kconfig | 1 +
drivers/mtd/bcm63xxpart.c | 163 ++-------------
drivers/mtd/parsers/Kconfig | 11 +
drivers/mtd/parsers/Makefile | 1 +
drivers/mtd/parsers/parser_imagetag.c | 222 +++++++++++++++++++++
7 files changed, 320 insertions(+), 147 deletions(-)
create mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm,bcm963xx-cfe-nor-partitions.txt
create mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm,bcm963xx-imagetag.txt
create mode 100644 drivers/mtd/parsers/parser_imagetag.c
--
2.13.2
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2019-03-28 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 14:19 Jonas Gorski [this message]
2019-03-28 14:19 ` [PATCH V2 1/5] dt-bindings: mtd: describe the simple BCM963XX NOR flash layout Jonas Gorski
2019-03-29 2:12 ` Florian Fainelli
2019-03-28 14:19 ` [PATCH V2 2/5] mtd: bcm63xxpart: add of_match_table support Jonas Gorski
2019-03-29 2:12 ` Florian Fainelli
2019-03-28 14:19 ` [PATCH V2 3/5] mtd: bcm63xxpart: move imagetag parsing to its own parser Jonas Gorski
2019-03-29 2:19 ` Florian Fainelli
2019-03-28 14:19 ` [PATCH V2 4/5] dt-bindings: mtd: describe BCM963XX ImageTag format and usage Jonas Gorski
2019-03-29 2:13 ` Florian Fainelli
2019-03-28 14:19 ` [PATCH V2 5/5] mtd: parser_imagetag: add of_match_table support Jonas Gorski
2019-03-29 2:13 ` Florian Fainelli
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=20190328141910.5723-1-jonas.gorski@gmail.com \
--to=jonas.gorski@gmail.com \
--cc=bbrezillon@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=f.fainelli@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
/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).