From patchwork Thu May 1 10:44:45 2014 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Sachin Kamat X-Patchwork-Id: 4098831 Return-Path: X-Original-To: patchwork-linux-samsung-soc@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.19.201]) by patchwork2.web.kernel.org (Postfix) with ESMTP id 6133BBFF02 for ; Thu, 1 May 2014 10:46:32 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id 9B5AE20304 for ; Thu, 1 May 2014 10:46:31 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id CD18020306 for ; Thu, 1 May 2014 10:46:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753880AbaEAKqa (ORCPT ); Thu, 1 May 2014 06:46:30 -0400 Received: from mail-pa0-f42.google.com ([209.85.220.42]:53247 "EHLO mail-pa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752249AbaEAKq3 (ORCPT ); Thu, 1 May 2014 06:46:29 -0400 Received: by mail-pa0-f42.google.com with SMTP id bj1so3406716pad.15 for ; Thu, 01 May 2014 03:46:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=0pExqz79l01m/2VppgZ9xO+l/Wd/luk7CsKccrwWwE0=; b=KFnNlDrgVJOh7n2/eeF5L56qMVayP6qbdwJIYNhoEHATl2nj5a77G27cfbdSnde5L+ srtLocRAkyjzO6ROZ0FBZuB9pdzhyyB0OfVyOMPQTKV4byy5ECI1FIqrPAuBcB/Sbwxj nzuzmVT+ad11eaDlYs6oY+5ZA9RFprKTIAIu6iRoFg0ELB2mIT0ZE8yx8e5+qd49Oa4j mYZWjU5i7YM9/kVLOfkbV5F5znZm90kiR5OAQ5a9DoSxWaO7MRmb4C9O9nEJ83E+lUQS GEfLcvoUuhiUf/6OwwGz9fVVhHD2fa1Ce8p4N1Kdh0SwqF47cc/5OIsmRAkicVP1uNc2 UkOA== X-Gm-Message-State: ALoCoQmvuwcdHm7yG5vb+UOn2IorZIYf3mli5GNxjKAalhgkcs8lrHBqKpfaMIhOQ2T0hMo17i3/ X-Received: by 10.66.66.66 with SMTP id d2mr19769046pat.36.1398941188775; Thu, 01 May 2014 03:46:28 -0700 (PDT) Received: from linaro.sisodomain.com ([115.113.119.130]) by mx.google.com with ESMTPSA id vx10sm154176373pac.17.2014.05.01.03.46.25 for (version=TLSv1.1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 01 May 2014 03:46:28 -0700 (PDT) From: Sachin Kamat To: linux-samsung-soc@vger.kernel.org Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, arnd@arndb.de, t.figa@samsung.com, kgene.kim@samsung.com, robh+dt@kernel.org, sachin.kamat@linaro.org Subject: [PATCH 2/2] Documentation: DT: Exynos: Bind SRAM though DT Date: Thu, 1 May 2014 16:14:45 +0530 Message-Id: <1398941085-10224-2-git-send-email-sachin.kamat@linaro.org> X-Mailer: git-send-email 1.7.9.5 In-Reply-To: <1398941085-10224-1-git-send-email-sachin.kamat@linaro.org> References: <1398941085-10224-1-git-send-email-sachin.kamat@linaro.org> Sender: linux-samsung-soc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-samsung-soc@vger.kernel.org X-Spam-Status: No, score=-7.5 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=ham 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 SRAM binding documentation. Signed-off-by: Sachin Kamat --- .../devicetree/bindings/arm/exynos/smp-sram.txt | 38 ++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/exynos/smp-sram.txt diff --git a/Documentation/devicetree/bindings/arm/exynos/smp-sram.txt b/Documentation/devicetree/bindings/arm/exynos/smp-sram.txt new file mode 100644 index 000000000000..9969ca22b6af --- /dev/null +++ b/Documentation/devicetree/bindings/arm/exynos/smp-sram.txt @@ -0,0 +1,38 @@ +Samsung Exynos SRAM for SMP bringup: +------------------------------------ + +Samsung SMP-capable Exynos SoCs use part of the SRAM for the bringup +of the cores. Once the core gets powered up it executes the code +that is residing at some specific location of the SRAM. + +Therefore reserved section sub-nodes have to be added to the mmio-sram +declaration. These nodes are of two types depending upon secure or +non-secure execution environment. + +Required sub-node properties: +- compatible : should be + "samsung,exynos4210-sram" : Secure SYSRAM + "samsung,exynos4210-sram-ns" : Non-secure SYSRAM + +The rest of the properties should follow the generic mmio-sram discription +found in ../../misc/sram.txt + +Example: + + sram@02020000 { + compatible = "mmio-sram"; + reg = <0x02020000 0x54000>; + #address-cells = <1>; + #size-cells = <1>; + ranges = <0 0x02020000 0x54000>; + + smp-sram@0 { + compatible = "samsung,exynos4210-sram"; + reg = <0x0 0x1000>; + }; + + smp-sram@53000 { + compatible = "samsung,exynos4210-sram-ns"; + reg = <0x53000 0x1000>; + }; + };