From: "Marek Behún" <marek.behun@nic.cz>
To: "Pali Rohár" <pali@kernel.org>
Cc: Stefan Roese <sr@denx.de>, u-boot@lists.denx.de
Subject: Re: [PATCH] arm: mvebu: Add support for reading LD0 and LD1 eFuse
Date: Wed, 6 Apr 2022 21:21:59 +0200 [thread overview]
Message-ID: <20220406212159.6eefb7b1@thinkpad> (raw)
In-Reply-To: <20220406121818.31078-1-pali@kernel.org>
On Wed, 6 Apr 2022 14:18:18 +0200
Pali Rohár <pali@kernel.org> wrote:
> Armada 385 contains 64 lines of HD eFuse and 2 lines of LD eFuse. HD eFuse
> is used for secure boot and each line is 64 bits long + 1 lock bit. LD
> eFuse lines are 256 bits long + 1 lock bit. LD 0 line is reserved for
> Marvell Internal Use and LD 1 line is for General Purpose Data. U-Boot
> already contains HD eFuse reading and programming support.
>
> This patch implements LD eFuse reading support. LD 0 line is mapped to
> U-Boot fuse bank 64 and LD 1 line to fuse bank 65.
>
> LD 0 Marvell Internal Use line seems that was burned in factory with some
> data and can be read by U-Boot fuse command:
>
> => fuse read 64 0 9
>
> LD 1 General Purpose Data line is by default empty and can be read by
> U-Boot fuse command:
>
> => fuse read 65 0 9
>
> Signed-off-by: Pali Rohár <pali@kernel.org>
I am not sure whether this can be used safely on Turris Omnia - there
was some issue with voltage or something, I know for sure that burning
does not work on Omnia, but I am not sure if the issue also prevents
stable reading.
Are the values you read always the same? Even across power cycles?
Marek
next prev parent reply other threads:[~2022-04-06 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 12:18 [PATCH] arm: mvebu: Add support for reading LD0 and LD1 eFuse Pali Rohár
2022-04-06 19:21 ` Marek Behún [this message]
2022-04-07 11:53 ` Pali Rohár
2022-04-07 11:57 ` Marek Behún
2022-04-21 14:07 ` Stefan Roese
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=20220406212159.6eefb7b1@thinkpad \
--to=marek.behun@nic.cz \
--cc=pali@kernel.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox