[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5DV+80np5qsq9JdKwmKFL1AkeqJ09S3o0XjQzAqYw0rYg@mail.gmail.com>
Date: Mon, 27 Mar 2017 10:42:06 -0300
From: Fabio Estevam <festevam@...il.com>
To: Richard Leitner <richard.leitner@...data.com>,
Sascha Hauer <kernel@...gutronix.de>,
Shawn Guo <shawnguo@...nel.org>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
dev@...l1n.net
Subject: Re: [PATCH 2/2] nvmem: imx-ocotp: add write support
[Adding Pengutronix folks and Shawn on Cc]
On Mon, Mar 27, 2017 at 10:31 AM, Richard Leitner
<richard.leitner@...data.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@...data.com>
Do we really want to have write support in the driver?
Powered by blists - more mailing lists