From: Tony Lindgren <tony@atomide.com>
To: Ladislav Michl <oss-lists@triops.cz>
Cc: linux-rtc@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] rtc: rtc-twl: add NVRAM support
Date: Tue, 18 Apr 2023 15:46:24 +0300 [thread overview]
Message-ID: <20230418124624.GD14287@atomide.com> (raw)
In-Reply-To: <ZD6G+6WtjpDYs3Zw@lenoch>
* Ladislav Michl <oss-lists@triops.cz> [230418 12:03]:
> Hi Tony,
>
> On Tue, Apr 18, 2023 at 12:43:03PM +0300, Tony Lindgren wrote:
> > Hi,
> >
> > * Ladislav Michl <oss-lists@triops.cz> [230413 12:56]:
> > > Export SRAM using nvmem.
> >
> > Patch looks good to me, just wondering how this is used..
>
> This has been sitting in my tree for over five years and it is used
> to store boot state. Patches for u-boot are pending here as well,
> but I'll do my best to upstream reasonable parts of them.
>
> All was done for failsafe device updating using A/B scheme. Device
> is also using U-Boot's Falcon mode to speed things up, so SPL
> loads kernel directly from UBI volume. To decide which one to load
> and boot, information from NVRAM is used - there is no other memory
> except NVRAM and NAND. I didn't want to use NAND for this purpose,
> see bellow how NVRAM failures are handled.
>
> > Are we just exporting the nvram via sysfs for userspace to use it
> > for whatever, or is there also some RTC core layer use for it?
>
> RTC itself is not using it. My board is using RAUC for updates:
> https://rauc.readthedocs.io/en/latest/examples.html#symmetric-a-b-setup
OK thanks for the detailed information :)
Regards,
Tony
next prev parent reply other threads:[~2023-04-18 12:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 12:55 [PATCH] rtc: rtc-twl: add NVRAM support Ladislav Michl
2023-04-18 9:43 ` Tony Lindgren
2023-04-18 12:03 ` Ladislav Michl
2023-04-18 12:46 ` Tony Lindgren [this message]
2023-05-31 4:17 ` Tony Lindgren
2023-08-14 20:00 ` Ladislav Michl
2023-08-27 22:10 ` 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=20230418124624.GD14287@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=oss-lists@triops.cz \
/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.