Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp1125951ybc; Tue, 12 Nov 2019 14:53:29 -0800 (PST) X-Google-Smtp-Source: APXvYqzEJReljPnf6+vJRRS160qiYQpdn3O1sJknJxKvzdq+vEQf6K/d0rifIwVO2igad9FCNva7 X-Received: by 2002:aa7:c898:: with SMTP id p24mr176782eds.19.1573599209276; Tue, 12 Nov 2019 14:53:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573599209; cv=none; d=google.com; s=arc-20160816; b=Z02cb4azM4wo9YgNYw3fDvBeCWC07ekYVcT4RvlxFGmqeJ+GYdqDxRE0x4koaDFNwH 2jlFuS/UUUVV7yR+Jv0WOkDTUD1MTrU4CXWyPEeJ3tdhoHfWQ5eguSDqhrXAkWWpxDwI AFitQ1cMg9FmpmXqtkCvhcdiVvBt9Y60JEdpdNmCB9jJdu+QTD5XL27xtfp3sGhkp3zi GddIqKXALtnBsFrvaXMco1VRP26yZuRGX8A8iNt9WxKWZNBkdJJ5eWsGgfB+LFg/IkTo ys2okuRhPScCsvWN6CHXEbGjOJZP0Mjr2GQ5P1W8YPg98m2Go/9nMN9MDVUh6pxq1sfX hMZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:user-agent:subject:cc:to :from:references:in-reply-to:content-transfer-encoding:mime-version :dkim-signature; bh=/g63zHzjma6ujyVqkNTXnmZqsCjjxZ1a06KZmu7dD8k=; b=YShZF+ipnKqTGzEtSov2Y9BXono7TKCMRJXqsHnHh+ajTDSBT12u2nTio+GHKOmvSz ZBQl8E2voVIUk6zsg2aTXdc7QiRyqr3Db8iUuuHtz9gqtwOoNUdg/zl7oxo8Y167KvZM 8AX1pvL6F8d8gvUtULg+UarF/VqXy1dqqaMNgAE4kVu55boIB2TQw2p1c7t1p+FbkWCE zILCewWO25lpIrcvazKQYpe6D76nc2Ha5nMfg+2eTDjbVUPiJ7YDPCByHg0oPp8yD6P0 CNCsDf1UJum/sfTiel7kU5UNqXZlAjQbktYyAgubrjR/zfCkZ2InSCeyW6HWUENbme4E 1+Bg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=wutODIcy; 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=pass (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 z26si978325ejb.223.2019.11.12.14.53.04; Tue, 12 Nov 2019 14:53:29 -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=@kernel.org header.s=default header.b=wutODIcy; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727020AbfKLWvt (ORCPT + 99 others); Tue, 12 Nov 2019 17:51:49 -0500 Received: from mail.kernel.org ([198.145.29.99]:33108 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726906AbfKLWvt (ORCPT ); Tue, 12 Nov 2019 17:51:49 -0500 Received: from kernel.org (unknown [104.132.0.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 7E59D21783; Tue, 12 Nov 2019 22:51:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1573599107; bh=Fvb/mXVl+l35yVh6GFoxh8HIEXMeuT21yKS6scDEvuE=; h=In-Reply-To:References:From:To:Cc:Subject:Date:From; b=wutODIcyfTnTRJBX9L/1YSqE+K/nXW/S5xy8DlXaib2Uh8FHE9K0vxgEFR/AKAGVC YGgb6J7Od/oj3v9K44i5Q7SS4bHPVCTfvH7NhmO9PujmMoNOEm9C1DsclPQjSPdFnE 2pivyDLHR97BdOIO0aLfJ1XD4Wr/LIyLhjpHQ3OQ= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <1573564580-9006-2-git-send-email-rajan.vaja@xilinx.com> References: <1573564580-9006-1-git-send-email-rajan.vaja@xilinx.com> <1573564580-9006-2-git-send-email-rajan.vaja@xilinx.com> From: Stephen Boyd To: Rajan Vaja , dan.carpenter@oracle.com, gustavo@embeddedor.com, jolly.shah@xilinx.com, m.tretter@pengutronix.de, mark.rutland@arm.com, michal.simek@xilinx.com, mturquette@baylibre.com, nava.manne@xilinx.com, ravi.patel@xilinx.com, robh+dt@kernel.org, tejas.patel@xilinx.com Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Rajan Vaja Subject: Re: [PATCH 1/7] dt-bindings: clock: Add bindings for versal clock driver User-Agent: alot/0.8.1 Date: Tue, 12 Nov 2019 14:51:46 -0800 Message-Id: <20191112225147.7E59D21783@mail.kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Rajan Vaja (2019-11-12 05:16:14) > diff --git a/Documentation/devicetree/bindings/clock/xlnx,versal-clk.yaml= b/Documentation/devicetree/bindings/clock/xlnx,versal-clk.yaml > new file mode 100644 > index 0000000..da82f6a > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/xlnx,versal-clk.yaml > @@ -0,0 +1,67 @@ > +# SPDX-License-Identifier: GPL-2.0 > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/bindings/clock/xlnx,versal-clk.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Xilinx Versal clock controller > + > +maintainers: > + - Michal Simek > + - Jolly Shah > + - Rajan Vaja > + > +description: | > + The clock controller is a h/w block of Xilinx versal clock tree. It re= ads hardware instead of h/w > + required input clock frequencies from the devicetree and acts as clock > + provider for all clock consumers of PS clocks. See clock_bindings.txt > + for more information on the generic clock bindings. Please drop this last sentence about clock_bindings.txt > + > +properties: > + compatible: > + const: xlnx,versal-clk > + > + "#clock-cells": > + const: 1 > + > + clocks: > + description: List of clock specifiers which are external input > + clocks to the given clock controller. > + minItems: 3 > + maxItems: 3 > + items: > + - description: ref clk > + - description: alternate ref clk > + - description: pl alternate ref clk What is "pl"? Can you clarify? > + > + clock-names: > + minItems: 3 > + maxItems: 3 > + items: > + - const: ref_clk > + - const: alt_ref_clk > + - const: pl_alt_ref_clk > + > +required: > + - compatible > + - "#clock-cells" > + - clocks > + - clock-names > + > +additionalProperties: false > + > +examples: > + - | > + firmware { > + zynqmp_firmware: zynqmp-firmware { > + compatible =3D "xlnx,zynqmp-firmware"; > + method =3D "smc"; Is there a way to say in the binding that this must be a child of a xlnx,zynqmp-firmware node? That would be ideal so we can constrain this to that location somehow. > + versal_clk: clock-controller { > + #clock-cells =3D <1>; > + compatible =3D "xlnx,versal-clk"; > + clocks =3D <&ref_clk>, <&alt_ref_clk>, <&pl_alt_ref_clk>; > + clock-names =3D "ref_clk", "alt_ref_clk", "pl_alt_ref_clk"; > + }; > + }; > + }; > +...