From patchwork Fri Mar 3 09:24:33 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Jerome Forissier X-Patchwork-Id: 734983 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3vZPDf5pBNz9s7b for ; Fri, 3 Mar 2017 20:35:30 +1100 (AEDT) Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=linaro.org header.i=@linaro.org header.b="R02vwMoC"; dkim-atps=neutral Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751074AbdCCJf2 (ORCPT ); Fri, 3 Mar 2017 04:35:28 -0500 Received: from mail-wm0-f49.google.com ([74.125.82.49]:38818 "EHLO mail-wm0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751050AbdCCJf1 (ORCPT ); Fri, 3 Mar 2017 04:35:27 -0500 Received: by mail-wm0-f49.google.com with SMTP id t193so10689398wmt.1 for ; Fri, 03 Mar 2017 01:34:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=aMJKey/wqfT82n/e+MZyWf+d8Taypu4xYwiUZU4JtXI=; b=R02vwMoCekaQVFYaIIij3VQmuVGR72EedNbgoCoXBi7FL+4kV95e9UZcczZAz0Xfk1 CCYwkBas6eKfw5DoEQ4KrZsyC4IMks7Lmq3JlN6J7aFNd1Ny9gzywVIer901BD4CcFmS VoK5PgoPBCJ+VepVbyasXNzXJ6lajQdf++Hek= 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; bh=aMJKey/wqfT82n/e+MZyWf+d8Taypu4xYwiUZU4JtXI=; b=HB++X0GWqy/qfPDeVvLTv2QNETt2UoXgkKo1sEbrOCEnflnD8SY2YEeWv0OXhH4V5Y bEN09CJXSHFm3p1LkZs+j4eVc09cHABvUbmeC3AG5l0eFj1HkgFSTkm9aSi7D7fdChsy c2clF8OmNXeEn35J0G6hKny0mK9y4OoLVAp61AtPN/Xe5X9cJXZqbKr1Oeyl8dW3QI7l dayLUbGY75hOaEz/umFDxDJaAaBauaLDfYjIswZeBnzoxHbvP1sMvj7W0LZJzsZKeRcZ +XQwSXmhzPutBvn4gNLL0/AR3MyxiGZdZaufl1MbBpZ67rSKuv7hQUKAP6Q8ST0qsW9z DtOg== X-Gm-Message-State: AMke39n2bZ9ATJCfOi0aDpiBMkDKAmpsSpRxj5GefX/9Y2aw63ENRO49TzBJNsXDmjZT7Wbw X-Received: by 10.28.65.196 with SMTP id o187mr2077617wma.9.1488533108874; Fri, 03 Mar 2017 01:25:08 -0800 (PST) Received: from jfw540.home (ANice-653-1-542-88.w86-205.abo.wanadoo.fr. [86.205.250.88]) by smtp.gmail.com with ESMTPSA id v1sm14457825wra.65.2017.03.03.01.25.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 03 Mar 2017 01:25:08 -0800 (PST) From: Jerome Forissier To: devicetree@vger.kernel.org Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org, jens.wiklander@linaro.org, christoffer.dall@linaro.org, peter.maydell@linaro.org, robin.murphy@arm.com, Jerome Forissier Subject: [PATCH] Documentation: dt: Add binding for /secure-chosen/stdout-path Date: Fri, 3 Mar 2017 10:24:33 +0100 Message-Id: X-Mailer: git-send-email 2.7.4 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Some platforms may use a single device tree to describe two address spaces, as described in d9f43babb998 ("Documentation: dt: Add bindings for Secure-only devices"). For these platforms it makes sense to define a secure counterpart of /chosen, namely: /secure-chosen. This new node is meant to be used by the secure firmware to pass data to the secure OS. Only the stdout-path property is supported for now. Signed-off-by: Jerome Forissier --- Documentation/devicetree/bindings/arm/secure.txt | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) v2 - Clarify the expected behavior when /secure-chosen/stdout-path is not present (either the property or the node itself), as proposed by Peter and Robin. Note that I have made the fallback to /chosen optional. diff --git a/Documentation/devicetree/bindings/arm/secure.txt b/Documentation/devicetree/bindings/arm/secure.txt index e31303f..c4a818e 100644 --- a/Documentation/devicetree/bindings/arm/secure.txt +++ b/Documentation/devicetree/bindings/arm/secure.txt @@ -32,7 +32,8 @@ describe the view of Secure world using the standard bindings. These secure- bindings only need to be used where both the Secure and Normal world views need to be described in a single device tree. -Valid Secure world properties: +Valid Secure world properties +----------------------------- - secure-status : specifies whether the device is present and usable in the secure world. The combination of this with "status" allows @@ -51,3 +52,19 @@ Valid Secure world properties: status = "disabled"; secure-status = "okay"; /* S-only */ status = "disabled"; /* disabled in both */ status = "disabled"; secure-status = "disabled"; /* disabled in both */ + +The secure-chosen node +---------------------- + +Similar to the /chosen node which serves as a place for passing data +between firmware and the operating system, the /secure-chosen node may +be used to pass data to the Secure OS. Only the properties defined +below may appear in the /secure-chosen node. + +- stdout-path : specifies the device to be used by the Secure OS for + its console output. The syntax is the same as for /chosen/stdout-path. + If the /secure-chosen node exists but the stdout-path property is not + present, the Secure OS should not perform any console output. If + /secure-chosen does not exist, the Secure OS may use the value of + /chosen/stdout-path instead (that is, use the same device as the + Normal world OS).