From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B39342FAE for ; Thu, 19 Aug 2021 07:56:35 +0000 (UTC) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailnew.nyi.internal (Postfix) with ESMTP id AFC4D580B35; Thu, 19 Aug 2021 03:56:34 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Thu, 19 Aug 2021 03:56:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cerno.tech; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=0eV2e4Kt4bNdKmcOimi64QwDPOM ArP7lXcHLaxrh8n4=; b=yB3Iee0lCnm04lXOMQEZk+JX2ueSLYcimEiTt4Xrxkk 1U+OewzOvufFTmoC4arfSdYIys9U6enZj7Xz/OkcIMUxGlz9GojIkPJTi0mxNH0f z2u14xUK+M47fvnVUkDggFNpyVbuiS8eXxfgBfOaWGuTb3AHnrExDmtV5FyzkiYC strWxxxtSyQBpheFn580ZjdKYmiTojb5TURqh9iKjfbxMQ1gxcLt109y6c5NH48V egiH1NGht9rbjPMFPVayW1IyOGaM5i3akxo/Ln5uR6HNuCP7Jj8d1k2dDl3hfcde Op5Lb3iMLt9+2I6zLf/lJPd5ljl59P4t/K8OzynRu7g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=0eV2e4 Kt4bNdKmcOimi64QwDPOMArP7lXcHLaxrh8n4=; b=vHDw1246WMq7l281GJdEU/ pssk45Uw94P1LqAelquOrLRrAWaPKElgJOtXGvmFpmE3me3E7my/JDQaGuUIwT/b s8Nr9xiPdumM0Mb+QbR2Blk0L/XdG8SyquDFZcw6WnqyQ1xcc2+tl8DbSakLJiu5 XQ9rAtgtZYUvZlzoayu9eMTOGPdaHYltQ3hCvX6alkF5mmTFrtx1gk41vhVCQdJ5 gPDcFWvEID1906UtZx2lsnuIkn3A70HQe3MvvkHCCkceiZtJpEkeWEQxXdmu96Lp fwtEZzWSE8PQ9B5Bi/o25cxdeMZknlIf9LoEG8QlGc+rzUqXZXkmg42ccvcQ+Qag == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrleeigdduvdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpeforgigihhm vgcutfhiphgrrhguuceomhgrgihimhgvsegtvghrnhhordhtvggthheqnecuggftrfgrth htvghrnhepleekgeehhfdutdeljefgleejffehfffgieejhffgueefhfdtveetgeehieeh gedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmh grgihimhgvsegtvghrnhhordhtvggthh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 19 Aug 2021 03:56:31 -0400 (EDT) Date: Thu, 19 Aug 2021 09:56:30 +0200 From: Maxime Ripard To: Alexandre Belloni Cc: Andre Przywara , Chen-Yu Tsai , Jernej Skrabec , Rob Herring , Icenowy Zheng , Samuel Holland , linux-arm-kernel@lists.infradead.org, linux-sunxi@googlegroups.com, linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org, Ondrej Jirman , devicetree@vger.kernel.org, Alessandro Zummo , linux-rtc@vger.kernel.org Subject: Re: [PATCH v8 02/11] dt-bindings: rtc: sun6i: Add H616 compatible string Message-ID: <20210819075630.upliivqux4dsohzd@gilmour> References: <20210723153838.6785-1-andre.przywara@arm.com> <20210723153838.6785-3-andre.przywara@arm.com> <20210726144137.6dauuxdssu7yszox@gilmour> <20210802013938.29fa18ed@slackpad.fritz.box> <20210817073810.7stuzrppyjf4spab@gilmour> Precedence: bulk X-Mailing-List: linux-sunxi@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3hmvsdooooerg7xw" Content-Disposition: inline In-Reply-To: --3hmvsdooooerg7xw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Salut Alex, On Tue, Aug 17, 2021 at 10:13:11AM +0200, Alexandre Belloni wrote: > On 17/08/2021 09:38:10+0200, Maxime Ripard wrote: > > > > It's not entirely clear to me what those clocks are about though. I= f we > > > > look at the clock output in the user manual, it looks like there's = only > > > > two clocks that are actually being output: the 32k "fanout" clock a= nd > > > > the losc. What are the 3 you're talking about?] > > >=20 > > > I see three: the raw SYSTEM "CLK32K_LOSC", the RTC input + debounce > > > clock (/32), and the multiplexed PAD. > >=20 > > But the input and debounce clock is only for the RTC itself right? So it > > should be local to the driver and doesn't need to be made available to > > the other drivers > >=20 >=20 > Shouldn't they be exposed to be able to use assigned-clock? I'm not sure we would even need that? If it's an internal clock to the RTC, then we probably won't ever need to change it from the device tree? Maxime --3hmvsdooooerg7xw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCYR4OrgAKCRDj7w1vZxhR xcfHAQD57em6KsLSV7qIaoRsDHdIufLm3Kb3PQEB8BalFLnh9wEAriRxL2uxqKaW zsgaYApsMZjAkwzrGtWjndk9bGNnfQw= =cvW0 -----END PGP SIGNATURE----- --3hmvsdooooerg7xw--