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-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH 2/2] nvmem: meson-efuse: add write support Date: Fri, 16 Mar 2018 16:01:13 +0100 [thread overview] Message-ID: <20180316150113.9779-3-jbrunet@baylibre.com> (raw) In-Reply-To: <20180316150113.9779-1-jbrunet@baylibre.com> Add write support to the meson-gx efuse driver. Beware, this efuse is one time programmable ! Signed-off-by: Jerome Brunet <jbrunet@baylibre.com> --- drivers/nvmem/meson-efuse.c | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/drivers/nvmem/meson-efuse.c b/drivers/nvmem/meson-efuse.c index 7ad80b80b293..30da5e1abf84 100644 --- a/drivers/nvmem/meson-efuse.c +++ b/drivers/nvmem/meson-efuse.c @@ -35,6 +35,20 @@ static int meson_efuse_read(void *context, unsigned int offset, return 0; } +static int meson_efuse_write(void *context, unsigned int offset, + void *val, size_t bytes) +{ + u8 *buf = val; + int ret; + + ret = meson_sm_call_write(buf, bytes, SM_EFUSE_WRITE, offset, + bytes, 0, 0, 0); + if (ret < 0) + return ret; + + return 0; +} + static const struct of_device_id meson_efuse_match[] = { { .compatible = "amlogic,meson-gxbb-efuse", }, { /* sentinel */ }, @@ -59,8 +73,8 @@ static int meson_efuse_probe(struct platform_device *pdev) econfig->name = dev_name(dev); econfig->stride = 1; econfig->word_size = 1; - econfig->read_only = true; econfig->reg_read = meson_efuse_read; + econfig->reg_write = meson_efuse_write; econfig->size = size; nvmem = nvmem_register(econfig); -- 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 2/2] nvmem: meson-efuse: add write support Date: Fri, 16 Mar 2018 16:01:13 +0100 [thread overview] Message-ID: <20180316150113.9779-3-jbrunet@baylibre.com> (raw) In-Reply-To: <20180316150113.9779-1-jbrunet@baylibre.com> Add write support to the meson-gx efuse driver. Beware, this efuse is one time programmable ! Signed-off-by: Jerome Brunet <jbrunet@baylibre.com> --- drivers/nvmem/meson-efuse.c | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/drivers/nvmem/meson-efuse.c b/drivers/nvmem/meson-efuse.c index 7ad80b80b293..30da5e1abf84 100644 --- a/drivers/nvmem/meson-efuse.c +++ b/drivers/nvmem/meson-efuse.c @@ -35,6 +35,20 @@ static int meson_efuse_read(void *context, unsigned int offset, return 0; } +static int meson_efuse_write(void *context, unsigned int offset, + void *val, size_t bytes) +{ + u8 *buf = val; + int ret; + + ret = meson_sm_call_write(buf, bytes, SM_EFUSE_WRITE, offset, + bytes, 0, 0, 0); + if (ret < 0) + return ret; + + return 0; +} + static const struct of_device_id meson_efuse_match[] = { { .compatible = "amlogic,meson-gxbb-efuse", }, { /* sentinel */ }, @@ -59,8 +73,8 @@ static int meson_efuse_probe(struct platform_device *pdev) econfig->name = dev_name(dev); econfig->stride = 1; econfig->word_size = 1; - econfig->read_only = true; econfig->reg_read = meson_efuse_read; + econfig->reg_write = meson_efuse_write; econfig->size = size; nvmem = nvmem_register(econfig); -- 2.14.3
next prev parent reply other threads:[~2018-03-16 15:01 UTC|newest] Thread overview: 12+ 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 ` Jerome Brunet 2018-03-16 15:01 ` [PATCH 1/2] nvmem: meson-efuse: remove econfig global Jerome Brunet 2018-03-16 15:01 ` Jerome Brunet 2018-03-16 15:01 ` Jerome Brunet [this message] 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:13 ` Jerome Brunet 2018-04-19 14:29 ` Srinivas Kandagatla 2018-04-19 14:29 ` Srinivas Kandagatla 2018-04-19 17:42 ` Kevin Hilman 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=20180316150113.9779-3-jbrunet@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 \ /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: linkBe 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.