Linux cryptographic layer development
 help / color / mirror / Atom feed
* [PATCH v1 0/4] crypto: stm32 - reuse for Ux500
@ 2022-11-19 22:12 Linus Walleij
  2022-11-19 22:12 ` [PATCH v1 1/4] dt-bindings: crypto: Let STM32 define Ux500 CRYP Linus Walleij
                   ` (3 more replies)
  0 siblings, 4 replies; 11+ messages in thread
From: Linus Walleij @ 2022-11-19 22:12 UTC (permalink / raw)
  To: linux-crypto, Herbert Xu, David S . Miller
  Cc: phone-devel, Stefan Hansson, Lionel Debieve, Maxime Coquelin,
	Alexandre Torgue, Linus Walleij

Experimenting by taking some small portions of the Ux500
CRYP driver and adding to the STM32 driver, it turns out
we can support both platforms with the more modern STM32
driver.

Upsides:

- We delete ~2400 lines of code and 8 files with intact
  crypto support for Ux500 and not properly maintained
  and supported.

- The STM32 driver is more modern and compact thanks to
  using things like the crypto engine.

Caveats:

- The STM32 driver does not support DMA. On the U8500
  this only works with AES (DES support is broken with
  DMA). If this is desired to be kept I can migrate
  it to the STM32 driver as well.

I have looked at doing the same for the Ux500 hash, which
is related but I am reluctant about this one, because
the Ux500 hardware has no interrupt and only supports
polling. I have a series of modernizations for that
driver that I have worked on and will think about how
to move forward.

Linus Walleij (4):
  dt-bindings: crypto: Let STM32 define Ux500 CRYP
  crypto: stm32 - enable drivers to be used on Ux500
  crypto: stm32/cryp - enable for use with Ux500
  crypto: ux500/cryp - delete driver

 .../bindings/crypto/st,stm32-cryp.yaml        |   32 +
 drivers/crypto/Makefile                       |    2 +-
 drivers/crypto/stm32/Kconfig                  |    4 +-
 drivers/crypto/stm32/stm32-cryp.c             |  334 +++-
 drivers/crypto/ux500/Kconfig                  |   10 -
 drivers/crypto/ux500/Makefile                 |    1 -
 drivers/crypto/ux500/cryp/Makefile            |   10 -
 drivers/crypto/ux500/cryp/cryp.c              |  394 ----
 drivers/crypto/ux500/cryp/cryp.h              |  315 ----
 drivers/crypto/ux500/cryp/cryp_core.c         | 1600 -----------------
 drivers/crypto/ux500/cryp/cryp_irq.c          |   45 -
 drivers/crypto/ux500/cryp/cryp_irq.h          |   31 -
 drivers/crypto/ux500/cryp/cryp_irqp.h         |  125 --
 drivers/crypto/ux500/cryp/cryp_p.h            |  122 --
 14 files changed, 315 insertions(+), 2710 deletions(-)
 delete mode 100644 drivers/crypto/ux500/cryp/Makefile
 delete mode 100644 drivers/crypto/ux500/cryp/cryp.c
 delete mode 100644 drivers/crypto/ux500/cryp/cryp.h
 delete mode 100644 drivers/crypto/ux500/cryp/cryp_core.c
 delete mode 100644 drivers/crypto/ux500/cryp/cryp_irq.c
 delete mode 100644 drivers/crypto/ux500/cryp/cryp_irq.h
 delete mode 100644 drivers/crypto/ux500/cryp/cryp_irqp.h
 delete mode 100644 drivers/crypto/ux500/cryp/cryp_p.h

-- 
2.38.1


^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2022-11-24 10:30 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-11-19 22:12 [PATCH v1 0/4] crypto: stm32 - reuse for Ux500 Linus Walleij
2022-11-19 22:12 ` [PATCH v1 1/4] dt-bindings: crypto: Let STM32 define Ux500 CRYP Linus Walleij
2022-11-23 16:13   ` Krzysztof Kozlowski
2022-11-23 21:35     ` Linus Walleij
2022-11-24  9:22       ` Krzysztof Kozlowski
2022-11-24 10:29         ` Linus Walleij
2022-11-19 22:12 ` [PATCH v1 2/4] crypto: stm32 - enable drivers to be used on Ux500 Linus Walleij
     [not found]   ` <b0b346ca-7b47-758a-c9e7-e7fda2b0856b@foss.st.com>
2022-11-21 14:05     ` Linus Walleij
2022-11-19 22:12 ` [PATCH v1 3/4] crypto: stm32/cryp - enable for use with Ux500 Linus Walleij
     [not found]   ` <8f55596e-12e3-8968-ebe5-e90be38ca5cb@foss.st.com>
2022-11-21 14:07     ` Linus Walleij
2022-11-19 22:12 ` [PATCH v1 4/4] crypto: ux500/cryp - delete driver Linus Walleij

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox