Received: by 10.223.176.5 with SMTP id f5csp2945402wra; Thu, 1 Feb 2018 08:25:24 -0800 (PST) X-Google-Smtp-Source: AH8x227SRSOOZWNBquq2oj4RsdtC0JLVs/y0bapY1HpI1KFc84uQV4urU5gVS1xudd/aoA6Xozdg X-Received: by 10.98.15.195 with SMTP id 64mr33187307pfp.225.1517502324034; Thu, 01 Feb 2018 08:25:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517502323; cv=none; d=google.com; s=arc-20160816; b=Um+XYELYEMnVyXMsD7FEwTasOSlprb4zQyWxXKAzCYJJ2rqCYyJS5oex6zDcejOw9o HPIPjjW3JHV+KzGFhxBRMhEKJgBTbbBFz4olmeJXe/VJL3v40iHkm7DG+ktyRSL98bV1 m+X9Bq5KfhYs8T7IIiq1X2YTPDysVZobt/jkXisExh3CaDkLMJZ0n8bYMiJjvd5GVI4X YHw9LVT/LlbfeXDKogBIcdAzpzZr0H9Fu0yjn0fvusPpsaN83olaC+nAhB40YG8pU8b5 WjHkOrnrHnsdXAW4uo2Pkk1n1I7aUHrq9MH9ZiIHesmNOMFgL3FmGuZVkYoOruZkHSzo k8ug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=8X71eeBF/013BK4J+2+XWkxfxMrQ0gcyaD4k3GiwSiE=; b=gxNzw6Uej/Jw7DpoNmzN1cZ/vqHSqpKsWSbBXUIk/N8/a/2PBkwvGw+mC099g56Ccx GMQ1O7cYvdhXcJ4MOIkYPe8dv6cw2k4cjQWICqvvMAuJUU9Kx1erj1sLYXS3YXqziFNN 76pBMW1ljSWfp7Ml14JwpDLjAdM7PLL7g3rfjCMyyFvX4RmfR0yRshdtiPdG7n0jU8wK 62Rjv0TGyU3X/5OoVScH4t6RTl593xc6l9bUoMZcPaZ/aCPz/UZvBlTX3cMxB7xHz25j pVT04qlBri6hb5KpXZa4o9k8vFHdhqLMcoBQvcKXwzr3oKu67Fhz8SwJdykIQ6UmqiDU d1zQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v4-v6si1866817plo.347.2018.02.01.08.25.08; Thu, 01 Feb 2018 08:25:23 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752463AbeBAQYR (ORCPT + 99 others); Thu, 1 Feb 2018 11:24:17 -0500 Received: from mga05.intel.com ([192.55.52.43]:37737 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751567AbeBAQYP (ORCPT ); Thu, 1 Feb 2018 11:24:15 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Feb 2018 08:24:15 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,444,1511856000"; d="scan'208";a="14296841" Received: from marshy.an.intel.com (HELO [10.122.105.159]) ([10.122.105.159]) by orsmga007.jf.intel.com with ESMTP; 01 Feb 2018 08:24:14 -0800 Subject: Re: [PATCHv1] dt-bindings: misc: add Intel Stratix10 service layer binding To: Rob Herring Cc: mark.rutland@arm.com, richard.gong@intel.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <1516735502-16745-1-git-send-email-richard.gong@linux.intel.com> <1516735502-16745-2-git-send-email-richard.gong@linux.intel.com> <20180130165713.nbib54mbj6fhofnt@rob-hp-laptop> From: Richard Gong Message-ID: <28aee16e-0d30-ee01-d4ba-912e0bd8d43a@linux.intel.com> Date: Thu, 1 Feb 2018 10:26:17 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20180130165713.nbib54mbj6fhofnt@rob-hp-laptop> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/30/2018 10:57 AM, Rob Herring wrote: > On Tue, Jan 23, 2018 at 01:25:02PM -0600, richard.gong@linux.intel.com wrote: >> From: Richard Gong >> >> Add a device tree binding for the Intel Stratix10 service layer driver >> >> Signed-off-by: Richard Gong >> --- >> .../devicetree/bindings/misc/intel-service.txt | 56 ++++++++++++++++++++++ >> 1 file changed, 56 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/misc/intel-service.txt >> >> diff --git a/Documentation/devicetree/bindings/misc/intel-service.txt b/Documentation/devicetree/bindings/misc/intel-service.txt >> new file mode 100644 >> index 0000000..254e4a1 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/misc/intel-service.txt >> @@ -0,0 +1,56 @@ >> +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 following are the mandatory properties: >> + >> +- compatible: >> + "intc,svc-1.0" >> +- method: >> + smc or hvc >> + smc - Secure Monitor Call >> + hvc - Hypervisor Call > Do you really need to support hvc or you are just copying and pasting > from other implementations? Thanks for the review. Yes, We need to support hvc. > >> +- memory-region: >> + phandle to the reserved memory node. See >> + Documentation/devicetree/bindings/reserved-memory/reserved-memory.txt >> + for details > Please also put the svc node under the /firmware node and state that in > the binding. Sure, I will fix that in the next version. Regards, Richard > >> + >> +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; >> + }; >> + }; >> + >> + svc { >> + compatible = "intc,svc-1.0"; >> + method = "smc"; >> + memory-region = <&service_reserved> >> + }; >> -- >> 2.7.4 >>