From: Juergen Borleis <jbe@pengutronix.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
kernel@pengutronix.de, Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com
Subject: Re: [rtc-linux] [PATCH 2nd try] RTC/i.MX/DryICE: add recovery routines to the driver
Date: Fri, 24 Apr 2015 12:32:30 +0200 [thread overview]
Message-ID: <201504241232.30104.jbe@pengutronix.de> (raw)
In-Reply-To: <20150421232615.GD8539@piout.net>
Hi Alexandre,
On Wednesday 22 April 2015 01:26:15 Alexandre Belloni wrote:
> On 14/04/2015 at 11:11:51 +0200, Juergen Borleis wrote :
> > 2nd try, this time with a cover letter... m(
> >
> > The built-in RTC unit on some i.MX SoCs isn't an RTC only. It is also a
> > tamper monitor unit which can keep some keys. When it does its tamper
> > detection job
>
> Does it have more functions? I would say that it also holds some keys
> but I don't have a handy Freescale representative to contact ;)
Yes it can hold some keys and will delete them if it detects a security=20
violation via its tamper detection feature.
> I'm fine getting that unlocking done in the RTC driver but maybe in the
> future, it will be necessary to handle that in an MFD driver when adding
> support for the other functions.
This change set just makes the RTC work again. Observation was, *sometimes*=
and=20
*somehow* this unit tends to lock even if no of these tamper detection=20
features were enabled nor the externals signals (to detect these security=20
violations) were used.
Regards,
Juergen
=2D-=20
Pengutronix e.K. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0| Juergen Borleis =A0 =A0 =A0 =A0 =A0 =A0 |
Industrial Linux Solutions =A0 =A0 =A0| http://www.pengutroni=
x.de/ |
WARNING: multiple messages have this Message-ID (diff)
From: jbe@pengutronix.de (Juergen Borleis)
To: linux-arm-kernel@lists.infradead.org
Subject: [rtc-linux] [PATCH 2nd try] RTC/i.MX/DryICE: add recovery routines to the driver
Date: Fri, 24 Apr 2015 12:32:30 +0200 [thread overview]
Message-ID: <201504241232.30104.jbe@pengutronix.de> (raw)
In-Reply-To: <20150421232615.GD8539@piout.net>
Hi Alexandre,
On Wednesday 22 April 2015 01:26:15 Alexandre Belloni wrote:
> On 14/04/2015 at 11:11:51 +0200, Juergen Borleis wrote :
> > 2nd try, this time with a cover letter... m(
> >
> > The built-in RTC unit on some i.MX SoCs isn't an RTC only. It is also a
> > tamper monitor unit which can keep some keys. When it does its tamper
> > detection job
>
> Does it have more functions? I would say that it also holds some keys
> but I don't have a handy Freescale representative to contact ;)
Yes it can hold some keys and will delete them if it detects a security
violation via its tamper detection feature.
> I'm fine getting that unlocking done in the RTC driver but maybe in the
> future, it will be necessary to handle that in an MFD driver when adding
> support for the other functions.
This change set just makes the RTC work again. Observation was, *sometimes* and
*somehow* this unit tends to lock even if no of these tamper detection
features were enabled nor the externals signals (to detect these security
violations) were used.
Regards,
Juergen
--
Pengutronix e.K. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| Juergen Borleis ? ? ? ? ? ? |
Industrial Linux Solutions ? ? ?| http://www.pengutronix.de/ |
WARNING: multiple messages have this Message-ID (diff)
From: Juergen Borleis <jbe@pengutronix.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
kernel@pengutronix.de, Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com
Subject: Re: [rtc-linux] [PATCH 2nd try] RTC/i.MX/DryICE: add recovery routines to the driver
Date: Fri, 24 Apr 2015 12:32:30 +0200 [thread overview]
Message-ID: <201504241232.30104.jbe@pengutronix.de> (raw)
In-Reply-To: <20150421232615.GD8539@piout.net>
Hi Alexandre,
On Wednesday 22 April 2015 01:26:15 Alexandre Belloni wrote:
> On 14/04/2015 at 11:11:51 +0200, Juergen Borleis wrote :
> > 2nd try, this time with a cover letter... m(
> >
> > The built-in RTC unit on some i.MX SoCs isn't an RTC only. It is also a
> > tamper monitor unit which can keep some keys. When it does its tamper
> > detection job
>
> Does it have more functions? I would say that it also holds some keys
> but I don't have a handy Freescale representative to contact ;)
Yes it can hold some keys and will delete them if it detects a security
violation via its tamper detection feature.
> I'm fine getting that unlocking done in the RTC driver but maybe in the
> future, it will be necessary to handle that in an MFD driver when adding
> support for the other functions.
This change set just makes the RTC work again. Observation was, *sometimes* and
*somehow* this unit tends to lock even if no of these tamper detection
features were enabled nor the externals signals (to detect these security
violations) were used.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2015-04-24 10:30 UTC|newest]
Thread overview: 41+ 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
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 [this message]
2015-04-24 10:32 ` Juergen Borleis
2015-04-24 10:32 ` 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=201504241232.30104.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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.