[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8a1caa0b-8117-4e2f-1782-a9251f617969@skidata.com>
Date: Mon, 27 Mar 2017 15:59:17 +0200
From: Richard Leitner <richard.leitner@...data.com>
To: Fabio Estevam <festevam@...il.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
On 03/27/2017 03:42 PM, Fabio Estevam wrote:
> [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?
We need it for our "factory startup" process and other fusebox drivers
support it as well. Therefore I thought it would be a good idea to bring
it upstream.
Furthermore you can disable it via devicetree (and it would also be
possible to introduce a CONFIG for write support if it's wanted).
kind regards,
Richard L
Powered by blists - more mailing lists