All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: "Jon Nettleton" <jon.nettleton@gmail.com>,
	"Eric Bénard" <eric@eukrea.com>
Cc: meta-freescale@yoctoproject.org,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [PATCH 0/1] arm: imx: fsl_otp: make fuses (OTP memory) read-only
Date: Fri, 07 Nov 2014 15:55:28 +0100	[thread overview]
Message-ID: <545CDD60.9020901@ahsoftware.de> (raw)
In-Reply-To: <CALHpu36rUCj6ZFRMn5V5p1u+S-YHOxUfEBJc_j_WkonJttnAdg@mail.gmail.com>

Am 07.11.2014 15:31, schrieb Jon Nettleton:
> Fair enough.  Can we all agree that it should default to disabled?

Anyone who is in need to write the OTP should be able to apply a patch 
or to do a git revert in order to use that functionality.

Those which are unable to do so, might not have an idea about OTP at 
all, or they might not be aware how dangerous it is to write it (besides 
the necessary knowledge about what to change).

Regards,

Alexander Holler

>
> -Jon
>
> On Fri, Nov 7, 2014 at 3:00 PM, Eric Bénard <eric@eukrea.com> wrote:
>> Hi Alexander,
>>
>> Le Fri,  7 Nov 2014 10:43:34 +0100,
>> Alexander Holler <holler@ahsoftware.de> a écrit :
>>> Jon Nettleton made me aware that there is a driver which makes it very
>>> easy to write to the OTP from userspace.
>>>
>>> And I have to admit that I was mildly shocked.
>>>
>>> Because OTP stands for One Time Programmable, it means the write
>>> functionality of that driver can be used only once per HW and if that
>>> is done wrong, the HW might be one of those famous electronic bricks
>>> afterwards.
>>>
>>> So I've quickly written a patch which makes this driver to a friendly
>>> citizen instead of an heavily armed cowboy.
>>>
>>> I really, really think this patch should be attached to all trees which
>>> are including fsl_otp.c. It applies without any error to
>>> imx_3.10.17_1.0.1_ga, imx_3.10.31_1.1.0_beta, linux-linaro-lsk-v3.14-mx6
>>> and likely any other tree which includes that driver.
>>>
>> That's not shocking to have this feature in a reference design's BSP :
>> Freescale provides base source code to evaluate their SOC and writing
>> OTP is one feature of their SOC.
>> Then that's the end product designer's responsibility to enable/disable
>> features he wants or not on its product.
>>
>> The solution proposed by Otavio to add an option to ease the
>> disabling of this feature is far better than fully removing the code.
>>
>> Best regards,
>> Eric




  reply	other threads:[~2014-11-07 14:59 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  9:43 [PATCH 0/1] arm: imx: fsl_otp: make fuses (OTP memory) read-only Alexander Holler
2014-11-07  9:43 ` [PATCH 1/1] " Alexander Holler
2014-11-07 11:34   ` Otavio Salvador
2014-11-07 14:40     ` Alexander Holler
2014-11-07 15:06       ` Otavio Salvador
2014-11-07 15:26         ` Alexander Holler
2014-11-07 14:00 ` [PATCH 0/1] " Eric Bénard
2014-11-07 14:31   ` Jon Nettleton
2014-11-07 14:55     ` Alexander Holler [this message]
2014-11-07 15:04     ` Eric Bénard
2014-11-07 15:07       ` Otavio Salvador
2014-11-07 15:23         ` Alexander Holler
2014-11-07 16:00           ` Otavio Salvador
2014-11-07 16:38             ` Alexander Holler
2014-11-08  2:03               ` Nikolay Dimitrov
2014-11-08  8:58                 ` Chris Tapp
2014-11-08  9:32                   ` Jon Nettleton
2014-11-08 18:49                 ` Alexander Holler
2014-11-09 10:14                   ` Alexander Holler
2014-11-09 15:09                     ` Eric Bénard
2014-11-09 17:03                       ` Bob Cochran
2014-11-09 12:34                   ` Nikolay Dimitrov
2014-11-09 18:09                     ` Alexander Holler
2014-11-09 19:20                       ` Nikolay Dimitrov
2014-11-07 16:03           ` Eric Bénard
2014-11-07 15:50         ` Eric Bénard
  -- strict thread matches above, loose matches on Subject: below --
2014-11-08 21:54 Robin Findley
2014-11-10 14:11 ` Alexander Holler
2014-11-13 19:19   ` Alexander Holler

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=545CDD60.9020901@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=eric@eukrea.com \
    --cc=jon.nettleton@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.