From: Thorsten Blum <blum@kernel.org>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Thorsten Blum <blum@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: "Guenter Roeck" <linux@roeck-us.net>,
"Wensheng Wang" <wenswang@yeah.net>,
"Frank Li" <Frank.Li@nxp.com>,
"Cosmo Chou" <chou.cosmo@gmail.com>,
"Colin Huang" <u8813345@gmail.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Dixit Parmar" <dixitparmar19@gmail.com>,
"Antoni Pokusinski" <apokusinski01@gmail.com>,
"Eddie James" <eajames@linux.ibm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] crypto: atmel-ecc - add support for atecc608a
Date: Mon, 31 Aug 2026 00:01:52 +0200 [thread overview]
Message-ID: <20260830220151.21469-4-blum@kernel.org> (raw)
In-Reply-To: <20260830220151.21469-3-blum@kernel.org>
The driver already supports the ATECC508A and ATECC608B and uses only
commands shared by these devices.
Microchip documents the ATECC608B as a backwards-compatible, functional
drop-in replacement for the ATECC608A, with the same device structure
and command interface [1]. Therefore, add support for the ATECC608A.
ATECC608A hardware was not available for testing.
Signed-off-by: Thorsten Blum <blum@kernel.org>
Link: https://ww1.microchip.com/downloads/en/Appnotes/Migrating-from-the-ATECC608A-to-the-ATECC608B-DS40002237A.pdf [1]
---
drivers/crypto/atmel-ecc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/crypto/atmel-ecc.c b/drivers/crypto/atmel-ecc.c
index 075f38a67935..0904bb47fd0a 100644
--- a/drivers/crypto/atmel-ecc.c
+++ b/drivers/crypto/atmel-ecc.c
@@ -348,6 +348,7 @@ static void atmel_ecc_remove(struct i2c_client *client)
static const struct of_device_id atmel_ecc_dt_ids[] = {
{ .compatible = "atmel,atecc508a", },
+ { .compatible = "atmel,atecc608a", },
{ .compatible = "atmel,atecc608b", },
{ }
};
@@ -355,6 +356,7 @@ MODULE_DEVICE_TABLE(of, atmel_ecc_dt_ids);
static const struct i2c_device_id atmel_ecc_id[] = {
{ .name = "atecc508a" },
+ { .name = "atecc608a" },
{ .name = "atecc608b" },
{ }
};
next prev parent reply other threads:[~2026-08-30 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 22:01 [PATCH 1/2] dt-bindings: trivial-devices: add atmel,atecc608a Thorsten Blum
2026-08-30 22:01 ` Thorsten Blum [this message]
2026-08-30 22:10 ` [PATCH 2/2] crypto: atmel-ecc - add support for atecc608a sashiko-bot
2026-08-31 16:19 ` [PATCH 1/2] dt-bindings: trivial-devices: add atmel,atecc608a Conor Dooley
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=20260830220151.21469-4-blum@kernel.org \
--to=blum@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=apokusinski01@gmail.com \
--cc=chou.cosmo@gmail.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dixitparmar19@gmail.com \
--cc=eajames@linux.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nicolas.ferre@microchip.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=u8813345@gmail.com \
--cc=wenswang@yeah.net \
/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