Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp567172rwb; Tue, 27 Sep 2022 01:13:41 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6bwMvJjbpUnb5jTEgN6HiIF7I9dq1Q86iBJKuIiCOpXI8jMB7uuQjGjiJFyN2QyIs1v31T X-Received: by 2002:a17:906:847b:b0:773:db0f:d533 with SMTP id hx27-20020a170906847b00b00773db0fd533mr22155911ejc.0.1664266421495; Tue, 27 Sep 2022 01:13:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664266421; cv=none; d=google.com; s=arc-20160816; b=xWFVfduH66TTNbJZN1STLahZMkF+nNsz1T7I6V+vEjgU15XAHUDWFt0Duf6f3LdZJP KNaldpoktqIwxzLIYrO+Ank1xYWjlJJSw+dhgIoljLnW4X4xxsq1UQW3UKW9zboObUHT wZXHo+yzT5+EuKxTAgo8rLsWfJtqsAOSTWLjGjwFUscvUbkse2Rms6ANFnn8DnDasU49 dIw9n0hlQvzzqhBaXzfegcJ5dVD40KbgQgL0/PqO9xbEVHlIYN1xhUp9RlEVBTgVmqTh 2cbLVJWuMZBHViKp4S9hvCkWw0Jllr9gbLY/aRZJaW7vOZlbghJ6iyQRa5qrdt6etRbB b1LA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=Lbh/c4vCkGtXonzdpXdp4XQ0sSxf7/y8kx7FY8V2Teo=; b=vkp6XS+OV51zH5WlyUiWqjw6h1OpGYDnBLhp4XXLUiJ6DgZ2ZVbS/tl5OcKPFIehpm lNHZAu5g5n7rSvaQEi6loO21YDTQFSaoig648DDARxdBWqEq4dzuSUV1uvrfiH+sNwhz pCYtFCnA3xhJ18rNXKV9p8q7YPPtXV0Is5krUdnQdLiOTnuxt9bszR+0pd3k0h2qohjH E0Uh1zYhRvjZQxjd4G1uBF+O+nMYqx6FxFd4tItJISpyG+VgMctNb7V+o5ijhZiNVF3N ddNuJ9LrczbHnEvgtI84CCYjsFqxnR2M3Z7qNEDFh4FRkVS0NR9uGu6lRYUp5EtOuesd TUpQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=BPWFqeFE; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hq40-20020a1709073f2800b00783e7d72fc0si877008ejc.272.2022.09.27.01.13.17; Tue, 27 Sep 2022 01:13:41 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=BPWFqeFE; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231691AbiI0IHk (ORCPT + 99 others); Tue, 27 Sep 2022 04:07:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35440 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231706AbiI0IHX (ORCPT ); Tue, 27 Sep 2022 04:07:23 -0400 Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B2B4FF34C6 for ; Tue, 27 Sep 2022 01:01:52 -0700 (PDT) Received: by mail-wm1-x32e.google.com with SMTP id i203-20020a1c3bd4000000b003b3df9a5ecbso8916919wma.1 for ; Tue, 27 Sep 2022 01:01:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date; bh=Lbh/c4vCkGtXonzdpXdp4XQ0sSxf7/y8kx7FY8V2Teo=; b=BPWFqeFE/urWJLLIaffyOd62/9aionydmnuP+9XMmZJffpqDs6QmZ/24AkuJ3D7N84 ByyBfct8LiRIIoyZDV3HMUi2jYHyTutDESS42723sHZikNFRK4kLjyTW/USb2BUiQ62r DZTlUdoqciHoSoHPfhYhnuY1IOWe2MO+E9yVo8TRCi7jNRkAgWWpDJ0pogSk9WnIPWa1 P0iLnnUs45yJhQOHL96REtFFMBQ1EkGWklMdv6M8YzSldMPZ6WWoUbFiM+BcJyE74VrK qLR8yhFB4nqn/2R2RSy2y/GnCP3+Yl5J9YPCOuS85oryBpOs39PYU5ik7ebJy8oeIWOr bd2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date; bh=Lbh/c4vCkGtXonzdpXdp4XQ0sSxf7/y8kx7FY8V2Teo=; b=QMg5/+BHtT2hsy52DA4QhqW/ne1DZiOMIR39Jx+ezngkXF+wErk7PJPUBZk/QDxBc+ kGxj/ksadaqcIO8YBzWYAbjG8+uSOFpGxoZKZti9agL1VLAxFg4BClD1T3+0N3Bh7Y5H ABDxrQ2oxE4clqKURSkm9yPifBDx0M18XdqSxGgzwwIKuxS1VmaiYgrZLEytcPzJ2lPN Nj+w3CBXiBpcRPrsIIVB1OMQRi/MSZ47h2/u1CKcvfIq4JHLJGcPyuMTJFEgTp4CnScA D0n0VEf3Z+cMNyueupG+h5PHQDRuknL+PWI4EsKdhAD6XmjdIpqYzlsEyQM+92WB2VXU bamA== X-Gm-Message-State: ACrzQf0au5ID7TUwrvD6bVT1Z6sOOJusjTGK5dVYGO7w5UoBPnNbdBT1 ISFpquhagNhTM9c7MCceyMlnww== X-Received: by 2002:a7b:ce08:0:b0:3b4:ff9b:3d89 with SMTP id m8-20020a7bce08000000b003b4ff9b3d89mr1639769wmc.31.1664265666615; Tue, 27 Sep 2022 01:01:06 -0700 (PDT) Received: from localhost.localdomain (laubervilliers-658-1-213-31.w90-63.abo.wanadoo.fr. [90.63.244.31]) by smtp.googlemail.com with ESMTPSA id p4-20020a1c5444000000b003a5c7a942edsm13357199wmi.28.2022.09.27.01.01.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 27 Sep 2022 01:01:05 -0700 (PDT) From: Corentin Labbe To: heiko@sntech.de, davem@davemloft.net, herbert@gondor.apana.org.au, krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org, Corentin Labbe Subject: [PATCH RFT 0/5] crypto: rockchip: add crypto offloader V2 Date: Tue, 27 Sep 2022 08:00:43 +0000 Message-Id: <20220927080048.3151911-1-clabbe@baylibre.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hello Rockchip rk3568 and rk3588 have a common crypto offloader IP different than rk3228 one. I started to work the driver for this IP on a rk3588 based board, but this SoC is still not upstream. So it is why I send this serie asking for test since I own no rk3568 and I need to be sure datasheet is right. Note: I keeped all rk3588 reference intentionaly, but probably it will need to be removed until this SoC was upstream. Regards Corentin Labbe (5): crypto: rockchip: move kconfig to its dedicated directory dt-bindings: crypto: add support for rockchip,crypto-rk3588 MAINTAINERS: add new dt-binding doc to the right entry crypto: rockchip: support the new crypto IP for rk3568/rk3588 ARM64: dts: rk3568: add crypto node .../crypto/rockchip,rk3588-crypto.yaml | 71 ++ MAINTAINERS | 1 + arch/arm64/boot/dts/rockchip/rk3568.dtsi | 14 + drivers/crypto/Kconfig | 32 +- drivers/crypto/Makefile | 2 +- drivers/crypto/rockchip/Kconfig | 56 ++ drivers/crypto/rockchip/Makefile | 5 + drivers/crypto/rockchip/rk3588_crypto.c | 646 ++++++++++++++++++ drivers/crypto/rockchip/rk3588_crypto.h | 221 ++++++ drivers/crypto/rockchip/rk3588_crypto_ahash.c | 346 ++++++++++ .../crypto/rockchip/rk3588_crypto_skcipher.c | 340 +++++++++ 11 files changed, 1703 insertions(+), 31 deletions(-) create mode 100644 Documentation/devicetree/bindings/crypto/rockchip,rk3588-crypto.yaml create mode 100644 drivers/crypto/rockchip/Kconfig create mode 100644 drivers/crypto/rockchip/rk3588_crypto.c create mode 100644 drivers/crypto/rockchip/rk3588_crypto.h create mode 100644 drivers/crypto/rockchip/rk3588_crypto_ahash.c create mode 100644 drivers/crypto/rockchip/rk3588_crypto_skcipher.c -- 2.35.1