From patchwork Tue Jun 12 10:44:33 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= X-Patchwork-Id: 928236 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=devicetree-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="ALiIcAU1"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 414mlM0tpkz9s1B for ; Tue, 12 Jun 2018 20:46:22 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753448AbeFLKqV (ORCPT ); Tue, 12 Jun 2018 06:46:21 -0400 Received: from mail-lf0-f65.google.com ([209.85.215.65]:39583 "EHLO mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752665AbeFLKqU (ORCPT ); Tue, 12 Jun 2018 06:46:20 -0400 Received: by mail-lf0-f65.google.com with SMTP id t134-v6so35263691lff.6 for ; Tue, 12 Jun 2018 03:46:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=DkS2vIv6zy5q4XJZoJ/JlfgJNu9ILkmm/z/3qXhsdQo=; b=ALiIcAU1aVveN9Qo0PinL8i+ViLa7v2krQTNkMe5HdgU3UnfShe6lDjAHPs9bse+Vf B/jHLP3/oN2qPtojxmU7b2FGbgbp8F86Zjz+BhODmAia1wL6vXJw0i2RXSgvGdI1VgwK Z21enAe8E0BgasAJEbGU1gw9/0cE3Ithl92vJf28sPKShKZC402DtucYvNzDXGDh8m8a 9zI7vAnZt7AX11mXGdADTUacNwdsblJUNFfDRESh/KqkolVMvXtcgCuOpM7noV93+2dd yu7rYqVmehi+YgbAMtuTTIfCuDv29HU/yBCff0hRGq6vxhCBA0TlDl/HroJfWU5BRwjH RWng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=DkS2vIv6zy5q4XJZoJ/JlfgJNu9ILkmm/z/3qXhsdQo=; b=mFT36aqf9+JzPpniGV9LW8ueEWCMc5Qk/XODotIIn8n5mxBcJS8Al1qKuo0dBVtZue +JVmIE1xvoQEvfgddm5V7i7QRzsjBLCUyANshCuNm/TWaeON1N5t4GaEAeo5LB5yRIDZ E1tUVCcZLX6aQVKRhy9NCuGZfzjy+AJBA5x+bNl7AHBaAJHjmeCbij9gcwvaUfMqEW/Q Y5eqqQTqmcidd9XlgVI6wyftvte1XRlBXdh/0pNKiZtIAWaDsjvqCq78EJy/pwuV3KtW eYBsg3BKnwPVvN7t2jcXJb6I9fQb8Kl/L8m8rqqxXK88jvXsiqm3zFuNoQOeMnrHY5rP M76Q== X-Gm-Message-State: APt69E0gkDGWJvlI+TbRopAuaiIhVCZGdzxoXZUn6I1apHgdbm2osG21 dFD/qsEkRMAi/IkuzSIeUQo= X-Google-Smtp-Source: ADUXVKLEryg77BIQt+MtwapEvBujjgiRrn02BVVsZWIh1FUNQAsW+gM0IziwYbGf88Wy7nlHtCUbcg== X-Received: by 2002:a19:9101:: with SMTP id t1-v6mr1751623lfd.29.1528800379197; Tue, 12 Jun 2018 03:46:19 -0700 (PDT) Received: from linux-veee.lan (ip-194-187-74-233.konfederacka.maverick.com.pl. [194.187.74.233]) by smtp.gmail.com with ESMTPSA id o26-v6sm155208ljg.39.2018.06.12.03.46.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 12 Jun 2018 03:46:18 -0700 (PDT) From: =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= To: Brian Norris , David Woodhouse , Boris Brezillon , Marek Vasut , Richard Weinberger , Cyrille Pitchen , Rob Herring Cc: Mark Rutland , linux-mtd@lists.infradead.org, devicetree@vger.kernel.org, Jonas Gorski , =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= Subject: [PATCH 1/2] dt-bindings: mtd: document Broadcom's TRX firmware format binding Date: Tue, 12 Jun 2018 12:44:33 +0200 Message-Id: <20180612104434.15232-1-zajec5@gmail.com> X-Mailer: git-send-email 2.13.7 MIME-Version: 1.0 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org From: Rafał Miłecki 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. Signed-off-by: Rafał Miłecki --- .../bindings/mtd/partitions/brcm,trx.txt | 35 ++++++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 Documentation/devicetree/bindings/mtd/partitions/brcm,trx.txt diff --git a/Documentation/devicetree/bindings/mtd/partitions/brcm,trx.txt b/Documentation/devicetree/bindings/mtd/partitions/brcm,trx.txt new file mode 100644 index 000000000000..e590b884e5ac --- /dev/null +++ b/Documentation/devicetree/bindings/mtd/partitions/brcm,trx.txt @@ -0,0 +1,35 @@ +Broadcom TRX Container Partition +================================ + +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 and 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 partitions. +Its purpose is to store a few partitions in a format that can be distributed as +a standalone file and written in a flash memory. + +Container can hold up to 4 partitions. The first partition has to contain 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. This 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 + +Required properties: +- compatible : (required) must be either: "brcm,trx-v1" or "brcm,trx-v2" + followed by "brcm,trx" + +Example: + +flash@0 { + partitions { + compatible = "brcm,trx-v1", "brcm,trx"; + }; +};