From: Sascha Hauer <s.hauer@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Richard Leitner <richard.leitner@skidata.com>,
Sascha Hauer <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
dev@g0hl1n.net
Subject: Re: [PATCH 2/2] nvmem: imx-ocotp: add write support
Date: Thu, 30 Mar 2017 08:16:43 +0200 [thread overview]
Message-ID: <20170330061643.mxk3regx6col4zt7@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5DV+80np5qsq9JdKwmKFL1AkeqJ09S3o0XjQzAqYw0rYg@mail.gmail.com>
On Mon, Mar 27, 2017 at 10:42:06AM -0300, Fabio Estevam wrote:
> [Adding Pengutronix folks and Shawn on Cc]
>
> On Mon, Mar 27, 2017 at 10:31 AM, Richard Leitner
> <richard.leitner@skidata.com> wrote:
> > Implement write routine for OCOTP controller found in i.MX6 SoC's.
> > Furthermore add locking to the read function to prevent race conditions.
> > The write routine code is based on the fsl_otp driver from Freescale.
> >
> > Signed-off-by: Richard Leitner <richard.leitner@skidata.com>
>
> Do we really want to have write support in the driver?
Why not? The fuses must be written somewhere and some like to do it
under Linux.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2017-03-30 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 13:31 [PATCH 1/2] nvmem: imx-ocotp: clear error bit after reading locked values Richard Leitner
2017-03-27 13:31 ` [PATCH 2/2] nvmem: imx-ocotp: add write support Richard Leitner
2017-03-27 13:42 ` Fabio Estevam
2017-03-27 13:59 ` Richard Leitner
2017-03-30 6:16 ` Sascha Hauer [this message]
2017-04-03 13:18 ` Rob Herring
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=20170330061643.mxk3regx6col4zt7@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=dev@g0hl1n.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=richard.leitner@skidata.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®