Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2079538imu; Tue, 6 Nov 2018 08:47:18 -0800 (PST) X-Google-Smtp-Source: AJdET5f+v6H67hrXVb/fkzTkCGSHoMzeNNsj/BXeAawvEG+rFlDj78Wp66gKhuuW46O3BS3VWJ5l X-Received: by 2002:a17:902:8347:: with SMTP id z7-v6mr2538684pln.340.1541522838785; Tue, 06 Nov 2018 08:47:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541522838; cv=none; d=google.com; s=arc-20160816; b=OJz8RZbVykRoVItxA27RykKCMHAjugeEfjJvwkSMIfNruqfxm4Ftj6AFRudt7JlQUK z0mkZRIcjFyJ2Yg986zZ7ybFm/NLB3f4QH8wKbjZikYk+A5sscci7IVt9j8dr7UgvN9N suO5y27mwnlJgQYUPSYsk+Xni35Qy6tOeP9v6sIwESL6i+ANrTM0P2WK+mLJnRkhYkMu 8fO6kEtkpyGltB5IHebP9eJQk3NTFq54N/WD+pHu5vuvgPDD0ioOOmFOxjWmUjcDObjJ p4Ud+lnpuo+eHlLoIfuZSL2UeSEy6Gs6gIljF5M2FpJfhrefNw7KDNsWRwqI6xohFrpD Au7A== 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=hnLiy/ODAxA0FqzowX8xOxne/ZY7Bn4RCtTUKpjLc00=; b=ZUIEm+x5Ljm3DcL7N9FpqKAeT/0dSAv6dvraoSqtbGSR7ejA3fb0UuRUK4w+v6NNBS No3tj9CA0BSn0wykBUkENOr/rbjL9ew9OQP7Xj7L5z5jlXLW9zFJu6g6XllX6PsNkgH9 A06ukor25FJbJ8guZxZfBkskrWeHbCzm9DV7nIFp30iiLwr3tsrTXU/g1lqt7AMAM0Jg Mvrp71eaOy2vmARy9EA9Y5zRHFS/Rrwg2Ctzlny7Tl7PGt7Ce5Bmhk8ytnrVv05QrT2w DQWhVI+zM8MtcHgky+p2+GdkXSvWtr1/P4WZU2biEao9cz+aC8eeo0ZjVBUausQqv2o8 SJ/g== 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 v69si37170614pgb.3.2018.11.06.08.47.03; Tue, 06 Nov 2018 08:47:18 -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 S2389440AbeKGCM0 (ORCPT + 99 others); Tue, 6 Nov 2018 21:12:26 -0500 Received: from mga12.intel.com ([192.55.52.136]:51168 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388935AbeKGCMZ (ORCPT ); Tue, 6 Nov 2018 21:12:25 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Nov 2018 08:46:22 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,472,1534834800"; d="scan'208";a="83755932" Received: from marshy.an.intel.com ([10.122.105.159]) by fmsmga007.fm.intel.com with ESMTP; 06 Nov 2018 08:46:21 -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@intel.com Subject: [PATCHv10 1/8] dt-bindings, firmware: add Intel Stratix10 service layer binding Date: Tue, 6 Nov 2018 10:52:45 -0600 Message-Id: <1541523172-5171-2-git-send-email-richard.gong@linux.intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1541523172-5171-1-git-send-email-richard.gong@linux.intel.com> References: <1541523172-5171-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 --- .../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