Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp2941116imm; Thu, 24 May 2018 19:31:56 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrUa0U8JnAsjJePViDeHNvrEQV3HH8qwZAm5oeF/SoxeySuXsccq8KwRuo/RpatlfBMJfV2 X-Received: by 2002:a62:428f:: with SMTP id h15-v6mr576795pfd.156.1527215516380; Thu, 24 May 2018 19:31:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527215516; cv=none; d=google.com; s=arc-20160816; b=x8fqA2EXHkYQOymqLLMCgieiaP6v9xdttIiwOT07qnnHErdXndcz0Th04b1ZAupDzY wOP0fkan0kYrxs4Uuq/pj2f3gqYSQGhejYEEfs0nu2TaV0pfwD7WqJrn27Ked3nCJUr8 l1iYXiF+om71+NXHxh2d2iRS8pxUpqTrvLW6f1qU2sJpzZFBR3D+GJTLYlC1bqfHSK95 w650p6XTPwncw0jCi6IYJfOKQL4Ufz4tSkyQn2WkZFGhF6WOz7pl/HPyUJCEurA6dWTG k9tI5qHAh2KBtrChYlgOPaayDX6esHJGt7aixMtMP5mmaCbVQPvrQTx6IiLWSTxFJQyx vwBw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=5xp/9mx+HMw9gJTe+k2GM5Ai9nj0GKZs7pdSCUvCm7k=; b=utucufIlYuWwKRT3cu+yB0gKVldYZ8kSPJMCuItBuT9twvYeKfTpLoGakZQSP+cT7O I3gRpDYSqGX6Fsp7tx2J2dxVMfelDyL9y+nGa3ySOUCg3s420SZOK3vQnwR35z53KPx8 1ye4tn6LANPtPVIPzYl/YERyILWInYtFfUnonEZYxxBH2ZOVBUUlULZtEePS90kkgrIW p3gYVu96Sr7k6G+xscmwfROGDwOJeSXfgGzZLI5wKpPZKLPYBOeYXQSLjKPUUHxzrOdj 6nUZ0jQ9G1tl8dAP3TZrlw+CviFYGbuyEmBdoOZIVWicLIqbn0ralsuDzhZu6pHiGfTZ g8kA== 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j61-v6si4093637plb.68.2018.05.24.19.31.41; Thu, 24 May 2018 19:31:56 -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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1034031AbeEXREY (ORCPT + 99 others); Thu, 24 May 2018 13:04:24 -0400 Received: from mail-pf0-f196.google.com ([209.85.192.196]:42237 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1034022AbeEXREN (ORCPT ); Thu, 24 May 2018 13:04:13 -0400 Received: by mail-pf0-f196.google.com with SMTP id p14-v6so1187566pfh.9 for ; Thu, 24 May 2018 10:04:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=5xp/9mx+HMw9gJTe+k2GM5Ai9nj0GKZs7pdSCUvCm7k=; b=TZR1gDQiXmbui243T5uv16v9PsDb5jb5qlWEx18pA0moVCd7mEB85eohBL+og+/eYv J+lUlQHpeNwbZurEK0n9Jhaxi6TkKa6Tr+mSIl4dqgBQmLcxMrXEj1Vj7DklNzgBdicl mQp5CjRz6QLPlvpbWJOmCYmvM2lshZwHD9xFA2MdF5K2hJbrN9AmUwy7NNF7J15YpeHx DzHXvs2qQUFF8EKFubHzZjWlrPWitek7IjsJZP3cK0l70hAtPWPHYgPsym0WpaaQA13x D9R5250oqauXj5pO9oJRQuulrVKVI8WR74YJzx1BoZbLUdJRQKEb0xuYx2KUilmn/CQo 7OxA== X-Gm-Message-State: ALKqPwfOduCHEvXdbf3NIv2ocVBcEJmYYpj5TvaSYxsJ8XYcGayWmw+4 iUvd6qHC71ORm7VkJ38m4+3mGg== X-Received: by 2002:a62:4b16:: with SMTP id y22-v6mr8177400pfa.29.1527181452540; Thu, 24 May 2018 10:04:12 -0700 (PDT) Received: from localhost ([207.114.172.147]) by smtp.gmail.com with ESMTPSA id t14-v6sm48190121pfh.109.2018.05.24.10.04.10 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 24 May 2018 10:04:11 -0700 (PDT) Date: Thu, 24 May 2018 10:04:09 -0700 From: Moritz Fischer To: richard.gong@linux.intel.com Cc: 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, 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: Re: [PATCHv5 1/8] dt-bindings, firmware: add Intel Stratix10 service layer binding Message-ID: <20180524170409.GA4051@archbook> References: <1527179600-26441-1-git-send-email-richard.gong@linux.intel.com> <1527179600-26441-2-git-send-email-richard.gong@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1527179600-26441-2-git-send-email-richard.gong@linux.intel.com> User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 24, 2018 at 11:33:13AM -0500, 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 > 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 > --- > .../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 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-fpga" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html