Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752925AbdFUSIx (ORCPT ); Wed, 21 Jun 2017 14:08:53 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:43459 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751174AbdFUSIv (ORCPT ); Wed, 21 Jun 2017 14:08:51 -0400 Date: Wed, 21 Jun 2017 20:08:47 +0200 From: Pavel Machek To: Alexandre Belloni Cc: Thomas Gleixner , Russell King - ARM Linux , Benjamin Gaignard , Baruch Siach , "patches@opensource.wolfsonmicro.com" , Linus Walleij , "linux-tegra@vger.kernel.org" , Thierry Reding , "x86@kernel.org" , Jonathan Hunter , Chen-Yu Tsai , Ingo Molnar , Sylvain Lemieux , Sebastian Hesselbarth , Len Brown , "linaro-kernel@lists.linaro.org" , Jason Cooper , "rtc-linux@googlegroups.com" , "linux-pm@vger.kernel.org" , Hans Ulli Kroll , "adi-buildroot-devel@lists.sourceforge.net" , Vladimir Zapolskiy , John Stultz , Gregory Clement , Michael Chan , "linux-arm-kernel@lists.infradead.org" , Alessandro Zummo , Barry Song , Support Opensource , "netdev@vger.kernel.org" , "Rafael J. Wysocki" , "linux-kernel@vger.kernel.org" , Steve Twiss , Maxime Ripard Subject: Re: [PATCH 00/51] rtc: stop using rtc deprecated functions Message-ID: <20170621180847.GA24175@amd> References: <20170620213507.urobmtg34vzubrdq@piout.net> <20170621075152.GA15996@amd> <20170621083907.y3gadsmsoufa5niv@piout.net> <20170621063443.GA4862@localhost> <20170621123535.b5fvwlydfhnhuqll@piout.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA" Content-Disposition: inline In-Reply-To: <20170621123535.b5fvwlydfhnhuqll@piout.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2232 Lines: 67 --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > > Or not, having an RTC set in the past is actually quite common. I'd f= ind > > > it weird to have a new device boot and be set to a date in the future. > >=20 > > ...but still better than board stuck in the past, no? > >=20 > > > Also note that the threshold or offset thing may seem like a good idea > > > but fails with many RTCs because of how they handle leap years. > >=20 > > Well, you can still convert time from rtc to unix time, then do adjustm= ent > > there. > >=20 >=20 > You can only if your machine is running when that happens. If that is > not the case, then you lost and your time is not correct anymore. I don't see why that should be a case... as long as you know what RTC does in event of overflow, and it is not something completely crazy. > > Anyway, I guess it would be cool for rtc drivers to annotate what limits > > underlying storage has to the common code, so that we can do fixups once > > per class, not once per driver. >=20 > Yes, I'm in the middle of the whole rework that allows that. >=20 > I don't understand the sudden urgency of fixing that and the amount of > bikeshedding, seeing that the closest cutoff date is actually 31st of > december 2069 in the rtc subsystem and that anyway the current 32bit > userspace will explode in february 2038. >=20 > My plan from the beginning was to have something for the next stable. I > know nobody can read my mind but again, I don't think there is currently > any urgency to change anything. Yes, mind reading is a problem. I can only read minds of ferungulates, and only if they are physicaly near me :-). Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --W/nzBZO5zC0uMSeA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAllKti8ACgkQMOfwapXb+vIiwQCfQ7QxR1SKvoHK+zdLpdef2SvB 0tQAnjy9uAFNWGhOZqLuDSMvdZ5dh9DC =n6oF -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA--