Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp1007408pxb; Tue, 17 Aug 2021 01:15:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw5gskR6A+SadQ9e880U97PBlu36VIMgsfERTIj5fihxXNWGAzDUxWSEFNjWPFFHPoLEk0O X-Received: by 2002:a17:906:32d9:: with SMTP id k25mr2625896ejk.290.1629188131801; Tue, 17 Aug 2021 01:15:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1629188131; cv=none; d=google.com; s=arc-20160816; b=kgnqCDfWuJrD5OifNZPuaNV+55KDuMS4iUqoEghBaqPPbJIeHrCMZwTwS1vMGNRI1+ UAUqE3GI1gCJzK2TRKXdMw+CfxDg3V9LOsShqyIw6iNxyVHNzfnXuTyX+WfqdiVPemLX SEYNwz+5uz6c5NmL5YW55zkRvFQmN1DGboXvI+G0Hq3M99Bz54r6azn6e2zkyIL9UAWi wnAz4eX9GPKAs1GEffFq4vAbH4dn9qEicXUdBaQsIzOYMtcNDREJSCdLNB9h6KBVVzx4 pqHJb2Fqy4Ipntsi1WPF3dG36w0rEAiFyrUAXwvRAHme0zUHoEc6D3R+HJ+M2PXua1ZW qgtg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=PB9sz0PDSuD6l0sNONr1Wbrm8vx4svBySpJ8zzVSjhA=; b=Oqi8cjV+ZgzJA4+eUKal93fs30Qc9skQ0h0JCbQMu5pg2QfXChtGjQ5CDYpTlg52yF uGVBL+KviReYzvgOyWS6wSR1X46Bc8R133AP/56fMERlKfL29SAlGksnH34LzixigoD2 IaeNRy8LRnVcILx3FFUi9qlJPH+jiZViCM5kqF7uUlpVnGAStBlB9Qd6VK1g5vIvD56Q WhFyQ7IUpTuFNHLqinXkIKiA3DBE/28DIPu0KQxtv0/slDR7lLM4pjEM2Fdfo3HpWX+m 6plMIwDyXjvgqLLKsYu+wcW4XWcN4D68fH2TIoe6pTJhCkRPUv3yQLZX9zUkg1OGG7cM NVzw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hq37si1771950ejc.56.2021.08.17.01.15.07; Tue, 17 Aug 2021 01:15:31 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239009AbhHQINw (ORCPT + 99 others); Tue, 17 Aug 2021 04:13:52 -0400 Received: from relay9-d.mail.gandi.net ([217.70.183.199]:40811 "EHLO relay9-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238605AbhHQINt (ORCPT ); Tue, 17 Aug 2021 04:13:49 -0400 Received: (Authenticated sender: alexandre.belloni@bootlin.com) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 73E60FF80B; Tue, 17 Aug 2021 08:13:11 +0000 (UTC) Date: Tue, 17 Aug 2021 10:13:11 +0200 From: Alexandre Belloni To: Maxime Ripard 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: 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210817073810.7stuzrppyjf4spab@gilmour> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17/08/2021 09:38:10+0200, Maxime Ripard wrote: > > > It's not entirely clear to me what those clocks are about though. If 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 and > > > the losc. What are the 3 you're talking about?] > > > > I see three: the raw SYSTEM "CLK32K_LOSC", the RTC input + debounce > > clock (/32), and the multiplexed PAD. > > 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 > Shouldn't they be exposed to be able to use assigned-clock? -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com