Received-SPF: pass (google.com: domain of linux-kernel+bounces-210932-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Tue, 11 Jun 2024 22:06:39 -0700
From: Richard Cochran <richardcochran@gmail.com>
To: =?iso-8859-1?B?Q3Pza+FzLA==?= Bence <csokas.bence@prolan.hu>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
	=?iso-8859-1?Q?Szentendrei=2C_Tam=E1s?= <szentendrei.tamas@prolan.hu>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	Miroslav Lichvar <mlichvar@redhat.com>
Subject: Re: [RFC PATCH v2] rtc: pcf2127: Add PPS capability through Seconds
 Interrupt
Message-ID: <Zmks31shpsnoLQ3k@hoboy.vegasvil.org>
References: <20240611150458.684349-1-csokas.bence@prolan.hu>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20240611150458.684349-1-csokas.bence@prolan.hu>


(adding Miroslav onto CC)

On Tue, Jun 11, 2024 at 05:04:57PM +0200, Cs?k?s, Bence wrote:

> PCF2127/29/31 is capable of generating an interrupt on every
> second (SI) or minute (MI) change. It signals this through
> the Minute/Second Flag (MSF) as well, which needs to be cleared.

This is a RFC, and my comment is that a PPS from an RTC is not useful
to the Linux kernel.

The kernel only uses the RTC to boot strap the wall clock to some
approximate phase.

After that, Linux either continues with a free running clock, or it
synchronizes to a global time source via NTP.  In the latter case,
Linux will write the NTP time back into the RTC.

So I can't see how the RTC's PPS provides any benefit.

Thanks,
Richard