From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [PATCH 00/51] rtc: stop using rtc deprecated functions Date: Tue, 20 Jun 2017 15:26:20 +0200 Message-ID: <20170620132620.GA16881@amd> References: <1497951359-13334-1-git-send-email-benjamin.gaignard@linaro.org> <20170620100348.zh4ygvjjgnhxvmvl@piout.net> <20170620121011.GA13221@amd> <20170620122400.sm7qqvwyj6cuzarw@piout.net> Reply-To: rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Cc: Benjamin Gaignard , linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org, adi-buildroot-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Alessandro Zummo , Gregory Clement , Ingo Molnar , Jason Cooper , John Stultz , linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Linus Walleij , Michael Chan , netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org, Sebastian Hesselbarth , Support Opensource , Thomas Gleixner , x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, Baruch Siach , Hans Ulli Kroll , Vladimir Zapolskiy , Sylvain Lemieux , Barry Song Return-path: Sender: rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: <20170620122400.sm7qqvwyj6cuzarw-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org> List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , List-Id: netdev.vger.kernel.org --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline On Tue 2017-06-20 14:24:00, Alexandre Belloni wrote: > On 20/06/2017 at 14:10:11 +0200, Pavel Machek wrote: > > On Tue 2017-06-20 12:03:48, Alexandre Belloni wrote: > > > On 20/06/2017 at 11:35:08 +0200, Benjamin Gaignard wrote: > > > > rtc_time_to_tm() and rtc_tm_to_time() are deprecated because they > > > > rely on 32bits variables and that will make rtc break in y2038/2016. > > > > > > Please don't, because this hide the fact that the hardware will not > > > handle dates in y2038 anyway and as pointed by Russell a few month ago, > > > rtc_time_to_tm will be able to catch it but the 64 bit version will > > > silently ignore it. > > > > Reference? Because rtc on PCs stores date in binary coded decimal, so > > it is likely to break in 2100, not 2038... > > I'm not saying it should be done but clearly, that is not the correct > thing to do for RTCs that are using a single 32 bits register to store > the time. > You give one example, I can give you three: armada38x, at91sam9, > at32ap700x and that just in the beginning of the series. I wanted reference to Russell's mail. > And yes, on PC, they will break in 2100, other in 2106, some in 2070. > I've delayed the tree wide patching until I manage to finish reworking > the infrastructure needed to handle the limits of the RTCs. Kernel does not know if it has working RTC or not, so it should use 64bit variables. Merging this -- does not hide anything. Yes, some drivers still may have problems -- so we fix the drivers. You said: > > > rtc_time_to_tm will be able to catch it but the 64 bit will > > > silently ignore it. If that's the case, we may need 64bit version to be smarter.. but we'll still need 64bit variables in the kernel. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- You received this message because you are subscribed to "rtc-linux". Membership options at http://groups.google.com/group/rtc-linux . Please read http://groups.google.com/group/rtc-linux/web/checklist before submitting a driver. --- You received this message because you are subscribed to the Google Groups "rtc-linux" group. To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit https://groups.google.com/d/optout. --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAllJInwACgkQMOfwapXb+vKvOACfa+kGFBRxWhkRpGKLgcPlEMXc Xp4An1BROF4v4jttS9yXrXm9FyxGRyLs =CY2S -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--