From: Jonas Gorski <jonas.gorski@gmail.com> To: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org Cc: Mark Rutland <mark.rutland@arm.com>, Florian Fainelli <f.fainelli@gmail.com>, Marek Vasut <marek.vasut@gmail.com>, Richard Weinberger <richard@nod.at>, Boris Brezillon <boris.brezillon@bootlin.com>, Rob Herring <robh+dt@kernel.org>, Brian Norris <computersforpeace@gmail.com>, David Woodhouse <dwmw2@infradead.org> Subject: [PATCH 0/5] mtd: bcm63xxpart: add device tree support Date: Tue, 28 Aug 2018 13:19:39 +0200 [thread overview] Message-ID: <20180828111944.5956-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. 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 | 78 ++++++++ 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, 353 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/
WARNING: multiple messages have this Message-ID (diff)
From: Jonas Gorski <jonas.gorski@gmail.com> To: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org Cc: David Woodhouse <dwmw2@infradead.org>, Brian Norris <computersforpeace@gmail.com>, Boris Brezillon <boris.brezillon@bootlin.com>, Marek Vasut <marek.vasut@gmail.com>, Richard Weinberger <richard@nod.at>, Rob Herring <robh+dt@kernel.org>, Mark Rutland <mark.rutland@arm.com>, Florian Fainelli <f.fainelli@gmail.com> Subject: [PATCH 0/5] mtd: bcm63xxpart: add device tree support Date: Tue, 28 Aug 2018 13:19:39 +0200 [thread overview] Message-ID: <20180828111944.5956-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. 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 | 78 ++++++++ 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, 353 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
next reply other threads:[~2018-08-28 11:19 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-08-28 11:19 Jonas Gorski [this message] 2018-08-28 11:19 ` [PATCH 0/5] mtd: bcm63xxpart: add device tree support Jonas Gorski 2018-08-28 11:19 ` [PATCH 1/5] dt-bindings: mtd: describe the simple BCM963XX NOR flash layout Jonas Gorski 2018-08-28 11:19 ` Jonas Gorski 2018-09-04 13:33 ` Rob Herring 2018-09-04 13:33 ` Rob Herring 2018-08-28 11:19 ` [PATCH 2/5] mtd: bcm63xxpart: add of_match_table support Jonas Gorski 2018-08-28 11:19 ` Jonas Gorski 2018-08-28 11:19 ` [PATCH 3/5] mtd: bcm63xxpart: move imagetag parsing to its own parser Jonas Gorski 2018-08-28 11:19 ` Jonas Gorski 2018-08-28 11:19 ` [PATCH 4/5] dt-bindings: mtd: describe BCM963XX ImageTag format and usage Jonas Gorski 2018-08-28 11:19 ` Jonas Gorski 2018-09-04 0:30 ` Rob Herring 2018-09-04 0:30 ` Rob Herring 2018-09-10 9:02 ` Jonas Gorski 2018-09-10 9:02 ` Jonas Gorski 2018-09-10 9:09 ` Jonas Gorski 2018-09-10 9:09 ` Jonas Gorski 2018-09-10 12:12 ` Rob Herring 2018-09-10 12:12 ` Rob Herring 2018-08-28 11:19 ` [PATCH 5/5] mtd: parser_imagetag: add of_match_table support Jonas Gorski 2018-08-28 11:19 ` Jonas Gorski
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=20180828111944.5956-1-jonas.gorski@gmail.com \ --to=jonas.gorski@gmail.com \ --cc=boris.brezillon@bootlin.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: linkBe 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.