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: Wed, 21 Jun 2017 20:08:47 +0200 Message-ID: <20170621180847.GA24175@amd> References: <20170620213507.urobmtg34vzubrdq@piout.net> <20170621075152.GA15996@amd> <20170621083907.y3gadsmsoufa5niv@piout.net> <20170621063443.GA4862@localhost> <20170621123535.b5fvwlydfhnhuqll@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="W/nzBZO5zC0uMSeA" Return-path: Sender: rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: <20170621123535.b5fvwlydfhnhuqll-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org> List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , To: Alexandre Belloni Cc: Thomas Gleixner , Russell King - ARM Linux , Benjamin Gaignard , Baruch Siach , "patches-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org" , Linus Walleij , "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Thierry Reding , "x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org" , Jonathan Hunter , Chen-Yu Tsai , Ingo Molnar , Sylvain Lemieux , Sebastian Hesselbarth , Len Brown , "linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org" , Jason Cooper , "rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org" , "linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: linux-pm@vger.kernel.org --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline 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 -- 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. --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-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Sender: rtc-linux@googlegroups.com Received: from atrey.karlin.mff.cuni.cz (atrey.karlin.mff.cuni.cz. [195.113.26.193]) by gmr-mx.google.com with ESMTPS id y3si1862452wmc.1.2017.06.21.11.08.48 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Jun 2017 11:08:49 -0700 (PDT) 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: [rtc-linux] 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" In-Reply-To: <20170621123535.b5fvwlydfhnhuqll@piout.net> Reply-To: rtc-linux@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline 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 -- 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@googlegroups.com. For more options, visit https://groups.google.com/d/optout. --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-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: pavel@ucw.cz (Pavel Machek) Date: Wed, 21 Jun 2017 20:08:47 +0200 Subject: [PATCH 00/51] rtc: stop using rtc deprecated functions In-Reply-To: <20170621123535.b5fvwlydfhnhuqll@piout.net> References: <20170620213507.urobmtg34vzubrdq@piout.net> <20170621075152.GA15996@amd> <20170621083907.y3gadsmsoufa5niv@piout.net> <20170621063443.GA4862@localhost> <20170621123535.b5fvwlydfhnhuqll@piout.net> Message-ID: <20170621180847.GA24175@amd> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: From mboxrd@z Thu Jan 1 00:00:00 1970 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 --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-- 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: Wed, 21 Jun 2017 20:08:47 +0200 Message-ID: <20170621180847.GA24175@amd> References: <20170620213507.urobmtg34vzubrdq@piout.net> <20170621075152.GA15996@amd> <20170621083907.y3gadsmsoufa5niv@piout.net> <20170621063443.GA4862@localhost> <20170621123535.b5fvwlydfhnhuqll@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="W/nzBZO5zC0uMSeA" Cc: Thomas Gleixner , Russell King - ARM Linux , Benjamin Gaignard , Baruch Siach , "patches-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org" , Linus Walleij , "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Thierry Reding , "x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org" , Jonathan Hunter , Chen-Yu Tsai , Ingo Molnar , Sylvain Lemieux , Sebastian Hesselbarth , Len Brown , "linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org" , Jason Cooper , "rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org" , "linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" Return-path: Sender: rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Content-Disposition: inline In-Reply-To: <20170621123535.b5fvwlydfhnhuqll-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org> List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , List-Id: netdev.vger.kernel.org --W/nzBZO5zC0uMSeA Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline 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 -- 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. --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--