[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170621180847.GA24175@amd>
Date: Wed, 21 Jun 2017 20:08:47 +0200
From: Pavel Machek <pavel@....cz>
To: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Benjamin Gaignard <benjamin.gaignard@...aro.org>,
Baruch Siach <baruch@...s.co.il>,
"patches@...nsource.wolfsonmicro.com"
<patches@...nsource.wolfsonmicro.com>,
Linus Walleij <linus.walleij@...aro.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
Thierry Reding <thierry.reding@...il.com>,
"x86@...nel.org" <x86@...nel.org>,
Jonathan Hunter <jonathanh@...dia.com>,
Chen-Yu Tsai <wens@...e.org>, Ingo Molnar <mingo@...hat.com>,
Sylvain Lemieux <slemieux.tyco@...il.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Len Brown <len.brown@...el.com>,
"linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>,
Jason Cooper <jason@...edaemon.net>,
"rtc-linux@...glegroups.com" <rtc-linux@...glegroups.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Hans Ulli Kroll <ulli.kroll@...glemail.com>,
"adi-buildroot-devel@...ts.sourceforge.net"
<adi-buildroot-devel@...ts.sourceforge.net>,
Vladimir Zapolskiy <vz@...ia.com>,
John Stultz <john.stultz@...aro.org>,
Gregory Clement <gregory.clement@...e-electrons.com>,
Michael Chan <michael.chan@...adcom.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Alessandro Zummo <a.zummo@...ertech.it>,
Barry Song <baohua@...nel.org>,
Support Opensource <Support.Opensource@...semi.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Steve Twiss <stwiss.opensource@...semi.com>,
Maxime Ripard <maxime.ripard@...e-electrons.com>
Subject: Re: [PATCH 00/51] rtc: stop using rtc deprecated functions
Hi!
> > > Or not, having an RTC set in the past is actually quite common. I'd find
> > > it weird to have a new device boot and be set to a date in the future.
> >
> > ...but still better than board stuck in the past, no?
> >
> > > 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.
> >
> > Well, you can still convert time from rtc to unix time, then do adjustment
> > there.
> >
>
> 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.
>
> Yes, I'm in the middle of the whole rework that allows that.
>
> 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.
>
> 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
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists