Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp709548imm; Wed, 18 Jul 2018 09:18:57 -0700 (PDT) X-Google-Smtp-Source: AAOMgpe041UC5/s1Acl0DEaODC1j0M179KWoFfSL29AKdfs9nSHXqgHhiVY37xypP8RUf+WmMpgX X-Received: by 2002:a62:da07:: with SMTP id c7-v6mr5804384pfh.106.1531930737448; Wed, 18 Jul 2018 09:18:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531930737; cv=none; d=google.com; s=arc-20160816; b=SglmKi8d/525zs5/Hq5sMbsZxw/L1OTcEtFWPW5IMtPvqkCrYul/poRMbwlbOJJq4j +ZR+Q+wS8eWwAyWpo9S9ivI8YvFf/M5/clit7PaHqQaDEaFJ7WsPbZyAt0G8fs4pprhk 9F740Bu49+3BlvU+ha+NpugYe3TTI9fz0P47ahMPoWYRnIS9yQmfMGlZbdAYcr7y65GS MctYFNuZ51LF08wIGb6RLM0SPXM1B6/g2NYO62f6Vkfxc5/BTF+M+l73IJahyjoCNn8k sRSkfu9hhPoSjuIsMATHpmwVlxIYFw/M8nUnzzm5qMdYVAZnRESRcLEHQteACCAe/X27 EK4A== 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=D/YItNboRXMTOj4qmeymeWrLQeM9w00giswRhHD5tmM=; b=FCi2ryrvcbIqPDL1pC5j56OCk1UNwoPcqpZyOOFUZQskE1AqtK4ZVQc4y2ztAWBS0I ko0AziFFYjoJOSoM9ZE4wYfOaJpA8UJXtsRdCLln+vzeUjRO1f9NYzmdiPVvkm3OnvZ+ A9MNp0i8N/U38HGMZRPznC3MFocXjkdOc3RWRQYGJGtzZLEGJAqimke5n8MKls0ysAQM exP2ma4u0aO9jVhMyCNd/CVAs2pXiDYMJOMUOkOULmi0D+65N7zDpTC6bZCSKl+XS9Lr aa23LCuwlpyNyhBC7//LYRizi1xP3vCKj1fvRbN7rLsriAuw2dlRFTsPF0Edk9MP/jpP VwlA== 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 d24-v6si3887229pfb.262.2018.07.18.09.18.42; Wed, 18 Jul 2018 09:18:57 -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 S1731541AbeGRQzL (ORCPT + 99 others); Wed, 18 Jul 2018 12:55:11 -0400 Received: from mga14.intel.com ([192.55.52.115]:3828 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730987AbeGRQzL (ORCPT ); Wed, 18 Jul 2018 12:55:11 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jul 2018 09:16:33 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.51,370,1526367600"; d="scan'208";a="67947018" Received: from marshy.an.intel.com ([10.122.105.159]) by orsmga003.jf.intel.com with ESMTP; 18 Jul 2018 09:16:32 -0700 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, yves.vandervennet@linux.intel.com, richard.gong@intel.com Subject: [PATCHv7 1/9] dt-bindings, firmware: add Intel Stratix10 service layer binding Date: Wed, 18 Jul 2018 11:18:36 -0500 Message-Id: <1531930724-22061-2-git-send-email-richard.gong@linux.intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1531930724-22061-1-git-send-email-richard.gong@linux.intel.com> References: <1531930724-22061-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 --- .../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