From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-arm-kernel@lists.infradead.org,
Andrew Lunn <andrew@lunn.ch>,
tbm@cyrius.com, Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org
Subject: Re: TS-219 RTC issue with Debian Buster
Date: Tue, 23 Jul 2019 21:34:43 +0200 [thread overview]
Message-ID: <20190723193443.bqcbrxalng554u76@pengutronix.de> (raw)
In-Reply-To: <4a5c0768-0383-0a16-8d3f-639dc9530abf@hartkopp.net>
Hello Oliver,
On Tue, Jul 23, 2019 at 09:21:06PM +0200, Oliver Hartkopp wrote:
> I think I already solved the problem, see here:
> https://marc.info/?l=linux-arm-kernel&m=156390875629259&w=2
IMHO the right fix is teach hwclock to handle your rtc correctly.
Changing the driver from =m to =y is only a workaround.
Maybe also using the time stuff from systemd instead of hwclock will
help^Wwork around your problem (not sure though).
Also I wonder why the ioctl to enable UIE doesn't fail if the driver set
.uie_unsupported (but I didn't look closely).
> Will file a Debian bug for it ...
Not sure this will have success. These were switched from =y to =m
because the kernel images got to big.
(https://salsa.debian.org/kernel-team/linux/commit/c55043a43eaacb9f876dabd71273b084cb024441)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2019-07-23 19:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99a8e2cc-61a2-3b43-0d72-6f001cffe572@hartkopp.net>
2019-07-23 19:06 ` TS-219 RTC issue with Debian Buster Uwe Kleine-König
2019-07-23 19:21 ` Oliver Hartkopp
2019-07-23 19:34 ` Uwe Kleine-König [this message]
2019-07-23 20:07 ` Oliver Hartkopp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190723193443.bqcbrxalng554u76@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rtc@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=tbm@cyrius.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).