Hi, On Fri, Dec 4, 2015 at 8:02 PM, Doug Anderson <diand...@chromium.org> wrote: > Hi, > > On Fri, Dec 4, 2015 at 5:54 PM, Julius Werner <jwer...@chromium.org> wrote: >>> How would such a hook work? If userspace sees the system suspend on >>> Nov 30th and sees the system wake up on Dec 1st, how does it know >>> whether it should adjust? If it's truly Dec 1st then the kernel will >>> have adjusted the date from Nov 31st to Dec 1st. If it's truly Dec >>> 2nd then the kernel will not have adjusted the date and the RTC will >>> have ticked past Nov 31 and onto Dec 1st. Userspace can't tell. >>> Userspace could try to parse "dmesg" and look to see if the kernel >>> adjusted, but that's ugly. >> >> Good point, I didn't think that through far enough. I guess parsing >> dmesg would be an option, but a pretty ugly one and it wouldn't be >> guaranteed to work if you got an early boot kernel crash after the >> correction. So, really, it seems like there's no reliable way to fix >> this for S5 (unless we start doing crazy things like writing to disk >> from kernel code). > > Hmmm, this made me think. We _do_ have some storage we could use, > depending on how hacky^H^H^H^H^H^H clever we wanted to be. We've got > the alarm registers in the RTC. If we set the alarm to something but > then turn the alarm off then we can use that to store information that > will persist in S5 (as long as the RTC is ticking). What do you > think? I'd have to think of a scheme, but we could certainly use > alarms that are several years in the future (or the past) as a > sentinel, then use the day/month of the last time the kernel saw the > time....
Actually, it wouldn't even be that terribly hacky Whenever the alarm isn't in use then set it to the next Nov 31st. At boot time, if the alarm is set to Nov 31st and the current date is >= the alarm time then you adjust. At shutdown time always disable the alarm (and set to Nov 31st). To handle resume time you might as well just keep the state somewhere in RAM (see below for why). Whenever you set the alarm for real then presumably you'll need to adjust for Nov 31st and presumably you'll wake up and deal with the alarm, then turn it off. So if you set the alarm for July 4th then (presumably) you'll wake up way before Nov 31st. If you set the alarm for Dec 25th and it's currently Oct 31st then you'll have to adjust in the alarm code and you'll really set it for Dec 24th. As per above, we're in S3 (presumably) or have some persistent kernel state so we know to adjust everything when we wake up (even if we wake up for a non-alarm reason). You'll still get a failure if you set the alarm and then forcibly go into S5 without software knowledge, then stay in S5 long enough to cross over Nov 31st without seeing it (but somehow keep the RTC state). ...but come on, that seems so incredibly rare! :-P Of course, all this hinges on being able to tell whether we've got the bug or not so we know whether to adjust. Assuming that there is no ID register, we could get someone from Rockchip to agree to change _something_ in a way that it's visible to us if they ever fix the bug... -Doug -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
