Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp2938495imm; Thu, 24 May 2018 19:28:14 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpd1Sa/cEcyGML/SkKM04wPMAWSmNNVqExTNzKmwG36GBkJS2M95/Jtb9XeJRKdyB+/p6/2 X-Received: by 2002:a63:8a4a:: with SMTP id y71-v6mr410120pgd.291.1527215294112; Thu, 24 May 2018 19:28:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527215294; cv=none; d=google.com; s=arc-20160816; b=DC/3W3F3zjm2mzMFSiYMQikKk4or8LiUYziWYmWlXn2/HcZ2dPcumU0sWdXyYBmZJ8 X2DLwpSJN1bMF8MvbAiYi3bUbwBP6tsqXfo95L4VRlVeA8RCMP7snasGEP4W4IWoJNAr 34ACn9qIdovMKXPNZaGkQvXs0h9oTNaZvrdENph/5uf1ZyHRTTOL4yJCnV+yi4QgbtKY WQJk1aIn0bNIzDcQvzW+3kMLq7UtJ75BWmlM/s+PcrhVJSQqaghSkk3JWHLhN4CHyvoO 8s09cm/5EWm1ycawms0GkmQE0Qqkgl96DiTc+7avNie0PAb2P1bmFvWxgLI4b/geCLjW 6krA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:arc-authentication-results; bh=wxGd4ZLeAlSfRK2pmMSpq44ey505vC6E3sEWg0q4c4Q=; b=LLfegXo1qO63R4OJwUPiuvzNPQt1+Xm3+jiR64BT/iKcw6EzlJlcE/OkqEIT0iwi76 I1Q6FFNGANmYZ5cfU2g3CaXDh7bHHp3cG+TksGHuAzPkQgAeil8LaT6EbAsNolPI07EE SRSmuiPwOzA44Go1IcDq6UtwaDfpqeWzeKRhJzeYVzTE6xzGW6SoLPWUs62jGwONg6gw k2wFH2Gx6e5hNZr7DdhVDykd9JhgYN7ArrgTdf3DP2BG7H1l/znKPJzV9ZERMZbpHpEH GZ8m5uBZ7MLkwb9X5zKPM7AR6KARN2TXpDoiQs0FBQ0NmOY1UXpIbjr0MH4hahElrJvp RpdA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 127-v6si4195647pge.159.2018.05.24.19.27.59; Thu, 24 May 2018 19:28:14 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1033682AbeEXQ30 (ORCPT + 99 others); Thu, 24 May 2018 12:29:26 -0400 Received: from mga06.intel.com ([134.134.136.31]:7296 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031486AbeEXQ3S (ORCPT ); Thu, 24 May 2018 12:29:18 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 May 2018 09:29:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,436,1520924400"; d="scan'208";a="51893069" Received: from marshy.an.intel.com ([10.122.105.159]) by FMSMGA003.fm.intel.com with ESMTP; 24 May 2018 09:29:15 -0700 From: richard.gong@linux.intel.com To: catalin.marinas@arm.com, will.deacon@arm.com, dinguyen@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com, atull@kernel.org, mdf@kernel.org, arnd@arndb.de, gregkh@linuxfoundation.org, corbet@lwn.net Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-fpga@vger.kernel.org, linux-doc@vger.kernel.org, yves.vandervennet@linux.intel.com, richard.gong@linux.intel.com, richard.gong@intel.com Subject: [PATCHv5 1/8] dt-bindings, firmware: add Intel Stratix10 service layer binding Date: Thu, 24 May 2018 11:33:13 -0500 Message-Id: <1527179600-26441-2-git-send-email-richard.gong@linux.intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1527179600-26441-1-git-send-email-richard.gong@linux.intel.com> References: <1527179600-26441-1-git-send-email-richard.gong@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Richard Gong Add a device tree binding for the Intel Stratix10 service layer driver Signed-off-by: Richard Gong Signed-off-by: Alan Tull Reviewed-by: Rob Herring --- v2: Change to put service layer driver node under the firmware node Change compatible to "intel, stratix10-svc" v3: No change v4: Add Rob's Reviewed-by v5: No change --- .../bindings/firmware/intel,stratix10-svc.txt | 57 ++++++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 Documentation/devicetree/bindings/firmware/intel,stratix10-svc.txt diff --git a/Documentation/devicetree/bindings/firmware/intel,stratix10-svc.txt b/Documentation/devicetree/bindings/firmware/intel,stratix10-svc.txt new file mode 100644 index 0000000..1fa6606 --- /dev/null +++ b/Documentation/devicetree/bindings/firmware/intel,stratix10-svc.txt @@ -0,0 +1,57 @@ +Intel Service Layer Driver for Stratix10 SoC +============================================ +Intel Stratix10 SoC is composed of a 64 bit quad-core ARM Cortex A53 hard +processor system (HPS) and Secure Device Manager (SDM). When the FPGA is +configured from HPS, there needs to be a way for HPS to notify SDM the +location and size of the configuration data. Then SDM will get the +configuration data from that location and perform the FPGA configuration. + +To meet the whole system security needs and support virtual machine requesting +communication with SDM, only the secure world of software (EL3, Exception +Layer 3) can interface with SDM. All software entities running on other +exception layers must channel through the EL3 software whenever it needs +service from SDM. + +Intel Stratix10 service layer driver, running at privileged exception level +(EL1, Exception Layer 1), interfaces with the service providers and provides +the services for FPGA configuration, QSPI, Crypto and warm reset. Service layer +driver also manages secure monitor call (SMC) to communicate with secure monitor +code running in EL3. + +Required properties: +------------------- +The svc node has the following mandatory properties, must be located under +the firmware node. + +- compatible: "intel,stratix10-svc" +- method: smc or hvc + smc - Secure Monitor Call + hvc - Hypervisor Call +- memory-region: + phandle to the reserved memory node. See + Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt + for details + +Example: +------- + + reserved-memory { + #address-cells = <2>; + #size-cells = <2>; + ranges; + + service_reserved: svcbuffer@0 { + compatible = "shared-dma-pool"; + reg = <0x0 0x0 0x0 0x1000000>; + alignment = <0x1000>; + no-map; + }; + }; + + firmware { + svc { + compatible = "intel,stratix10-svc"; + method = "smc"; + memory-region = <&service_reserved>; + }; + }; -- 2.7.4