From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Julius Werner <jwerner@chromium.org>
Cc: Doug Anderson <dianders@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Sonny Rao <sonnyrao@chromium.org>,
Chris Zhong <zyw@rock-chips.com>,
Heiko Stuebner <heiko@sntech.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
rtc-linux@googlegroups.com
Subject: [rtc-linux] Re: [PATCH v2] RTC: RK808: Work around hardware bug on November 31st
Date: Thu, 10 Dec 2015 19:41:19 +0100 [thread overview]
Message-ID: <20151210184119.GL3515@piout.net> (raw)
In-Reply-To: <CAODwPW9M6gWXpUkT2A3k6jmj7sBzwjmScE+ZSAe209UDnAW6mg@mail.gmail.com>
Hi Julius, Doug,
On 09/12/2015 at 13:32:52 -0800, Julius Werner wrote :
> > Thinking about all this: these's actually a totally different
> > alternative approach we could take if you wanted. It would fix S5 and
> > avoid all the anchor stuff, unless I'm crazy.
> >
> > Basically totally give up on the RTC time reflecting reality. Add a
> > "real time to rk808" and "rk808 time to real time" function. Always
> > use it when reading from rk808 and always use it when writing to
> > rk808. Choose 2015 as the "truth" year if you want (or pick another
> > year). In early 2016 the rk808 always contains 1 day back. In 2017
> > the rk808 always contains 2 days back. Etc, etc, etc.
> >
> > The firmware would get confused, but ...
>
> Well... other than that it's crazy and that I'd have to rewrite the
> whole patch again, I can't come up with a good argument against this.
> In Chromebook firmware the time is only needed for a debug log, so
> we'd probably just be willing to accept it being wrong. If U-Boot ever
> gets RK808 support, they'll probably just copy the Linux driver
> wholesale anyway so they'll conform to the same system.
>
> So if nobody else raises fundamental objections to this approach, I
> guess I'll get started on another patch version. (Further replies
> below for reference, but most of that stuff would then become moot.)
>
I'll try to review and evaluate both solution by the end of the week (no
guarantee though).
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
--
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.
next prev parent reply other threads:[~2015-12-10 18:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 1:53 [rtc-linux] [PATCH] RTC: RK808: Work around hardware bug on November 31st Julius Werner
2015-12-03 14:42 ` Alexandre Belloni
2015-12-03 16:53 ` Julius Werner
2015-12-04 23:50 ` [rtc-linux] " Doug Anderson
2015-12-05 0:25 ` Julius Werner
2015-12-05 0:58 ` Doug Anderson
2015-12-05 1:54 ` Julius Werner
2015-12-05 4:02 ` Doug Anderson
2015-12-05 4:53 ` Doug Anderson
2015-12-05 7:17 ` Julius Werner
2015-12-06 0:36 ` Doug Anderson
2015-12-07 1:33 ` Chris Zhong
2015-12-07 2:50 ` Doug Anderson
2015-12-07 2:52 ` Doug Anderson
2015-12-07 3:08 ` Chris Zhong
2015-12-07 20:28 ` Julius Werner
2015-12-07 22:40 ` Julius Werner
2015-12-08 1:17 ` Doug Anderson
2015-12-08 1:41 ` Julius Werner
2015-12-08 5:19 ` Julius Werner
2015-12-08 5:21 ` [rtc-linux] [PATCH v2] " Julius Werner
2015-12-09 5:44 ` [rtc-linux] " Doug Anderson
2015-12-09 21:32 ` Julius Werner
2015-12-10 18:41 ` Alexandre Belloni [this message]
2015-12-10 18:57 ` Julius Werner
2015-12-15 23:02 ` [rtc-linux] [PATCHv3] RTC: RK808: Compensate for Rockchip calendar deviation " Julius Werner
2015-12-15 23:14 ` [rtc-linux] " Julius Werner
2015-12-19 0:25 ` Doug Anderson
2015-12-19 0:31 ` Julius Werner
2015-12-19 0:26 ` Doug Anderson
2015-12-21 8:16 ` Alexandre Belloni
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=20151210184119.GL3515@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sonnyrao@chromium.org \
--cc=zyw@rock-chips.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