LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jerome Brunet <jbrunet@baylibre.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Carlo Caione <carlo@caione.org>,
	Kevin Hilman <khilman@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] nvmem: meson-efuse: add write support
Date: Thu, 19 Apr 2018 16:13:26 +0200	[thread overview]
Message-ID: <1524147206.2601.104.camel@baylibre.com> (raw)
In-Reply-To: <20180316150113.9779-1-jbrunet@baylibre.com>

On Fri, 2018-03-16 at 16:01 +0100, Jerome Brunet wrote:
> 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

Hi Srinivas,

Is this patchset ok with you ? Do you want to me to change something ?

Regards
Jerome

> 
> [0]: https://lkml.kernel.org/r/20180316145021.8517-1-jbrunet@baylibre.com
> 
> Jerome Brunet (2):
>   nvmem: meson-efuse: remove econfig global
>   nvmem: meson-efuse: add write support
> 
>  drivers/nvmem/meson-efuse.c | 37 +++++++++++++++++++++++++++----------
>  1 file changed, 27 insertions(+), 10 deletions(-)
> 

  parent reply	other threads:[~2018-04-19 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 15:01 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 ` Jerome Brunet [this message]
2018-04-19 14:29   ` [PATCH 0/2] " Srinivas Kandagatla
2018-04-19 17:42 ` Kevin Hilman

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=1524147206.2601.104.camel@baylibre.com \
    --to=jbrunet@baylibre.com \
    --cc=carlo@caione.org \
    --cc=khilman@baylibre.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --subject='Re: [PATCH 0/2] nvmem: meson-efuse: add write support' \
    /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

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).