Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp2549673pxk; Mon, 14 Sep 2020 17:09:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxw87MMKUq/VzucN5Fwr27I0PihfCOsiSFgkd8f7PmNK85Sclfo3DabyV7a8NKp7w0unHsD X-Received: by 2002:a17:906:3748:: with SMTP id e8mr13874743ejc.71.1600128598910; Mon, 14 Sep 2020 17:09:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600128598; cv=none; d=google.com; s=arc-20160816; b=NwOlUkMISMVS0aOWGbzLDpvVbZ1CPLTZVAEG94zfPDYcrJgOE6NbTr0NpWOI/KhqDz W3NYJ4+Ii+EQXF4WyGF9GouBysPartj2M3iO1WJwUa50owt/4ObnvcCyLHP56LB2MucE 1cOZSF53FyLWNZQaeiCNZVZt+c8zDrZX4reP70YD6dayY39iudUShTFzMcOt/V9ytIEQ QuaJapQyB0OkgFKVv3nTb/48p4Cq1z6Us5uYvc15V1PhD/xywfWM3n0lrwrKvQxf0g+e TDM3JAGRovS4T9s7YyhoeYds0kC0Lo5jP8Fwm40Cn93ricPK+YJv5TSJuv7+VoazXdv1 Nt7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:date:to:cc:from :subject:references:in-reply-to:content-transfer-encoding :mime-version:dkim-signature; bh=w/1S0nTUmsSTt8xi9nC7AWRmE4z7EuNTcRlq6saj8E4=; b=bnFaVZjB24kIEWrEUdgKgbH1cj73w6eUp1pYJVNWSskUWKwwG56pa/1f3H/BGdKDsU omZic8mjU/R8M26kRwFc5Yl/FqDGlqOBedf2+jRSkZnr6ChA75dgb2zHNmSO11fMHQrx sDFBW8Ztadg9p6nE+TPCvvHMDHkjJvPHpBlEdph4NXmP8Oek9yalfnr7gPX5Ym9g5vSS UzXF7oFDNXBLnCdOj7x4CbLODK72vZLHLL2ZpJO0+DrETqzGc3rFACulGhW8Ht3xMnZu YgQHSZKqyVKZJ6l9lKVNmlKuI4lldVy47vRlFy7QA7D0lqiJVmML2V0A4i3epIvPJKPP 9jww== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=fCupoy2y; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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. [23.128.96.18]) by mx.google.com with ESMTP id h10si3798393eje.414.2020.09.14.17.09.36; Mon, 14 Sep 2020 17:09:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=fCupoy2y; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S1726069AbgIOAHD (ORCPT + 99 others); Mon, 14 Sep 2020 20:07:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:55742 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726013AbgIOAHC (ORCPT ); Mon, 14 Sep 2020 20:07:02 -0400 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 53530208DB; Tue, 15 Sep 2020 00:07:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1600128421; bh=687u1BUQg/1ZmnPl6dLZ+wNLHLAr+aXXJgaQZx/yQZ4=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=fCupoy2yZi1b6Lon2fshR3NSKREDyGmA8OXZZ7nkc8e9fHSbXXXzzvQWnR27mYkZ/ /UXWPHwy7KxvlYyhm8h1QnPCb+Z5SkjR72zmGqznIBzh9OGOI8duUmba83ZR+djuxq wwAib1y1b3pUN10aSoObe7D152uPGBFdt7WsXPvM= Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <1599734644-4791-2-git-send-email-sagar.kadam@sifive.com> References: <1599734644-4791-1-git-send-email-sagar.kadam@sifive.com> <1599734644-4791-2-git-send-email-sagar.kadam@sifive.com> Subject: Re: [PATCH v1 1/3] dt-bindings: fu540: prci: convert PRCI bindings to json-schema From: Stephen Boyd Cc: mturquette@baylibre.com, robh+dt@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com, tglx@linutronix.de, jason@lakedaemon.net, maz@kernel.org, thierry.reding@gmail.com, u.kleine-koenig@pengutronix.de, lee.jones@linaro.org, aou@eecs.berkeley.edu, yash.shah@sifive.com, Sagar Kadam To: Sagar Kadam , devicetree@vger.kernel.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org, linux-riscv@lists.infradead.org Date: Mon, 14 Sep 2020 17:07:00 -0700 Message-ID: <160012842007.4188128.14895985041717484631@swboyd.mtv.corp.google.com> User-Agent: alot/0.9.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Sagar Kadam (2020-09-10 03:44:02) > diff --git a/Documentation/devicetree/bindings/clock/sifive/fu540-prci.ya= ml b/Documentation/devicetree/bindings/clock/sifive/fu540-prci.yaml > new file mode 100644 > index 0000000..49386cd > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/sifive/fu540-prci.yaml > @@ -0,0 +1,75 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +# Copyright (C) 2020 SiFive, Inc. > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/clock/sifive/fu540-prci.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: SiFive FU540 Power Reset Clock Interrupt Controller (PRCI) > + > +maintainers: > + - Sagar Kadam > + - Paul Walmsley > + > +description: > + On the FU540 family of SoCs, most system-wide clock and reset integrat= ion > + is via the PRCI IP block. > + The clock consumer should specify the desired clock via the clock ID > + macros defined in include/dt-bindings/clock/sifive-fu540-prci.h. > + These macros begin with PRCI_CLK_. > + > + The hfclk and rtcclk nodes are required, and represent physical > + crystals or resonators located on the PCB. These nodes should be pres= ent > + underneath /, rather than /soc. > + > +properties: > + compatible: > + enum: > + - sifive,fu540-c000-prci > + description: > + Should have "sifive,-prci", only one value is supported Drop description and have=20 compatible: const: sifive,fu540-c000-prci > + > + reg: > + maxItems: 1 > + description: Describe the PRCI's register target physical address re= gion Drop description. > + > + clocks: > + description: > + Should point to the hfclk device tree node and the rtcclk device t= ree node. s/device tree node//g > + The RTC clock here is not a time-of-day clock, but is instead a hi= gh-stability > + clock source for system timers and cycle counters. Better to have: clocks: items: - const: high frequency clock - const: RTC clock Can you add clock-names too? Making it optional is OK. > + "#clock-cells": > + const: 1 > + > +required: > + - compatible > + - reg > + - clocks > + - "#clock-cells" > + > +additionalProperties: false > + > +examples: > + - | > + //hfclk and rtcclk present under /, in PCB-specific DT data > + hfclk: hfclk { > + #clock-cells =3D <0>; > + compatible =3D "fixed-clock"; > + clock-frequency =3D <33333333>; > + clock-output-names =3D "hfclk"; > + }; Add a newline here? > + rtcclk: rtcclk { > + #clock-cells =3D <0>; > + compatible =3D "fixed-clock"; > + clock-frequency =3D <1000000>; > + clock-output-names =3D "rtcclk"; > + }; These may not be necessary either, just have the clock-controller node reference phandles? > + > + //under /soc, in SoC-specific DT data Don't think this comment is necessary. > + prci: clock-controller@10000000 { > + compatible =3D "sifive,fu540-c000-prci"; > + reg =3D <0x10000000 0x1000>; > + clocks =3D <&hfclk>, <&rtcclk>; > + #clock-cells =3D <1>; > + };