Received: by 10.223.176.5 with SMTP id f5csp1693083wra; Wed, 31 Jan 2018 10:05:36 -0800 (PST) X-Google-Smtp-Source: AH8x225zotT/AZ3vaZXe4iY8wKHbZXbr0xDOF35l43DFGj3gzBIvPZ9BhRhU8LPX1GPntIk4GoO1 X-Received: by 10.98.232.14 with SMTP id c14mr34892344pfi.215.1517421936443; Wed, 31 Jan 2018 10:05:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517421936; cv=none; d=google.com; s=arc-20160816; b=a5YGFQXCUSynjxQrAZBgZUAfEVC8VllGR/uWgS1ropx/FpSuj3bEOtOOx22890asiC ZprrJbPkxPPwURvfAggrtb6Unn2xMIeXmjPbN2DEyAMlclZoYRVeNpjLHPxGDorB7UaT FagfEqVL5XtaI0si3ClTcZKaL0Q0DqR+1HQD7GLy74mpaxzrOfJdGr9Uzusbra0g54Mz X/iigVDWnz39w8qjcATtjHryz/5yZFYW51aW80y0QWy/da1CNGlCY7863m7ztkZxRR0+ JKKk0V9PH74qmtP6TRPtDI3U/ytmlqL7MOvfHVBUC8kZOkeVNdxKQnEiRLXy9EbfEeoi 22YA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :spamdiagnosticmetadata:spamdiagnosticoutput:content-language :accept-language:in-reply-to:references:message-id:date:thread-index :thread-topic:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=jC/ytgrFbj1BFQkBp30Eq1sTSpxbzwOnjkByoetMOIg=; b=jDBmzneXaYWIAbOgwXo4xhbEto4QjPflx0IY2r178RfrhEhV1EyuNieRN6OV0e03an RcEYFa1zdED2vLPPiabJ0rYVw0DI5+7BfImzt1nuKyuwZGTlFc+bty98yliVl4FL+QBt t8Gwk+T8T7SYu38aw4a8qC8xXKk5vaZ+rj9bGD6pGnu54wGuACBzVPG8Oubai9kVCf/P OTj9KDvzG4TpKixwTIsqQ/3NUBJCo5DVu+LUAAYpXix+IPSHZOFlvGj+l/pZYmtYYaYv SULtn9PYRshp3n00MeGDnTY49hsorXMBLhUr/wYTMm7qGHcDLI1OXyM4RCBsiiu4aWzr /+uw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@xilinx.onmicrosoft.com header.s=selector1-xilinx-com header.b=mQpTrj6R; 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 m3-v6si14278pld.358.2018.01.31.10.05.21; Wed, 31 Jan 2018 10:05:36 -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; dkim=pass header.i=@xilinx.onmicrosoft.com header.s=selector1-xilinx-com header.b=mQpTrj6R; 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 S1753897AbeAaSEl (ORCPT + 99 others); Wed, 31 Jan 2018 13:04:41 -0500 Received: from mail-by2nam03on0086.outbound.protection.outlook.com ([104.47.42.86]:36631 "EHLO NAM03-BY2-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753661AbeAaSDV (ORCPT ); Wed, 31 Jan 2018 13:03:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xilinx.onmicrosoft.com; s=selector1-xilinx-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=jC/ytgrFbj1BFQkBp30Eq1sTSpxbzwOnjkByoetMOIg=; b=mQpTrj6RNrJAnhYhq3Z5CPwLlzt/USIREoRWRSOc2AXdugZJrOjqBJ/D+MN38hghCHBgCMh8yb6aMqOmzz6JZ4fnPqB7m7uTimH0/Juoz/2HL+BmWymskLv4ypMGKvkgxCVARKjraFMKAo/WXbhPuUz+8GciquIfzqyjA5HY8qY= Received: from DM2PR0201MB0767.namprd02.prod.outlook.com (10.160.95.13) by DM2PR0201MB0733.namprd02.prod.outlook.com (10.160.94.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.464.11; Wed, 31 Jan 2018 18:03:16 +0000 Received: from DM2PR0201MB0767.namprd02.prod.outlook.com ([fe80::5d1e:ad23:462e:4de1]) by DM2PR0201MB0767.namprd02.prod.outlook.com ([fe80::5d1e:ad23:462e:4de1%14]) with mapi id 15.20.0464.012; Wed, 31 Jan 2018 18:03:14 +0000 From: Jolly Shah To: Rob Herring 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" , Rajan Vaja Subject: RE: [PATCH v3 1/4] dt-bindings: firmware: Add bindings for ZynqMP firmware Thread-Topic: [PATCH v3 1/4] dt-bindings: firmware: Add bindings for ZynqMP firmware Thread-Index: AQHTlWomdmmvreQR6kiWwxGfbK0z8aOMrwQAgAGhGdA= Date: Wed, 31 Jan 2018 18:03:14 +0000 Message-ID: References: <1516836074-4149-1-git-send-email-jollys@xilinx.com> <1516836074-4149-2-git-send-email-jollys@xilinx.com> <20180130170818.tz4hoqvyekrl7uio@rob-hp-laptop> In-Reply-To: <20180130170818.tz4hoqvyekrl7uio@rob-hp-laptop> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=JOLLYS@xilinx.com; x-originating-ip: [73.162.184.228] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1;DM2PR0201MB0733;7:add0xMe+rSNSpDVxzkX1vnCAbzCGlGg8n/0Z8WZ2Ck/wC2J89zPu/Y1OFK526Qvl9bnlAO3jVG+qmokSRIk7OV+doNWLICWhTsh68PKMFOnshLLgmaAg2rMBr8+2IQy19f3NVFLL8TLhjmX5jSgqurJsbAHOLxmHuuOsG0baknBcelUcARclHbnkvXk/5GM7Yr3lY3NaXefPaVktCb+F2xLFetFCjsohr76ye679wV9Cp2J7Z8rgyMQScL+OrNmF x-ms-exchange-antispam-srfa-diagnostics: SSOS;SSOR; x-forefront-antispam-report: SFV:SKI;SCL:-1;SFV:NSPM;SFS:(10009020)(396003)(39380400002)(376002)(39860400002)(346002)(366004)(189003)(13464003)(51914003)(199004)(3846002)(7696005)(6116002)(6436002)(66066001)(76176011)(102836004)(229853002)(33656002)(305945005)(7736002)(3660700001)(6506007)(53546011)(74316002)(2900100001)(106356001)(4326008)(6916009)(14454004)(2950100002)(478600001)(7416002)(72206003)(39060400002)(107886003)(6246003)(68736007)(5250100002)(8676002)(81166006)(81156014)(5660300001)(8936002)(25786009)(105586002)(99286004)(2906002)(54906003)(55016002)(97736004)(53936002)(316002)(9686003)(26005)(3280700002)(86362001)(186003);DIR:OUT;SFP:1101;SCL:1;SRVR:DM2PR0201MB0733;H:DM2PR0201MB0767.namprd02.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;MX:1;A:1;LANG:en; x-ms-office365-filtering-ht: Tenant x-ms-office365-filtering-correlation-id: 8f18fdf9-4186-493f-5084-08d568d4e647 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(7020095)(4652020)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020);SRVR:DM2PR0201MB0733; x-ms-traffictypediagnostic: DM2PR0201MB0733: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(180628864354917)(9452136761055)(85827821059158)(258649278758335)(192813158149592); x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(6040501)(2401047)(8121501046)(5005006)(10201501046)(3231101)(2400082)(944501161)(3002001)(93006095)(93001095)(6055026)(6041288)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123564045)(20161123562045)(6072148)(201708071742011);SRVR:DM2PR0201MB0733;BCL:0;PCL:0;RULEID:;SRVR:DM2PR0201MB0733; x-forefront-prvs: 056929CBB8 received-spf: None (protection.outlook.com: xilinx.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: bx1kznMjhG0+bmJ+piI7ZYVpT0IC1/uPZk5j6/HUK2wE8nvezvPlLQ7iI2K0DGTYRyCzMsV9cfvzigLEfaekjw== spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: xilinx.com X-MS-Exchange-CrossTenant-Network-Message-Id: 8f18fdf9-4186-493f-5084-08d568d4e647 X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Jan 2018 18:03:14.6280 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 657af505-d5df-48d0-8300-c31994686c5c X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0201MB0733 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob, Thanks for the review, > -----Original Message----- > From: Rob Herring [mailto:robh@kernel.org] > Sent: Tuesday, January 30, 2018 9:08 AM > 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 ZynqM= P > firmware >=20 > 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-firmwa > > re.txt > > b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-firmwa > > re.txt > > new file mode 100644 > > index 0000000..a7aaf56 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/firmware/xilinx/xlnx,zynqmp-fi > > +++ rmware.txt > > @@ -0,0 +1,16 @@ > > +Xilinx Zynq MPSoC Firmware Device Tree Bindings > > + > > +The zynqmp-firmware node describes the interface to platform firmware. >=20 > Please define this a is child of /firmware. > I dint get you. It is already under firmware/xilinx. =20 > Also, some brief summary of what functions the firmware provides would be > nice. >=20 Sure. Will add it in next version. > > + > > +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 >=20 > Do you really need to support hvc? Yes we do support hvc and smc both. >=20 > > + > > +Examples: > > + zynqmp_firmware: zynqmp-firmware { > > + compatible =3D "xlnx,zynqmp-firmware"; > > + method =3D "smc"; > > + }; > > -- > > 2.7.4 > >