From patchwork Mon May 9 21:49:21 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Dave Gerlach X-Patchwork-Id: 9050261 Return-Path: X-Original-To: patchwork-linux-arm@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.136]) by patchwork2.web.kernel.org (Postfix) with ESMTP id CE690BF29F for ; Mon, 9 May 2016 21:51:34 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id EC34C2011E for ; Mon, 9 May 2016 21:51:33 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.9]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1E6A8200F3 for ; Mon, 9 May 2016 21:51:33 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1azt48-0006Fb-RB; Mon, 09 May 2016 21:50:12 +0000 Received: from arroyo.ext.ti.com ([192.94.94.40]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1azt41-0005OZ-KX for linux-arm-kernel@lists.infradead.org; Mon, 09 May 2016 21:50:06 +0000 Received: from dflxv15.itg.ti.com ([128.247.5.124]) by arroyo.ext.ti.com (8.13.7/8.13.7) with ESMTP id u49LnhX7020755; Mon, 9 May 2016 16:49:43 -0500 Received: from DLEE70.ent.ti.com (dlee70.ent.ti.com [157.170.170.113]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id u49LnhHr020092; Mon, 9 May 2016 16:49:43 -0500 Received: from dlep33.itg.ti.com (157.170.170.75) by DLEE70.ent.ti.com (157.170.170.113) with Microsoft SMTP Server id 14.3.224.2; Mon, 9 May 2016 16:49:43 -0500 Received: from legion.dal.design.ti.com (legion.dal.design.ti.com [128.247.22.53]) by dlep33.itg.ti.com (8.14.3/8.13.8) with ESMTP id u49LngNB027959; Mon, 9 May 2016 16:49:43 -0500 Received: from localhost (uda0274052.am.dhcp.ti.com [128.247.83.19]) by legion.dal.design.ti.com (8.11.7p1+Sun/8.11.7) with ESMTP id u49Lng305068; Mon, 9 May 2016 16:49:42 -0500 (CDT) From: Dave Gerlach To: , Subject: [PATCH 1/6] Documentation: sram: ti: Add TI SRAM bindings Date: Mon, 9 May 2016 16:49:21 -0500 Message-ID: <1462830566-28708-2-git-send-email-d-gerlach@ti.com> X-Mailer: git-send-email 2.7.3 In-Reply-To: <1462830566-28708-1-git-send-email-d-gerlach@ti.com> References: <1462830566-28708-1-git-send-email-d-gerlach@ti.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20160509_145005_838255_88072EA6 X-CRM114-Status: GOOD ( 13.50 ) X-Spam-Score: -9.0 (---------) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Tony Lindgren , Dave Gerlach Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+patchwork-linux-arm=patchwork.kernel.org@lists.infradead.org X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_MED, RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP Add binding document for TI use of mmio-sram driver for purposes like mapping the region as executable or reserving space needed by secure silicon. Signed-off-by: Dave Gerlach --- Documentation/devicetree/bindings/sram/ti-sram.txt | 47 ++++++++++++++++++++++ 1 file changed, 47 insertions(+) create mode 100644 Documentation/devicetree/bindings/sram/ti-sram.txt diff --git a/Documentation/devicetree/bindings/sram/ti-sram.txt b/Documentation/devicetree/bindings/sram/ti-sram.txt new file mode 100644 index 000000000000..68c4b733c78c --- /dev/null +++ b/Documentation/devicetree/bindings/sram/ti-sram.txt @@ -0,0 +1,47 @@ +TI SRAM Node: +------------- + +Many TI SoC's rely on SRAM for running low-level PM code as part of the +suspend or cpuidle path. Because of this, regions in sram must be mapped +as "memory-exec" or "memory-exec-nocache" in order for the region to be +executable. + +Optional sub-node +----------------- +Some TI SoCs have secure variants that require a certain portion of +the SRAM to be reserved for use by secure software. This can be +marked in the parent SRAM node with a subnode as described in +Documentation/devicetree/bindings/sram/sram.txt. This node can be +added in two ways: + +- From board dts files for secure platforms to avoid adding it + for all SoC variants with a fixed size defined. +- As a dummy node in the .dtsi sram node with any size that will be + modified by a bootloader to the correct size needed. + +Sub-node properties: +- compatible : should be "ti,secure-sram" + +The rest of the properties should follow the generic mmio-sram discription +found in Documentation/devicetree/bindings/sram/sram.txt + +Example: + /* In parent SoC .dtsi */ + ocmcram: ocmcram@40200000 { + compatible = "mmio-sram"; + reg = <0x40200000 0x10000>; /* 64k */ + memory-exec-nocache; + ranges = <0x0 0x40200000 0x10000>; + + #address-cells = <1>; + #size-cells = <1>; + + }; + + /* In board .dts where secure silicon is present */ + &ocmcram { + sram-hs@0 { + compatible = "ti,secure-ram"; + reg = <0x0 0xC000>; + }; + };