Received: by 10.223.176.5 with SMTP id f5csp1692739wra; Wed, 31 Jan 2018 10:05:21 -0800 (PST) X-Google-Smtp-Source: AH8x227j9bq/KgaYCpVg77iaLyvpCatULxIl+xdgtLMURcgf6SftHzRtlFQnGJCD7l4tNMS4sYSr X-Received: by 10.101.64.4 with SMTP id f4mr26289567pgp.171.1517421921778; Wed, 31 Jan 2018 10:05:21 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517421921; cv=none; d=google.com; s=arc-20160816; b=GbYfbdd/zLM9DH7S1H65lcTbzkaDSPcoev9c+MToXVD6E9jCO40DXMaI1u4b1lWGSU alqtxxAnG/jPUOEk0XdMvhY78gGAYsZZ1n24BJQqCmdUTt5IxV2vjqlu7WHlXIJFwO8Q my4XwUZThIUqg1sfnVOSzRb1BIfT0wV7is8MEXjSGWESFEdHGOa1eCw2dzz+u7tJQltk QDKho5t+/YqLzpm4FCB+GZdJ1ZA69bgOA3Yu+VN1NPG4+3UgSiXkwGa3JKLDKcQb7wIT hcaJlFcM6qI4b9UqPuHP2dp2p8c/uDfEQMAXAhVlY2CGlq1T+twaEB8groUOJ0TN/6IX s7dw== 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=aCnuE7a/MjfqYskROSICJpVHG99MV2VeRxoly7mrd90=; b=zCgMemlKe9EBuV01ICPwPrk/cFF+4P4dl5CzRPs/MHxJE3/gu9FBUZopi+xXgZG0xj a053ck723gLcQ1IbO4rfqtdbEAtHran5RR6bNX1WTfMbfifCvJUhocZXxUtvCJXq9oUa 1itVfPNZqPsjvDEbgOSnJG57EcTBWT/6xdMlIBN6gZixQCECkANF2K1TGKfozbK3eVLb 7M34d2lPAbuwDXIAGTpPq/he6oiIEgaq4Xdm5gI/ggJiPioNjm5/9K0D7nUlWzkHNATp WAa+pxu5FMATYilnAaoYxDZ/H7hWPCHvjxjC0jG5eAaFny9dI/1FV2K7cU9fiXLJwe0/ SXWw== 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 d63si1800723pgc.260.2018.01.31.10.05.07; Wed, 31 Jan 2018 10:05:21 -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 S1753677AbeAaSEM (ORCPT + 99 others); Wed, 31 Jan 2018 13:04:12 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:40940 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753733AbeAaSEK (ORCPT ); Wed, 31 Jan 2018 13:04:10 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 4989E1529; Wed, 31 Jan 2018 10:04:10 -0800 (PST) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.72.51.249]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9CF323F487; Wed, 31 Jan 2018 10:04:07 -0800 (PST) Date: Wed, 31 Jan 2018 18:03:54 +0000 From: Mark Rutland 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, robh+dt@kernel.org, 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: <20180131180354.mqf4gvvprdtycbn5@lakrids.cambridge.arm.com> 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/20170113 (1.7.2) 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. Is there any documentation for this that can be referred to? > + > +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 Please specify what exactly these mean. I assume these follow the SMCCC. If so, this can be: - method: The method of calling the PM-API firmware layer. Permitted values are: - "smc" : SMC #0, following the SMCCC - "hvc" : HVC #0, following the SMCCC Otherwise, this looks ok to me. Thanks, Mark. > + > +Examples: > + zynqmp_firmware: zynqmp-firmware { > + compatible = "xlnx,zynqmp-firmware"; > + method = "smc"; > + }; > -- > 2.7.4 >