From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9D360C433EF for ; Fri, 3 Sep 2021 14:52:12 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 68CBC610CC for ; Fri, 3 Sep 2021 14:52:12 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 68CBC610CC Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=cerno.tech Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date :Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=fu5VR8J40zzLUS82fCLxe0lN6QwC6318u3R8CkHg8lM=; b=SvoH/vSdmRFXFq6xeFny2sQSBt 51CLKaz45vmeqIen2nnrf8rW9D3qPpolU1gPn7e8O3ItjY2s8nomlAlS+iXHdykJLLozEFPzymYDE BPEiHtjfyPWGlHCjSlf2uwjER9svhMWir2SPP9UBPmwzw/HvEA1s7qcf7UrBwLVPyQDpdFK7LfdHR E+R4FFgPS5nL+L30P4h3PB/cM/KpgvGmQIkxJBL2OFuwTWl5vOmsRdpI02myNvv1SRJ7G++/e1I3f Qs6Y6meHkIS3pxN2/e5zzkMr1DnZCdjQW4KywMrfKKgRG8ZadOrl0EX29+xr0g+ryoQDD/E6lNpcf 07fGxKHQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mMAWN-00CEQD-PJ; Fri, 03 Sep 2021 14:50:23 +0000 Received: from new4-smtp.messagingengine.com ([66.111.4.230]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mMAWJ-00CEPg-J3 for linux-arm-kernel@lists.infradead.org; Fri, 03 Sep 2021 14:50:21 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailnew.nyi.internal (Postfix) with ESMTP id E71F2580ACC; Fri, 3 Sep 2021 10:50:17 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 03 Sep 2021 10:50:17 -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=1+UNQ4mZYAX+yX8v1shjgWGw45M YrAYp1gT+fM1QCoA=; b=rbAtD4PN386W+BxKH5SsXETJ8QBRSvDEB/etHH6iVsH rho+11BM8EWl2GPPyZK37ZBlo3ggqWddwcIVWNb8dIZ3yvDK8jqjqH4pZRbdZDfH P6wWHVADgQfiJtfB7Pmd6DFMTViWHtzox3yGr3i+eKXAoFHDlYp0nRqgBOEOYrn+ DG7bBFY2Kes7PGLKh/amjbpYSdVJ3/Yr4yGglaTgQwBND1EA+Y8yKbglnelM4BRr yRYl6hj51WOhUkT4CMBn2OSoi/yHXdcLNXzLTS8MnSxXY6Mrv4p7ZyuzWJ1wpmYu AKo/vSy5CXf5mczam8ZDyXLpn9m34vBp6h1OM4z24Zw== 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=1+UNQ4 mZYAX+yX8v1shjgWGw45MYrAYp1gT+fM1QCoA=; b=slWUYSruonY0xKUWmiFC1E SD5CqLQsNw2WabtJxTif87cYvsQ/t51pSazn2rgRlj7xOGQOMHVmUZ+NV3FQI5YQ HMjTkG9LkuKo2+wZP+BifP5J4T+1KU7sLfLO2xHs+D7CedujIdeb+rHSyqnxiDD5 obAq9f+Q7UmnT0waXDCNWbgR0KgzgendP17NwrEO66nTMkrJOBbOxrWQq0bC9Tbg O75IrnKe0KJCAuHk6HW2JyVKvO/qkpjplTUYoe35ydlSmu3CzXI7iSU8CAZL3YOn tB6Tad7auHJEqBd2Bz+CIWhF7EwZAhVsUoTehhbDIZsaxLYrcwCabTlvZRsUjliw == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddruddvjedgjeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpeforgigihhm vgcutfhiphgrrhguuceomhgrgihimhgvsegtvghrnhhordhtvggthheqnecuggftrfgrth htvghrnhepleekgeehhfdutdeljefgleejffehfffgieejhffgueefhfdtveetgeehieeh gedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmh grgihimhgvsegtvghrnhhordhtvggthh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 3 Sep 2021 10:50:15 -0400 (EDT) Date: Fri, 3 Sep 2021 16:50:13 +0200 From: Maxime Ripard To: Samuel Holland Cc: Chen-Yu Tsai , Jernej Skrabec , Rob Herring , Michael Turquette , Stephen Boyd , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org, linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH 0/7] clk: sunxi-ng: Add a RTC CCU driver Message-ID: <20210903145013.hn6dv7lfyvfys374@gilmour> References: <20210901053951.60952-1-samuel@sholland.org> MIME-Version: 1.0 In-Reply-To: <20210901053951.60952-1-samuel@sholland.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210903_075019_925335_952EA49E X-CRM114-Status: GOOD ( 28.38 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1682328348114628768==" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org --===============1682328348114628768== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="aqyjfro3lmncra3z" Content-Disposition: inline --aqyjfro3lmncra3z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Wed, Sep 01, 2021 at 12:39:44AM -0500, Samuel Holland wrote: > This patch series adds a CCU driver for the RTC in the H616 and R329. > The extra patches at the end of this series show how it would be > explanded to additional hardware variants. >=20 > The driver is intended to support the existing binding used for the H6, > but also an updated binding which includes all RTC input clocks. I do > not know how to best represent that binding -- that is a major reason > why this series is an RFC. >=20 > A future patch series could add functionality to the driver to manage > IOSC calibration at boot and during suspend/resume. >=20 > It may be possible to support all of these hardware variants in the > existing RTC clock driver and avoid some duplicate code, but I'm > concerned about the complexity there, without any of the CCU > abstraction. >=20 > This series is currently based on top of the other series I just sent > (clk: sunxi-ng: Lifetime fixes and module support), but I can rebase it > elsewhere. I'm generally ok with this, it makes sense to move it to sunxi-ng, especially with that other series of yours. My main concern about this is the split driver approach. We used to have that before in the RTC too, but it was mostly due to the early clock requirements. With your previous work, that requirement is not there anymore and we can just register it as a device just like the other clock providers. And since we can register all those clocks at device probe time, we don't really need to split the driver in two (and especially in two different places). The only obstacle to this after your previous series is that we don't have of_sunxi_ccu_probe / devm_sunxi_ccu_probe functions public, but that can easily be fixed by moving their definition to include/linux/clk/sunxi-ng.h Maxime --aqyjfro3lmncra3z Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRcEzekXsqa64kGDp7j7w1vZxhRxQUCYTI2JQAKCRDj7w1vZxhR xULeAP9F874xM3NzdYuwFLC9z8BzcFNMMzlOjOqwTFV7P7pHxAD/Vzu6odW0IVrM Ulo17sA/rKg+2hzkHxw6WkxA9mXhNgs= =TM12 -----END PGP SIGNATURE----- --aqyjfro3lmncra3z-- --===============1682328348114628768== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel --===============1682328348114628768==--