From: khilman@baylibre.com (Kevin Hilman)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/2] nvmem: meson-efuse: add write support
Date: Thu, 19 Apr 2018 10:42:40 -0700 [thread overview]
Message-ID: <7hwox33xf3.fsf@baylibre.com> (raw)
In-Reply-To: <20180316150113.9779-1-jbrunet@baylibre.com> (Jerome Brunet's message of "Fri, 16 Mar 2018 16:01:11 +0100")
Jerome Brunet <jbrunet@baylibre.com> writes:
> This changeset adds write support to meson efuse driver.
> The first patch just changes the way the nvmem data are allocated w/o
> any functional changes. The second patches actually adds write support.
>
> The memory being an OTP, it is safer if it remains read-only by default,
> which is why I also submitted this DT patch [0].
>
> If a user knows what he is doing, it should be easy to remove the
> read-only property from the board DT. This can be done in u-boot, before
> starting linux:
>
> > fdt rm /efuse read-only
>
> Tested on the gxl libretech-cc
For the series,
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
prev parent reply other threads:[~2018-04-19 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 15:01 [PATCH 0/2] nvmem: meson-efuse: add write support Jerome Brunet
2018-03-16 15:01 ` [PATCH 1/2] nvmem: meson-efuse: remove econfig global Jerome Brunet
2018-03-16 15:01 ` [PATCH 2/2] nvmem: meson-efuse: add write support Jerome Brunet
2018-04-19 14:13 ` [PATCH 0/2] " Jerome Brunet
2018-04-19 14:29 ` Srinivas Kandagatla
2018-04-19 17:42 ` Kevin Hilman [this message]
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=7hwox33xf3.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linus-amlogic@lists.infradead.org \
/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).