All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: pure.logic@nexus-software.ie, richard.leitner@skidata.com
Cc: peng.fan@nxp.com, andrea@inversepath.com, festevam@gmail.com,
	kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org
Subject: nvmem: imx-ocotp: fusing write tools
Date: Wed, 18 Dec 2019 11:10:59 +0100	[thread overview]
Message-ID: <2d527ebfde26459b7fa57e519610a8a5@agner.ch> (raw)

Hi,

We are looking to replace the NXP downstream OTP driver (CONFIG_FSL_OTP)
with the new upstream nvmem based driver. I was wondering if there is
user-space tooling around which can be used to write fuses. The NXP
driver had the fuse map as part of the API, so fusing was rather simple
and only required an echo into the right file. The new driver requires a
seek to the right offset. 

I found this tool which provides fuse maps as yaml files and makes
fusing rather simple:
https://github.com/inversepath/crucible

At this point it seems to miss i.MX 8 series fuse maps. Also we so far
have no go runtime on our production system, we consider writing a
(probably simpler) C implementation thereof.

What is generally used to write fuses using the nvmem driver?

--
Stefan

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-12-18 10:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18 10:10 Stefan Agner [this message]
2019-12-18 10:18 ` nvmem: imx-ocotp: fusing write tools Barisani, Andrea

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=2d527ebfde26459b7fa57e519610a8a5@agner.ch \
    --to=stefan@agner.ch \
    --cc=andrea@inversepath.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=peng.fan@nxp.com \
    --cc=pure.logic@nexus-software.ie \
    --cc=richard.leitner@skidata.com \
    /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.