Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp6700217imu; Mon, 3 Dec 2018 01:07:20 -0800 (PST) X-Google-Smtp-Source: AFSGD/WRZf+8pVp2D/LYprEVW9IYqPEvYD3kX9qD8ddeHQZ5+TgaFZ7AGojmnoA4w/GweRoUhsBP X-Received: by 2002:a63:5664:: with SMTP id g36mr12457040pgm.313.1543828040821; Mon, 03 Dec 2018 01:07:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543828040; cv=none; d=google.com; s=arc-20160816; b=toA0uG5JknEZFHb/+2BR3lysI7aMyn4YLbnNR5zglDP26WQb0BZ630dvcRgnxJw+Eq y4YSgAMTfPHUCmr26nj+8ssorB8/fxxjJNcIlnFEP1X5EdV6x0oKH4U/XoWSMauG0oNL xhBIcKddViaTYFIIElBwzceCN2ULAz5FSKChnQMju6Z9S5GxG2lmnyznWalwQ/XEozgW 6j+n6Y51IhBaGT4E5fZqaasaKzcWqoCS8u7nN5vxukRs5fOCsWFkCT6nSylO506EZ8NG QALzTLQdI3bfvC5fiNTvpLfPUTzO64bR2XdAvz+T/MCXKb1zBuvA9aNTu9fhYx7XstnZ sa1A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=XqnJloKVI1yzVjmsSMK5Z6CT3kBwXZlAjx/A8O6FE3s=; b=QevJEsK83jUt7me1ePDPDjDRhJCbWNRyPQX4x64/1fVlmzndPZ0FBui/meZqUhvR7+ 9Xcz7tzrrLRQI5rGMjm1tmdtv0z7cUUkD0jUnDSoyG2k/wrvWdPybwr1LdlarwNpnO9E xCcETnBXS96DCalSAh9KYn6shlTkqQ2khPFUn42kui65JYmLne00AkoikCVoSdRh8GuI HrjOfea119ja8yasB8SYKxfZ155oK48FHjT3OWXFb5NL3+3pLyWXByKWce1kYaZdEj5P k9re2KhcRo1+mAy4XZKfMZvcFdpIAEuDIYsuIZfp7utX4tQ8SnTqqEFkIU2GIBy0tgpD CYIA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l30si2798778plg.113.2018.12.03.01.07.06; Mon, 03 Dec 2018 01:07:20 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725919AbeLCJGj (ORCPT + 99 others); Mon, 3 Dec 2018 04:06:39 -0500 Received: from mail.bootlin.com ([62.4.15.54]:52716 "EHLO mail.bootlin.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725849AbeLCJGj (ORCPT ); Mon, 3 Dec 2018 04:06:39 -0500 Received: by mail.bootlin.com (Postfix, from userid 110) id 3623220787; Mon, 3 Dec 2018 10:06:28 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.bootlin.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT, URIBL_BLOCKED shortcircuit=ham autolearn=disabled version=3.4.2 Received: from localhost (aaubervilliers-681-1-63-158.w90-88.abo.wanadoo.fr [90.88.18.158]) by mail.bootlin.com (Postfix) with ESMTPSA id EEA002071D; Mon, 3 Dec 2018 10:06:17 +0100 (CET) Date: Mon, 3 Dec 2018 10:06:18 +0100 From: Maxime Ripard To: Chen-Yu Tsai Cc: alexandre.belloni@bootlin.com, Alessandro Zummo , Mike Turquette , Stephen Boyd , Rob Herring , Mark Rutland , linux-arm-kernel , linux-rtc@vger.kernel.org, linux-clk , devicetree , linux-kernel , linux-sunxi@googlegroups.com Subject: Re: [PATCH 04/15] dt-bindings: rtc: sun6i-rtc: Export internal RC oscillator Message-ID: <20181203090618.u4bi3owfpk2kcqik@flea> References: <20181128093013.24442-1-wens@csie.org> <20181128093013.24442-5-wens@csie.org> <20181128103219.b625lttcgoluhgz5@flea> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="krs5icnvo4odeegk" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --krs5icnvo4odeegk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 28, 2018 at 07:18:26PM +0800, Chen-Yu Tsai wrote: > On Wed, Nov 28, 2018 at 6:33 PM Maxime Ripard = wrote: > > > > On Wed, Nov 28, 2018 at 05:30:01PM +0800, Chen-Yu Tsai wrote: > > > Experiments showed that on at least the H3/H5/A64 the RTC's internal > > > oscillator also feeds the CPUS mux in the PRCM. > > > > > > Export this clock through the device tree, instead of having to use > > > a dummy fixed-clock device node, for the PRCM to consume. This will > > > properly describe the relationship between the clocks. > > > > > > Signed-off-by: Chen-Yu Tsai > > > --- > > > Documentation/devicetree/bindings/rtc/sun6i-rtc.txt | 3 ++- > > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > > > diff --git a/Documentation/devicetree/bindings/rtc/sun6i-rtc.txt b/Do= cumentation/devicetree/bindings/rtc/sun6i-rtc.txt > > > index 78c4fb472eb7..1bd37faadecb 100644 > > > --- a/Documentation/devicetree/bindings/rtc/sun6i-rtc.txt > > > +++ b/Documentation/devicetree/bindings/rtc/sun6i-rtc.txt > > > @@ -24,7 +24,7 @@ Required properties: > > > > > > Required properties for new device trees > > > - clocks : phandle to the 32kHz external oscillator > > > -- clock-output-names : names of the two clock outputs. See below. > > > +- clock-output-names : names of the three clock outputs. See below. > > > - #clock-cells : must be equal to 1. > > > > > > The RTC provides the following clocks at the given indices: > > > @@ -32,6 +32,7 @@ The RTC provides the following clocks at the given = indices: > > > - 1: LOSC external output, known as X32KFOUT in the datasheet. > > > This clock is not available on the A31 and is deprecated for old > > > device trees still using the "allwinner,sun6i-a31-rtc" compatib= le. > > > +- 2: InternalOSC, or internal RC oscillator > > > > It seems to be required only for a few RTC though (H3, H5 and R40?) >=20 > IMO there's no harm in exporting it for all SoCs. I still don't know > if it's needed for the A31 either. And we don't have documents for the > PRCM stuff for any of the SoCs involved. I'm still a bit worried about this, since that means that we can't ever remove it from the DT interface, even though we find out it might cause some issues in the future. If we don't really have a need for it right now, I'd prefer not to expose it. Maxime --=20 Maxime Ripard, Bootlin Embedded Linux and Kernel engineering https://bootlin.com --krs5icnvo4odeegk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCXATyCgAKCRDj7w1vZxhR xTq/AP9WIRb7HtqNFrFkdfV6uGu037o83NPO7KzWey4u31t85QEAvW7U3/PGul6i mu4yDZZYaKjr9keZ6pW1XNH0scK/MwY= =nsv4 -----END PGP SIGNATURE----- --krs5icnvo4odeegk--