Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp62538ybm; Wed, 27 May 2020 19:22:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzNH3vOKq1/t7Nrsrs+IOozDfggAGuC7Xk90NRPYCxl/ak8xUfAmF6ZCkkn+qkiGcwPXaoM X-Received: by 2002:a50:d1c4:: with SMTP id i4mr915732edg.344.1590632555363; Wed, 27 May 2020 19:22:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590632555; cv=none; d=google.com; s=arc-20160816; b=m2F963JkwscQxmK/lSN1D/Am51Q6QPcVINNsD0+oix/D7cSPgSVEFqLuMS0MlNs7xQ oSWVcm6kCJ3FSiaqcpIrA871Fd50zjChtJiw3Ph3vyxwYIOfUOikDas0qAddN99LeE02 byYVpME1GnxhHiiFFuC7KAcoTiNDxWwU6gBNZ3rjCoaWZeqvbIGiYR8NRPLkKQ2/9JFl d9f/4MRLuT6UEOI0me80EX/YMBXq2goDuI+kC0KIrfvYTNlgAMLFV9z+fE+EdoFx3Rky AIDl9CP7jw6ernWtP9hYzCjANfd+nnuBC04bYfXIZeL4eanzuqx/PRXz9JSYkFKcu4+q HBeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=kltOMpJbIDHqgiVTyTHUiwKcDlpFvBKVIUzBWkM4zNU=; b=lIBeumg/dVNv5ALII3MoEaiWF6CWwCYZuO2arQ27WL9kYER6qn96Tmi8iSajRVvCLa XxbCB3+2615IpOcCEPqUZNN9Bc2fSNdqH0QnPsY0864e6/yZqDzNnLow1z1v3tlXk1Za 8+6dOZyzmq3Wkz91gymmjbnx+VgOuM0gPWLjOL1jHfMRv+352CkzwQ1GM5iiyvtcUlv/ DFF8+R8Ui7E+6JdwqzM9afTosDttaQQZTk07JeJ434jZQDzTXrP2OY1HCgodI1aHTqkd YUtMsaiiq4LIUueqSZspySesWlLffiEdC6+8/RVayhNN8ioYpb2Nhk0MCW8GhDUqg3b8 i5qQ== ARC-Authentication-Results: i=1; mx.google.com; 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 do5si3721518ejc.105.2020.05.27.19.22.12; Wed, 27 May 2020 19:22:35 -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; 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 S1726915AbgE1CS3 (ORCPT + 99 others); Wed, 27 May 2020 22:18:29 -0400 Received: from mail-il1-f196.google.com ([209.85.166.196]:34719 "EHLO mail-il1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725849AbgE1CS3 (ORCPT ); Wed, 27 May 2020 22:18:29 -0400 Received: by mail-il1-f196.google.com with SMTP id v11so8756644ilh.1; Wed, 27 May 2020 19:18:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=kltOMpJbIDHqgiVTyTHUiwKcDlpFvBKVIUzBWkM4zNU=; b=Yc+FSqPz2y5P64NVrrxsrchfcoqjaQFiSBZQQQb0IzPAYSEzzJ1K7jQx1hPky1S4JC oAwIWNi5GcjUbH4YtpOllys4SyA31HpgOAOg9qBPeFt/4xqHJ0TdvbgfbwKkVwgMS2VD MTJXRi1KyAMk39SSKcg/o09XC1AT+AeNp3CnJ8XsH9TefjK4KDdyrT99XB8cARCFLT8w XN4pNhbCukDEREJvag3fNVj4ix39YdanGgFM4y2BMd7SH+pMs/U/SccgWsMUZXrY7mzF v8Zhe1llY5fmDIX2XJN/WnbNdQJl2pKG4duIG39e38aRPXP0zZeUv680Eu7toVboiwI7 q4wQ== X-Gm-Message-State: AOAM531izkwrm/jLMsIf9ijFM0hveSrDHudFI24D9qQEJn5oD9q6qveU W/c1fVqTlaSDRqHsLL7JlA== X-Received: by 2002:a92:9f82:: with SMTP id z2mr950652ilk.59.1590632307912; Wed, 27 May 2020 19:18:27 -0700 (PDT) Received: from xps15 ([64.188.179.252]) by smtp.gmail.com with ESMTPSA id s71sm2536741ilc.32.2020.05.27.19.18.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 May 2020 19:18:27 -0700 (PDT) Received: (nullmailer pid 3229541 invoked by uid 1000); Thu, 28 May 2020 02:18:26 -0000 Date: Wed, 27 May 2020 20:18:26 -0600 From: Rob Herring To: Lars Povlsen Cc: SoC Team , Arnd Bergmann , Stephen Boyd , Linus Walleij , Steen Hegelund , Microchip Linux Driver Support , Olof Johansson , Michael Turquette , devicetree@vger.kernel.org, linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Alexandre Belloni Subject: Re: [PATCH 10/14] dt-bindings: clock: sparx5: Add Sparx5 SoC DPLL clock Message-ID: <20200528021826.GA3221035@bogus> References: <20200513125532.24585-1-lars.povlsen@microchip.com> <20200513125532.24585-11-lars.povlsen@microchip.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200513125532.24585-11-lars.povlsen@microchip.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 13, 2020 at 02:55:28PM +0200, Lars Povlsen wrote: > This add the DT bindings documentation for the Sparx5 SoC DPLL clock > > Reviewed-by: Alexandre Belloni > Signed-off-by: Lars Povlsen > --- > .../bindings/clock/microchip,sparx5-dpll.yaml | 46 +++++++++++++++++++ > 1 file changed, 46 insertions(+) > create mode 100644 Documentation/devicetree/bindings/clock/microchip,sparx5-dpll.yaml > > diff --git a/Documentation/devicetree/bindings/clock/microchip,sparx5-dpll.yaml b/Documentation/devicetree/bindings/clock/microchip,sparx5-dpll.yaml > new file mode 100644 > index 0000000000000..594007d8fc59a > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/microchip,sparx5-dpll.yaml > @@ -0,0 +1,46 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/clock/microchip,sparx5-dpll.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Microchip Sparx5 DPLL Clock > + > +maintainers: > + - Lars Povlsen > + > +description: | > + The Sparx5 DPLL clock controller generates and supplies clock to > + various peripherals within the SoC. > + > + This binding uses common clock bindings > + [1] Documentation/devicetree/bindings/clock/clock-bindings.txt > + > +properties: > + compatible: > + const: microchip,sparx5-dpll > + > + reg: > + items: > + - description: dpll registers For a single entry, just: maxItems: 1 > + > + '#clock-cells': > + const: 1 > + > +required: > + - compatible > + - reg > + - '#clock-cells' > + > +additionalProperties: false > + > +examples: > + # Clock provider for eMMC: > + - | > + clks: clks@61110000c { clock-controller@1110000c { > + compatible = "microchip,sparx5-dpll"; > + #clock-cells = <1>; > + reg = <0x1110000c 0x24>; Looks like this is a sub-block in some other h/w block. What's the parent device? That should be described and this should be part of it either as a single node or a child node. Without a complete view of what this block has I can't provide any guidance. Rob