Received: by 2002:a25:ef43:0:0:0:0:0 with SMTP id w3csp569990ybm; Fri, 29 May 2020 07:07:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxYTm2PXpT2zLYw9bZcqUcv6NA+lAxN7kUUY3arLG/frClj5+dMdMKVhZ0z8N+4AA7WQGKq X-Received: by 2002:a17:906:f913:: with SMTP id lc19mr2134920ejb.286.1590761250423; Fri, 29 May 2020 07:07:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590761250; cv=none; d=google.com; s=arc-20160816; b=TIz4K1AcUBsk4F17E2SW+jpiUf0rFrRMT1xJDRzfGQsGraDsK2RdYTq5hmjHce2XBl fndqsBWxaKLwo1xL4VO8IxDDdQwz0ip8x0Ly5WaHtJFjOGR02ILHl3L4vjQGz1yJAW1t 8DPP9a2hNQr6avNH5BPnHeaRr/LwHCVOTG062YspYlAnQiYR5PQTyvZX93P/Ybx0v1Aj PY+C4vlFcMJfVo+3/WajsWD2DPExT6kw/ebS/jd2zSp20XyQMP/m2rCcmro8Xle2aOl9 Xrcbb9OuJ4yhxA7XpXm8avohG7zAConlmtbBJmkeRwg1MqfBLsfxflAgiL5H1R43Uhdo l5tA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:in-reply-to :subject:cc:to:from:references:ironport-sdr:dkim-signature; bh=bdFQtPeGLVdVw29jRyvh30Vz9s3LKp//86LhxxrRDBc=; b=igai8bePar4Ve0Qq9k2d11/4RMgiu7TqosNU4k+U2eZ2nHJfSFL3vIQFKATCQg66EF AbqvdltUWf2J2iHN2yZUdz0WxPSdjdQ9C473b6x+8q7ijingCPrAG3KfrpfoES7+QCTo FYia8OmH1abBlyDsEfEaptnbKbP2dq/QQFZeaDtr8uxez67lQno/H8j+jfGYIaExKBZK /DY99Jp9XxuYkFQlY179MXxg/vj4iFDUNaEIQ4DapNvool+jzch79EZkHAXmDpjtRpcE aWOEwDu0w7gD0iYkj2onWZ04e2w+dZCggjvNYjUpE20sMxes+voCvjc87IwMlJTPH3JX LM4A== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@microchip.com header.s=mchp header.b=URWVUOZq; 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=fail (p=NONE sp=NONE dis=NONE) header.from=microchip.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r1si5737718eji.355.2020.05.29.07.06.59; Fri, 29 May 2020 07:07:30 -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=fail header.i=@microchip.com header.s=mchp header.b=URWVUOZq; 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=fail (p=NONE sp=NONE dis=NONE) header.from=microchip.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727049AbgE2OEj (ORCPT + 99 others); Fri, 29 May 2020 10:04:39 -0400 Received: from esa2.microchip.iphmx.com ([68.232.149.84]:8703 "EHLO esa2.microchip.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726898AbgE2OEi (ORCPT ); Fri, 29 May 2020 10:04:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1590761078; x=1622297078; h=references:from:to:cc:subject:in-reply-to:date: message-id:mime-version; bh=sAGWaqia1JF0ryeRDXVzFPeaOltQyl1NGW+wvlqDi/E=; b=URWVUOZqjoRzONnnH/q05xZjn/+tJ5OFy7pO4A+Xk04NClzFwzEmk4o0 oCWnUXvIo8Wr+e7NX4gZd3ZxcXRAD91ziqCgppCunRr+bfiTFYkbpxvnr yRJPrOPmoTdwXF89Mps9VhpjPZi0eYEoLE9KGjR2p9lCx2JEm2MTt6Kpi 1dNTJhotEvcLn4RhZUA0Q1SRj3UuAhNBR2cur/hAD4kAbfpqiyUtRjhSV 8GYqQJw47Wu3LzpeGDd1dAwwUKdE5YkCycXSX2rgERb7R6YAmHsEcSCIb h++3ncSfc75VYDZJ0DWPYwEwcmUVFsLrokUlKsOY7EfsbW+oN3GThFvoF Q==; IronPort-SDR: xpzqGjpyykV5Ih2wHq02FXx0AqsGr/X8yLZnO6sUmywda4kivT2QCL6RfgUMu/+Mo7l9o/BFdz eE5+qVqCa2lVZL5SDnAKAB9ZWgFApKonr+D6Tn6LKVvhGj0EMsHHtXKOQO4hBQk4pAhpJdC3/T oSeo8ia8aXe0OQprk4ftk7b2Q5mkFCr7fBh1lEuOKj3veab6yAchm6/zODKBhgT3fNGupVkkZX NyNMfNrLKlKmDbgry41qbg+dHhM/zAN07j+tX4W+FU0kPMqY2yjRRAJZ5m8BXBRwZSwDb8/s93 CCI= X-IronPort-AV: E=Sophos;i="5.73,448,1583218800"; d="scan'208";a="76764161" Received: from smtpout.microchip.com (HELO email.microchip.com) ([198.175.253.82]) by esa2.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 29 May 2020 07:04:37 -0700 Received: from chn-vm-ex01.mchp-main.com (10.10.85.143) by chn-vm-ex02.mchp-main.com (10.10.85.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Fri, 29 May 2020 07:04:40 -0700 Received: from soft-dev15.microsemi.net.microchip.com (10.10.115.15) by chn-vm-ex01.mchp-main.com (10.10.85.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5 via Frontend Transport; Fri, 29 May 2020 07:04:25 -0700 References: <20200513125532.24585-1-lars.povlsen@microchip.com> <20200513125532.24585-11-lars.povlsen@microchip.com> <159054759981.88029.2630901114208720574@swboyd.mtv.corp.google.com> From: Lars Povlsen To: Stephen Boyd CC: Arnd Bergmann , Linus Walleij , Rob Herring , SoC Team , Lars Povlsen , Steen Hegelund , Microchip Linux Driver Support , Olof Johansson , Michael Turquette , , , , , , Alexandre Belloni Subject: Re: [PATCH 10/14] dt-bindings: clock: sparx5: Add Sparx5 SoC DPLL clock In-Reply-To: <159054759981.88029.2630901114208720574@swboyd.mtv.corp.google.com> Date: Fri, 29 May 2020 16:04:32 +0200 Message-ID: <87lflaq1lb.fsf@soft-dev15.microsemi.net> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Stephen Boyd writes: > Quoting Lars Povlsen (2020-05-13 05:55:28) >> 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 > > I don't think we need this sentence. Please drop it. OK. (Assuming the "This binding ..." part). > >> + >> +properties: >> + compatible: >> + const: microchip,sparx5-dpll >> + >> + reg: >> + items: >> + - description: dpll registers >> + >> + '#clock-cells': >> + const: 1 >> + >> +required: >> + - compatible >> + - reg >> + - '#clock-cells' >> + >> +additionalProperties: false >> + >> +examples: >> + # Clock provider for eMMC: >> + - | >> + clks: clks@61110000c { > > Node name should be clock-controller@61110000c Ok. > >> + compatible = "microchip,sparx5-dpll"; >> + #clock-cells = <1>; >> + reg = <0x1110000c 0x24>; > > Does it consume any clks itself? I'd expect to see some sort of 'clocks' > property in this node. > >> + }; I changed the driver to use a fixed-rate input clock, replacing the BASE_CLOCK define(s). Additionally, I made the ahb_clock into fixed-factor clock using the A53 cpu clock as a base. So I updated the example and added 'clocks' to the schema. I will send you a new series shortly. Thank you for the comments. -- Lars Povlsen, Microchip