Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5683854imu; Tue, 13 Nov 2018 10:06:43 -0800 (PST) X-Google-Smtp-Source: AJdET5c5lyikX5Hl16A797i+NtRIZMU8KQcO94LqnhulI6B0Vm2JGGoi1VnanxyzqduNaVSNvPDH X-Received: by 2002:a17:902:bcc4:: with SMTP id o4-v6mr6158766pls.13.1542132403374; Tue, 13 Nov 2018 10:06:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542132403; cv=none; d=google.com; s=arc-20160816; b=nn9IzBNC58R+S8mP4D9cz3IEzHo9717+YyhT5y0B6Zgha5Cu8qW4VuP71aPFUfmtQM NJv8gLgvZ5ILLMlZKWfYzzHuIw+n9IXF3ieeezHrNREFl0dWgXy0ViJZnwsLHc7JUQPJ zLgqAbQdHOqIxJVDWP8Yp2mj+ByQWH+CRprC+tgimFi5NkNC40BgzvElUDQPa2hgY5uT uvWSKR0lQsJ+h7SonKW/o9oVaclAP8YHC0RVrCj2M32UBqk1zdbvsR+P3ez2AgrGivGn L1boiQ4eEoevrd9pvShpiHv+P3EcmPpW+Iw78iOW/jKmUYxS1z+MtdC0DYhaC8hOV0Kw SeJQ== 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; bh=G8dI7xC0wCJUXks03e+F96UzLUsA98mIlfOkbBEb2eM=; b=uRyHA9rwRU7AJsP3r5l+JHmMOF6Skwo7q4QWJw27cxiCUoE2PP0yhJM4fhCgzEyLBA hUgFAJZGfmrPoF6SIY7np6CBwV48NkXw9QxaNrrsjUkW9is8+kNMU2yEMv2ho7uqYMq2 8/WGlCejf1MLImZCNx/Pu62bOR7bz4RndGDdMw4tDAhqmIBZg55rO4XCZO1BCRW7Yzxo 6fYLRdxmFOYBu1kOe68K+/dyo6ISjb50XgKTZ7aeU77Jtq1g7BsdHg2wOOyxLXKZbX7c Z0cyK3KxZWCrbFB5CkfAk4e8bGEx5pQs/xlEjPxwTsqwdueGCd0H85zRT16dfood8kT7 JHlA== 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 c81si4027863pfc.196.2018.11.13.10.06.18; Tue, 13 Nov 2018 10:06:43 -0800 (PST) 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 S1732403AbeKNEEy (ORCPT + 99 others); Tue, 13 Nov 2018 23:04:54 -0500 Received: from mga07.intel.com ([134.134.136.100]:30019 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726862AbeKNEEy (ORCPT ); Tue, 13 Nov 2018 23:04:54 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Nov 2018 10:05:41 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,229,1539673200"; d="scan'208";a="279519309" Received: from marshy.an.intel.com ([10.122.105.159]) by fmsmga005.fm.intel.com with ESMTP; 13 Nov 2018 10:05:40 -0800 From: richard.gong@linux.intel.com To: gregkh@linuxfoundation.org, 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, 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, todd.riffel@intel.com, richard.gong@linux.intel.com, richard.gong@intel.com Subject: [PATCHv11 1/8] dt-bindings, firmware: add Intel Stratix10 service layer binding Date: Tue, 13 Nov 2018 12:13:59 -0600 Message-Id: <1542132846-24168-2-git-send-email-richard.gong@linux.intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1542132846-24168-1-git-send-email-richard.gong@linux.intel.com> References: <1542132846-24168-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 Acked-by: Moritz Fischer --- 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 v6: add Moritz's Acked-by v7: no change v8: no change v9: no chnage v10: no change v11: 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