From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.bootlin.com ([62.4.15.54]) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1fbk1j-0001zb-QY for linux-mtd@lists.infradead.org; Sat, 07 Jul 2018 10:01:17 +0000 Date: Sat, 7 Jul 2018 12:01:04 +0200 From: Boris Brezillon To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: Brian Norris , David Woodhouse , Boris Brezillon , Marek Vasut , Richard Weinberger , Cyrille Pitchen , Rob Herring , Mark Rutland , linux-mtd@lists.infradead.org, devicetree@vger.kernel.org, Jonas Gorski , =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Subject: Re: [PATCH V2 1/2] dt-bindings: mtd: document Broadcom's TRX firmware format binding Message-ID: <20180707120104.34687f91@bbrezillon> In-Reply-To: <20180625220508.21242-1-zajec5@gmail.com> References: <20180612104434.15232-1-zajec5@gmail.com> <20180625220508.21242-1-zajec5@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 26 Jun 2018 00:05:07 +0200 Rafa=C5=82 Mi=C5=82ecki wrote: > From: Rafa=C5=82 Mi=C5=82ecki >=20 > Broadcom based home router devices use TRX firmware format. It's a > container that can hold few partitions. If operating system is expected > to access them it has to understand that format and parse flash data > accordingly. >=20 > Signed-off-by: Rafa=C5=82 Mi=C5=82ecki Applied both patches. Thanks, Boris > --- > V2: Drop unneeded "brcm,trx-v1" and "brcm,trx-v2" bindings. > --- > .../bindings/mtd/partitions/brcm,trx.txt | 37 ++++++++++++++++= ++++++ > 1 file changed, 37 insertions(+) > create mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm= ,trx.txt >=20 > diff --git a/Documentation/devicetree/bindings/mtd/partitions/brcm,trx.tx= t b/Documentation/devicetree/bindings/mtd/partitions/brcm,trx.txt > new file mode 100644 > index 000000000000..b677147ca4e1 > --- /dev/null > +++ b/Documentation/devicetree/bindings/mtd/partitions/brcm,trx.txt > @@ -0,0 +1,37 @@ > +Broadcom TRX Container Partition > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D > + > +TRX is Broadcom's official firmware format for the BCM947xx boards. It's= used by > +most of the vendors building devices based on Broadcom's BCM47xx SoCs an= d is > +supported by the CFE bootloader. > + > +Design of the TRX format is very minimalistic. Its header contains > +identification fields, CRC32 checksum and the locations of embedded part= itions. > +Its purpose is to store a few partitions in a format that can be distrib= uted as > +a standalone file and written in a flash memory. > + > +Container can hold up to 4 partitions. The first partition has to contai= n a > +device executable binary (e.g. a kernel) as it's what the CFE bootloader= starts > +executing. Other partitions can be used for operating system purposes. T= his is > +useful for systems that keep kernel and rootfs separated. > + > +TRX doesn't enforce any strict partition boundaries or size limits. All > +partitions have to be less than the 4GiB max size limit. > + > +There are two existing/known TRX variants: > +1) v1 which contains 3 partitions > +2) v2 which contains 4 partitions > + > +There aren't separated compatible bindings for them as version can be tr= ivialy > +detected by a software parsing TRX header. > + > +Required properties: > +- compatible : (required) must be "brcm,trx" > + > +Example: > + > +flash@0 { > + partitions { > + compatible =3D "brcm,trx"; > + }; > +};