Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp1066768pxu; Thu, 17 Dec 2020 01:02:55 -0800 (PST) X-Google-Smtp-Source: ABdhPJzw65zqvG2qj+CTwD+26FGEm8vxjbePmk3Y6kccCQoOmMMfcDKvNZSNVssoLMr9XGtpjtQa X-Received: by 2002:a17:906:6d0b:: with SMTP id m11mr33608071ejr.230.1608195775031; Thu, 17 Dec 2020 01:02:55 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1608195775; cv=none; d=google.com; s=arc-20160816; b=Ovkfb9F29hpdFQZFGDjj+vjkfVnzGIHF4Blojy9jlVVx8xcRBSt5QhPYsy5B5E0xgo GRKCpxLNkNMsjmJmk2Iak8/EpWL8eAHRtNPN//bATB/IY3LiU13giBV4AIKh9UbIs9zB LFjwmTE1YPTi0SbFoskz6VlhHJMvjvlQXmDl1ZSVlKqb5fpsO8SnC1nI0s/t/qTIXZxT c8oByWg2ltW51NC/RKe1sZVIUXuHobznRPdFu+FH+i/DOf9iiIOXRcjLL9VCoyFpuWJP LzVuTfBp/OiJgwos5fe6YIlbmc4vHmpNsTYHnVcpH4U/l5Psc2NI+uDuM9F1KWsQWxYP /JTw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:message-id:date:to:cc:from:subject :references:in-reply-to:content-transfer-encoding:mime-version :dkim-signature; bh=DN+xFbSBzljI4dT360nXSR8LL5ZY4XhvldMW07Un+Vc=; b=gBAcydH7Gi7X4/xE/gzcXNfLo/6cT4TqMhsudB5twkTaVOrSnEfJ8l2lRJdZWHZGSr VIowRB3SwXCJTi8bFdpTVLt2UTeIVS8DXL0ytmDsckrhPN7agEdQIjLbLvHLuMKxNHWx Oug5ahN1obOF7ywCsdPsIzHgdSZrpGEx9Xf9Dc06u8XFUE8C82S0Yur54obZ5ZdFMT86 CNaU2kuT+sd7TqHwDaKiVGjNQLNHzfAmO/3ICMFgs7HGj6/Fv5u20sVcHQHjfW4SkLEo pybNA/UHAXiHtzaObDCQirB3v7WesQbn52s9tbUG/PiZQvUaAZHx/pH4SDWZf1iQokl4 DS6g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=jSM8yIJe; 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 x25si3894469edi.388.2020.12.17.01.02.31; Thu, 17 Dec 2020 01:02:55 -0800 (PST) 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=k20201202 header.b=jSM8yIJe; 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 S1727448AbgLQI7J (ORCPT + 99 others); Thu, 17 Dec 2020 03:59:09 -0500 Received: from mail.kernel.org ([198.145.29.99]:32996 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725950AbgLQI7I (ORCPT ); Thu, 17 Dec 2020 03:59:08 -0500 Content-Type: text/plain; charset="utf-8" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1608195507; bh=89Rrw3aBfmj49VIcsFK0hxM3oXxLCW7ouMh8y82kb8c=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=jSM8yIJeNXE2vbVBtrhtHPxiIvg3M2ZUY4PpsQ6HWbzbJ57SHE7Su1WHykBMYxJfv 7Oet2owLzFdWUI7lKwBCNx1Vhm0MmL9Qr9p6QM9EcWH3dZSse/NhX0IKLuPCeFhLp/ mvXDJARC/IrF++8iS9JIh6MdK/N1yM30FbdQM2hEdXi7HRbTW66pN3dQ7abUhi87a4 JhrKcevsI++WNiAtoNs7ZnNFtYOZQN+WlIGNRXSMY4P/zHHz4opdahBPzpfcheuR/V VdAV3dgvfPJeH9QniPA9YLljEidWSb5XcqQchHh5xFooX9LHZni7L1Aknyp94dXP1J w4bk84/dNUniw== MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20201122095556.21597-3-sergio.paracuellos@gmail.com> References: <20201122095556.21597-1-sergio.paracuellos@gmail.com> <20201122095556.21597-3-sergio.paracuellos@gmail.com> Subject: Re: [PATCH v4 2/6] dt: bindings: add mt7621-clk device tree binding documentation From: Stephen Boyd Cc: robh+dt@kernel.org, john@phrozen.org, tsbogend@alpha.franken.de, gregkh@linuxfoundation.org, gch981213@gmail.com, hackpascal@gmail.com, linux-clk@vger.kernel.org, evicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org, devel@driverdev.osuosl.org, neil@brown.name To: Sergio Paracuellos , mturquette@baylibre.com Date: Thu, 17 Dec 2020 00:58:26 -0800 Message-ID: <160819550615.1580929.14234996916739809712@swboyd.mtv.corp.google.com> User-Agent: alot/0.9.1 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Sergio Paracuellos (2020-11-22 01:55:52) > Adds device tree binding documentation for clocks in the > MT7621 SOC. >=20 > Signed-off-by: Sergio Paracuellos > --- > .../bindings/clock/mediatek,mt7621-clk.yaml | 67 +++++++++++++++++++ > 1 file changed, 67 insertions(+) > create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt76= 21-clk.yaml >=20 Rob? > diff --git a/Documentation/devicetree/bindings/clock/mediatek,mt7621-clk.= yaml b/Documentation/devicetree/bindings/clock/mediatek,mt7621-clk.yaml > new file mode 100644 > index 000000000000..6aca4c1a4a46 > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/mediatek,mt7621-clk.yaml > @@ -0,0 +1,67 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/clock/mediatek,mt7621-clk.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: MT7621 Clock Device Tree Bindings > + > +maintainers: > + - Sergio Paracuellos > + > +description: | > + The MT7621 has a PLL controller from where the cpu clock is provided > + as well as derived clocks for the bus and the peripherals. It also > + can gate SoC device clocks. > + > + Each clock is assigned an identifier and client nodes use this identif= ier > + to specify the clock which they consume. > + > + All these identifiers could be found in: > + [1]: . > + > + The mt7621 clock node should be the child of a syscon node with the > + required property: > + > + - compatible: Should be one of the following: > + "mediatek,mt7621-sysc", "syscon" > + > + Refer to the bindings described in > + Documentation/devicetree/bindings/mfd/syscon.yaml > + > +properties: > + compatible: > + const: mediatek,mt7621-clk > + > + "#clock-cells": > + description: > + The first cell indicates the clock gate number, see [1] for availa= ble > + clocks. > + const: 1 > + > + clock-output-names: > + maxItems: 8 > + > +required: > + - compatible > + - '#clock-cells' > + - clock-output-names Why is clock-output-names required? Hopefully it is not required. > + > +additionalProperties: false > + > +examples: > + - | > + #include > + > + sysc: sysc@0 { syscon@0? I don't think sysc is a standard node name. > + compatible =3D "mediatek,mt7621-sysc", "syscon"; > + reg =3D <0x0 0x100>; > + > + pll { clock-controller? Why can't the parent device be the clk provider and have #clock-cells? > + compatible =3D "mediatek,mt7621-clk"; > + #clock-cells =3D <1>; > + clock-output-names =3D "xtal", "cpu", "bus", > + "50m", "125m", "150m", > + "250m", "270m"; > + }; > + };