From: "Rafał Miłecki" <zajec5@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Rob Herring <robh+dt@kernel.org>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org,
"Jonas Gorski" <jonas.gorski@gmail.com>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH V2 1/2] dt-bindings: mtd: document Broadcom's BCM47xx partitions
Date: Tue, 22 May 2018 09:46:31 +0200 [thread overview]
Message-ID: <5267836f-7f30-ceb5-14da-93abca3db63b@gmail.com> (raw)
In-Reply-To: <20180509081729.28347-1-zajec5@gmail.com>
Hi Rob,
On 09.05.2018 10:17, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Broadcom based home router devices use partitions which have to be
> discovered in a specific way. They are not fixed and there is not any
> standard partition table. This commit adds and describes a new custom
> binding for such devices.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> This commit documents a new binding for describing partitions. Just as a
> reminder: we agreed to use "compatible" for that purpose to avoid
> /guessing/. There are too many cases, devices and /formats/ to just
> blindly try every possible parser.
>
> This was e.g. described by Boris in his patchset 2+ years ago:
> [RFC PATCH 0/7] mtd: partitions: add of_match_table support
> http://lists.infradead.org/pipermail/linux-mtd/2015-December/064076.html
>
> Quote:
>> (2) we can't just scan for all supported parsers (like the block system does), since
>> there is a wide diversity of "formats" (no standardization), and it is not
>> always safe or efficient to attempt to do so, particularly since many of
>> them allow their data structures to be placed anywhere on the flash, and
>> so require scanning the entire flash device to find them.
>
> I believe this solution was also acked back then by Rob:
> [RFC PATCH 3/7] doc: dt: mtd: partition: add on-flash format binding
> http://lists.infradead.org/pipermail/linux-mtd/2015-December/064100.html
>
> V2: Move documentation to the new brcm,bcm947xx-cfe-partitions.txt file
> as suggested by Rob (we don't want to bloat partition.txt).
> Slightly update commit message.
I sent this V2 per your request from V1:
On 8 May 2018 at 18:25, Rob Herring <robh@kernel.org> wrote:
> I guess this is fine. Can you resend as I don't have the original patch.
>
> I think it should be a separate file though as partition.txt would
> become very long if every vendor partitioning was added there.
Would you find a moment to review/nack/ack it, please?
next prev parent reply other threads:[~2018-05-22 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 8:17 [PATCH V2 1/2] dt-bindings: mtd: document Broadcom's BCM47xx partitions Rafał Miłecki
2018-05-09 8:17 ` [PATCH V2 2/2] mtd: bcm47xxpart: add of_match_table with a new DT binding Rafał Miłecki
2018-05-22 7:46 ` Rafał Miłecki [this message]
2018-05-22 17:30 ` [PATCH V2 1/2] dt-bindings: mtd: document Broadcom's BCM47xx partitions Rob Herring
2018-05-23 11:34 ` Boris Brezillon
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=5267836f-7f30-ceb5-14da-93abca3db63b@gmail.com \
--to=zajec5@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=jonas.gorski@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=rafal@milecki.pl \
--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