[meta-freescale] [PATCH 0/1] arm: imx: fsl_otp: make fuses (OTP memory) read-only

Alexander Holler holler at ahsoftware.de
Sun Nov 9 02:14:39 PST 2014

Am 08.11.2014 19:49, schrieb Alexander Holler:

> I'm not confused, at least not in regard what you want to suggest. Of
> course, I'm totally confused about the fact that almost nobody else
> before has critized that write functionality of this driver, also I'm
> already used to the fact that I'm unable to understand many things which
> are happing in todays world. But nobody is perfect. ;)

Just to make it more clear what this thread is about, here is a relevant 
sentence copied form the reference manual for the chip:

"In order to avoid "rogue" code performing erroneous writes to OTP, a 
special unlocking sequence is required for writes to the fuse banks."

Now guess why the HW was designed this way. And then look again at the 
driver which nullifies the careful implementation in the HW. It doesn't 
have to be the fault of the author, e.g. he just might have written it 
for internal use. The problem is that it went into kernels for public 
use and nobody has seen a problem. Might be because of missing knowledge 
about what the driver does at all or whatever. I don't know.

Alexander Holler

More information about the meta-freescale mailing list