public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lothar Rubusch <l.rubusch@gmail.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
	claudiu.beznea@tuxon.dev, linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, l.rubusch@gmail.com
Subject: [PATCH v2 0/4] crypto: atmel-sha204a - read out otp zone
Date: Fri,  3 May 2024 21:10:50 +0000	[thread overview]
Message-ID: <20240503211054.1231-1-l.rubusch@gmail.com> (raw)

Read out otp memory zone of this secure eeprom and rng chip. The chip
has an otp zone and data zone, both still not accessed. The otp zone
can be used to store persistently serial numbers or similar, if externally
pre-configured. In any way the Atmel SHA204a needs to be preconfgured and
fuse locked in order to be useful also for the already implemented RNG
functionality. Placing data into the otp zone is optional. If empty, the
chip returns 0xff on all field. The implementation passes the content to
a new sysfs handle to userspace. If the chip is locked or not accessible
no sysfs handle is set.

Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
---
v1 -> v2
- fix typo in commit title
- drop patch: remove unused includes

Lothar Rubusch (4):
  crypto: atmel-i2c - add missing arg description
  crypto: atmel-i2c - rename read function
  crypto: atmel-sha204a - add reading from otp zone
  crypto: atmel-sha204a - provide the otp content

 drivers/crypto/atmel-i2c.c     | 30 +++++++++++++--
 drivers/crypto/atmel-i2c.h     |  8 +++-
 drivers/crypto/atmel-sha204a.c | 68 ++++++++++++++++++++++++++++++++++
 3 files changed, 102 insertions(+), 4 deletions(-)

-- 
2.25.1


             reply	other threads:[~2024-05-03 21:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 21:10 Lothar Rubusch [this message]
2024-05-03 21:10 ` [PATCH v2 1/4] crypto: atmel-i2c - add missing arg description Lothar Rubusch
2024-05-03 21:10 ` [PATCH v2 2/4] crypto: atmel-i2c - rename read function Lothar Rubusch
2024-05-03 21:10 ` [PATCH v2 3/4] crypto: atmel-sha204a - add reading from otp zone Lothar Rubusch
2024-05-03 21:10 ` [PATCH v2 4/4] crypto: atmel-sha204a - provide the otp content Lothar Rubusch
2024-05-10  9:23 ` [PATCH v2 0/4] crypto: atmel-sha204a - read out otp zone Herbert Xu

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=20240503211054.1231-1-l.rubusch@gmail.com \
    --to=l.rubusch@gmail.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@microchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox