From: Wolfgang Denk <wd@denx.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Heiko Schocher <hs@denx.de>,
Vitaly Bordug <vbordug@ru.mvista.com>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH] drivers, char: add U-Boot bootcount driver
Date: Sun, 04 Dec 2011 17:34:17 +0100 [thread overview]
Message-ID: <20111204163417.1AD6625EA22@gemini.denx.de> (raw)
In-Reply-To: <20111204114741.GA5788@pengutronix.de>
Dear Wolfram,
in message <20111204114741.GA5788@pengutronix.de> you wrote:
>
> > Description: OSDL CGL specifies that carrier grade Linux
> > shall provide support for detecting a repeating reboot cycle
> > due to recurring failures. This detection should happen in
> > user space before system services are started.
>
> So, technically, a flag would be enough, not necessarily a counter? Although a
> counter probably has more advantages...
The real-life applications we have seen so far all required a counter.
They all required to switch to a recovery mode or other alternative
boot sequence after N failed boot attempts, with N > 1 in all cases.
> > reg = <0x23060 0x20>;
>
> I assume that non-volatile memory would qualify as a boot-counter, so those
> could be tied to I2C busses etc? reg would not fit then.
Actually all kind of non-volatile storage can be used - it depends
on specific hardware roperties. Some SoCs have registers that are
guaranteed not to change theier value during a reset; on other systems
we have storage or NVRAM in RTCs or similar, or we can use SRAM, or
I2C or SPI attached EEPROM, or even storage on SDCard, USB or other
storage devices.
This binding covers the memory type only.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"There is nothing new under the sun, but there are lots of old things
we don't know yet." - Ambrose Bierce
next prev parent reply other threads:[~2011-12-04 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 9:45 [PATCH] drivers, char: add U-Boot bootcount driver Heiko Schocher
2011-12-04 10:34 ` Matthias Kaehlcke
2011-12-04 11:47 ` Wolfram Sang
2011-12-04 16:34 ` Wolfgang Denk [this message]
[not found] ` <20111204114741.GA5788-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-12-05 7:43 ` Thierry Reding
2011-12-05 14:39 ` Heiko Schocher
2011-12-06 21:50 ` Wolfram Sang
[not found] ` <20111206215056.GD14154-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-12-06 21:56 ` Wolfgang Denk
2011-12-06 22:06 ` Wolfram Sang
2011-12-06 23:22 ` Rob Herring
[not found] ` <4EDEA3BF.6020507-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-01-30 12:35 ` Heiko Schocher
2011-12-04 16:42 ` Paul Bolle
2011-12-04 23:30 ` Ryan Mallon
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=20111204163417.1AD6625EA22@gemini.denx.de \
--to=wd@denx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hs@denx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=vbordug@ru.mvista.com \
--cc=w.sang@pengutronix.de \
/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).