From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
kernel@pengutronix.de, Alessandro Zummo <a.zummo@towertech.it>,
linux-arm-kernel@lists.infradead.org,
Robert Schwebel <rsc@pengutronix.de>
Subject: Re: [rtc-linux] [PATCH 2/5] RTC/i.MX/DryIce: add the unit recovery code
Date: Wed, 22 Apr 2015 01:46:50 +0200 [thread overview]
Message-ID: <20150421234649.GG8539@piout.net> (raw)
In-Reply-To: <20150421231411.GC8539@piout.net>
On 22/04/2015 at 01:14:11 +0200, Alexandre Belloni wrote :
> > + sec = __raw_readl(imxdi->ioaddr + DTCMR);
> > + if (sec != 0)
> > + dev_warn(&imxdi->pdev->dev,
> > + "The security violation has happend at %u seconds\n",
>
> Further improvement for this driver: use both DTCMR and DTCLR to be year
> 2038 proof
Please forget that comment I just realized that seconds were counted in
the most significant part...
--
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.
WARNING: multiple messages have this Message-ID (diff)
From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [rtc-linux] [PATCH 2/5] RTC/i.MX/DryIce: add the unit recovery code
Date: Wed, 22 Apr 2015 01:46:50 +0200 [thread overview]
Message-ID: <20150421234649.GG8539@piout.net> (raw)
In-Reply-To: <20150421231411.GC8539@piout.net>
On 22/04/2015 at 01:14:11 +0200, Alexandre Belloni wrote :
> > + sec = __raw_readl(imxdi->ioaddr + DTCMR);
> > + if (sec != 0)
> > + dev_warn(&imxdi->pdev->dev,
> > + "The security violation has happend at %u seconds\n",
>
> Further improvement for this driver: use both DTCMR and DTCLR to be year
> 2038 proof
Please forget that comment I just realized that seconds were counted in
the most significant part...
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Juergen Borleis <jbe@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
kernel@pengutronix.de, Alessandro Zummo <a.zummo@towertech.it>,
linux-arm-kernel@lists.infradead.org,
Robert Schwebel <rsc@pengutronix.de>
Subject: Re: [rtc-linux] [PATCH 2/5] RTC/i.MX/DryIce: add the unit recovery code
Date: Wed, 22 Apr 2015 01:46:50 +0200 [thread overview]
Message-ID: <20150421234649.GG8539@piout.net> (raw)
In-Reply-To: <20150421231411.GC8539@piout.net>
On 22/04/2015 at 01:14:11 +0200, Alexandre Belloni wrote :
> > + sec = __raw_readl(imxdi->ioaddr + DTCMR);
> > + if (sec != 0)
> > + dev_warn(&imxdi->pdev->dev,
> > + "The security violation has happend at %u seconds\n",
>
> Further improvement for this driver: use both DTCMR and DTCLR to be year
> 2038 proof
Please forget that comment I just realized that seconds were counted in
the most significant part...
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-21 23:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 9:11 [rtc-linux] [PATCH 2nd try] RTC/i.MX/DryICE: add recovery routines to the driver Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-14 9:11 ` [rtc-linux] [PATCH 1/5] RTC/i.MX/DryIce: add some background info about the states the machine can be in Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-21 22:09 ` [rtc-linux] " Alexandre Belloni
2015-04-21 22:09 ` Alexandre Belloni
2015-04-24 10:10 ` Juergen Borleis
2015-04-24 10:10 ` Juergen Borleis
2015-04-24 10:10 ` Juergen Borleis
2015-04-14 9:11 ` [rtc-linux] [PATCH 2/5] RTC/i.MX/DryIce: add the unit recovery code Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-21 23:14 ` [rtc-linux] " Alexandre Belloni
2015-04-21 23:14 ` Alexandre Belloni
2015-04-21 23:14 ` Alexandre Belloni
2015-04-21 23:46 ` Alexandre Belloni [this message]
2015-04-21 23:46 ` Alexandre Belloni
2015-04-21 23:46 ` Alexandre Belloni
2015-04-24 10:24 ` Juergen Borleis
2015-04-24 10:24 ` Juergen Borleis
2015-04-24 10:24 ` Juergen Borleis
2015-04-14 9:11 ` [rtc-linux] [PATCH 3/5] RTC/i.MX/DryIce: monitor a security violation at runtime Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-14 9:11 ` [rtc-linux] [PATCH 4/5] RTC/i.MX/DryIce: when locked, do not fail silently Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-21 23:30 ` [rtc-linux] " Alexandre Belloni
2015-04-21 23:30 ` Alexandre Belloni
2015-04-21 23:30 ` Alexandre Belloni
2015-04-14 9:11 ` [rtc-linux] [PATCH 5/5] RTC/i.MX/DryIce: prepare to force a security violation Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-14 9:11 ` Juergen Borleis
2015-04-21 23:26 ` [rtc-linux] [PATCH 2nd try] RTC/i.MX/DryICE: add recovery routines to the driver Alexandre Belloni
2015-04-21 23:26 ` Alexandre Belloni
2015-04-21 23:26 ` Alexandre Belloni
2015-04-24 10:32 ` Juergen Borleis
2015-04-24 10:32 ` Juergen Borleis
2015-04-24 10:32 ` Juergen Borleis
-- strict thread matches above, loose matches on Subject: below --
2015-04-14 9:08 [rtc-linux] [PATCH 1/5] RTC/i.MX/DryIce: add some background info about the states the machine can be in Juergen Borleis
2015-04-14 9:08 ` [rtc-linux] [PATCH 2/5] RTC/i.MX/DryIce: add the unit recovery code Juergen Borleis
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=20150421234649.GG8539@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=jbe@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rsc@pengutronix.de \
--cc=rtc-linux@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.