Received: by 10.223.176.5 with SMTP id f5csp167028wra; Tue, 30 Jan 2018 09:36:32 -0800 (PST) X-Google-Smtp-Source: AH8x227AF9Q3P5u9hE6ndEhxCPCqac0QZZVd1LrZoyTeo2FkiPzmsLBpdXOeWwj0zr498h8KdVeS X-Received: by 10.98.59.149 with SMTP id w21mr30860340pfj.7.1517333792643; Tue, 30 Jan 2018 09:36:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517333792; cv=none; d=google.com; s=arc-20160816; b=ufu3ml8ev8S+cCW/K3DnSC3ks04aCBQ2KZNyHB89xbJQiOn5lkWcpALjU3Zg+FUjGK JuN9Y3JFgsm4NVHDLUJXhAjfedF5p8pMsTn5lCuUBBkfKd/xWlImLqnA8uSTtLe4+VOq jsN7kev64ZaEOJfVefkDk6nsoiY+s/33rjFSzT8oUinNbjzEwsUWAggSfi0zGiv0vC7y MDKyU+t+Iepkp3JNluE/hWh9NkU5yvZwT41rETJAkdzIYgP2AizCEQS5H7I4mu1wxUPE ymjPLLRNipAf6adua9lmNHYUZY/dBZbNA+J3xzTuzfvcUXetMulmUB/3zJfDtx3EsiQO CeSQ== 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=gaXFMTx0ikGEWmIziF4B/FgfghuA8Jft7rv7E2oWYfM=; b=A3KuyPKY5RtKVlbaMtca+/0nlKA+nm5QM5MrFj3T55G49kcHh1SF+tsYLEWGXTv/Vt 1DqoMFZhaxqe4qsM52KvL5hsciHDHIs8xgLukYK0I/bOX+zOGRIAwvDt1e5U4er9kMmC 27X6+G6s46AQMYBvZtoh0OflHPdoYk8eHnOP9HdGUrok7v3zXn/nNZBN2Kgu/s7eeLIX QDFjUjUl+0FjD45BHR+YAMmn4gLBW9DdFj6bdYCHFYaqRnB4oNemzDLvuFJY/RTbpO9O GQWlK6wvauU9fRr2LpCKJOjFfbmPbZC+b5WBoGjIK3j34oK2F7Z+frbfZDcvKvGJJVWq M+Zg== 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 a23si2249985pff.83.2018.01.30.09.36.18; Tue, 30 Jan 2018 09:36:32 -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 S1752564AbeA3RIW (ORCPT + 99 others); Tue, 30 Jan 2018 12:08:22 -0500 Received: from mail-ot0-f195.google.com ([74.125.82.195]:41777 "EHLO mail-ot0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751474AbeA3RIU (ORCPT ); Tue, 30 Jan 2018 12:08:20 -0500 Received: by mail-ot0-f195.google.com with SMTP id r23so9140430ote.8; Tue, 30 Jan 2018 09:08:19 -0800 (PST) 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=gaXFMTx0ikGEWmIziF4B/FgfghuA8Jft7rv7E2oWYfM=; b=qTrS7xzmf6IHjRDtd5UEuCCJ7FjAXkbVQHI5OelfbamLTlPrSYaAq3ybL+W2z2rgAb r+GXwJxrpQgtmP7S2akJfDDNfvC9I9WxhCmwR4Gor4DEKdhCMcKpg0dpnobvbH5++Rec cBRpRMBMZVfXRFoLkZhJQ29igvUuVltAmdcukeWACuUKefqy/44wlfLc6hGRd9+S0Yyf 8ip1vgVaJvFHRxKyk6EbplPHa2zYNX1rjJoL/Kcua8oGaT8qx+R5kqe6OgtU9dBDXajK /LgYtaqFBOoGAUTbubzMUiJPjWY0systJnhkPp8ptWlqcxpFeFNFwu+w4t6xINbPKQzq eyIQ== X-Gm-Message-State: AKwxyteseg3jSEGWuzLkOyUOiypg1LREsp7ulrZTUUiJrgpJd3Jbpb4Z dfJJwaP5HgDstEAsfKu117mQcH0= X-Received: by 10.157.31.43 with SMTP id x40mr22984807otd.37.1517332099477; Tue, 30 Jan 2018 09:08:19 -0800 (PST) Received: from localhost (216-188-254-6.dyn.grandenetworks.net. [216.188.254.6]) by smtp.gmail.com with ESMTPSA id t18sm2319749oti.56.2018.01.30.09.08.18 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 30 Jan 2018 09:08:18 -0800 (PST) Date: Tue, 30 Jan 2018 11:08:18 -0600 From: Rob Herring To: Jolly Shah Cc: ard.biesheuvel@linaro.org, mingo@kernel.org, gregkh@linuxfoundation.org, matt@codeblueprint.co.uk, sudeep.holla@arm.com, hkallweit1@gmail.com, keescook@chromium.org, dmitry.torokhov@gmail.com, michal.simek@xilinx.com, mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Jolly Shah , Rajan Vaja Subject: Re: [PATCH v3 1/4] dt-bindings: firmware: Add bindings for ZynqMP firmware Message-ID: <20180130170818.tz4hoqvyekrl7uio@rob-hp-laptop> References: <1516836074-4149-1-git-send-email-jollys@xilinx.com> <1516836074-4149-2-git-send-email-jollys@xilinx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1516836074-4149-2-git-send-email-jollys@xilinx.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 24, 2018 at 03:21:11PM -0800, Jolly Shah wrote: > Add documentation to describe Xilinx ZynqMP firmware driver > bindings. Firmware driver provides an interface to firmware > APIs. Interface APIs can be used by any driver to communicate > to PMUFW (Platform Management Unit). > > Signed-off-by: Jolly Shah > Signed-off-by: Rajan Vaja > --- > .../bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > create mode 100644 Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt > > diff --git a/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt > new file mode 100644 > index 0000000..a7aaf56 > --- /dev/null > +++ b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt > @@ -0,0 +1,16 @@ > +Xilinx Zynq MPSoC Firmware Device Tree Bindings > + > +The zynqmp-firmware node describes the interface to platform firmware. Please define this a is child of /firmware. Also, some brief summary of what functions the firmware provides would be nice. > + > +Required properties: > + - compatible: Must contain: "xlnx,zynqmp-firmware" > + - method: The method of calling the PM-API firmware layer. > + Permitted values are: > + - "smc" : To be used in configurations without a hypervisor > + - "hvc" : To be used when hypervisor is present Do you really need to support hvc? > + > +Examples: > + zynqmp_firmware: zynqmp-firmware { > + compatible = "xlnx,zynqmp-firmware"; > + method = "smc"; > + }; > -- > 2.7.4 >