From: Jerome Brunet <jbrunet@baylibre.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Carlo Caione <carlo@caione.org>,
Kevin Hilman <khilman@baylibre.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] nvmem: meson-efuse: add write support
Date: Mon, 23 Apr 2018 14:41:46 +0200 [thread overview]
Message-ID: <20180423124149.3077-1-jbrunet@baylibre.com> (raw)
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]. It has now been merged by
Kevin.
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
Changes since v1 [1]:
- Remove un-necessary code in callbacks
- Rebase on v4.17-rc1
[0]: https://lkml.kernel.org/r/20180316145021.8517-1-jbrunet@baylibre.com
[1]: https://lkml.kernel.org/r/20180316150113.9779-1-jbrunet@baylibre.com
Jerome Brunet (3):
nvmem: meson-efuse: remove econfig global
nvmem: meson-efuse: simplify read callback
nvmem: meson-efuse: add write support
drivers/nvmem/meson-efuse.c | 41 ++++++++++++++++++++++-------------------
1 file changed, 22 insertions(+), 19 deletions(-)
--
2.14.3
WARNING: multiple messages have this Message-ID (diff)
From: jbrunet@baylibre.com (Jerome Brunet)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] nvmem: meson-efuse: add write support
Date: Mon, 23 Apr 2018 14:41:46 +0200 [thread overview]
Message-ID: <20180423124149.3077-1-jbrunet@baylibre.com> (raw)
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]. It has now been merged by
Kevin.
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
Changes since v1 [1]:
- Remove un-necessary code in callbacks
- Rebase on v4.17-rc1
[0]: https://lkml.kernel.org/r/20180316145021.8517-1-jbrunet at baylibre.com
[1]: https://lkml.kernel.org/r/20180316150113.9779-1-jbrunet at baylibre.com
Jerome Brunet (3):
nvmem: meson-efuse: remove econfig global
nvmem: meson-efuse: simplify read callback
nvmem: meson-efuse: add write support
drivers/nvmem/meson-efuse.c | 41 ++++++++++++++++++++++-------------------
1 file changed, 22 insertions(+), 19 deletions(-)
--
2.14.3
WARNING: multiple messages have this Message-ID (diff)
From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH v2 0/3] nvmem: meson-efuse: add write support
Date: Mon, 23 Apr 2018 14:41:46 +0200 [thread overview]
Message-ID: <20180423124149.3077-1-jbrunet@baylibre.com> (raw)
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]. It has now been merged by
Kevin.
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
Changes since v1 [1]:
- Remove un-necessary code in callbacks
- Rebase on v4.17-rc1
[0]: https://lkml.kernel.org/r/20180316145021.8517-1-jbrunet at baylibre.com
[1]: https://lkml.kernel.org/r/20180316150113.9779-1-jbrunet at baylibre.com
Jerome Brunet (3):
nvmem: meson-efuse: remove econfig global
nvmem: meson-efuse: simplify read callback
nvmem: meson-efuse: add write support
drivers/nvmem/meson-efuse.c | 41 ++++++++++++++++++++++-------------------
1 file changed, 22 insertions(+), 19 deletions(-)
--
2.14.3
next reply other threads:[~2018-04-23 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 12:41 Jerome Brunet [this message]
2018-04-23 12:41 ` [PATCH v2 0/3] nvmem: meson-efuse: add write support Jerome Brunet
2018-04-23 12:41 ` Jerome Brunet
2018-04-23 12:41 ` [PATCH v2 1/3] nvmem: meson-efuse: remove econfig global Jerome Brunet
2018-04-23 12:41 ` Jerome Brunet
2018-04-23 12:41 ` Jerome Brunet
2018-04-23 12:41 ` [PATCH v2 2/3] nvmem: meson-efuse: simplify read callback Jerome Brunet
2018-04-23 12:41 ` Jerome Brunet
2018-04-23 12:41 ` Jerome Brunet
2018-04-23 12:41 ` [PATCH v2 3/3] nvmem: meson-efuse: add write support Jerome Brunet
2018-04-23 12:41 ` Jerome Brunet
2018-04-23 12:41 ` Jerome Brunet
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=20180423124149.3077-1-jbrunet@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=carlo@caione.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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 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.