Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp1705612rwb; Thu, 29 Sep 2022 00:40:27 -0700 (PDT) X-Google-Smtp-Source: AMsMyM54EOzBnZ0E8ASWdkL3q5/Ri2W7EspGlMoS+7NMn5Z1b2qWTiDPfCKnq2fnQDZ/Z8niaPQC X-Received: by 2002:a17:907:6288:b0:72f:90ba:f0b2 with SMTP id nd8-20020a170907628800b0072f90baf0b2mr1566002ejc.696.1664437227604; Thu, 29 Sep 2022 00:40:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664437227; cv=none; d=google.com; s=arc-20160816; b=ETiLkD7vPQMz5edLIl9o3BaGPJOZl1pEYOhrEryXyOS3HF5SwATdmK1gqg0PX61AIR ObTlMRzwx7LCLvSNmgGXgLAhFpwMovbtyhUpR8iLpfEzOHSPejC56o3y/2q7Ciz+E4iF VKoY0FUKech5R/h0yrUu5zSJOxsjzkH6F24DgoJLSaKOuIjjPvq2bee8nAWAcxAH55K7 E2FLt/2q7/59Yo5f+0T+lkYoQAloAeXogpclQ28A7dXeGid2C0KIF6HDLPOI9DD6MHNQ X/dG5Cvp1B71kUHKRXpOLcAbahDYdPfQVgiZQ0587GaQORRieLCfLt/Y43elS2fTKECL U7hA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:to :from:date:dkim-signature; bh=atACqxLtygvoatmuSiOUnja6i+2u6x+rxoy2apBcCBk=; b=CS88vEijJrtnSqLkQle4n5MbOcGFd73Wi2R5zkgmdr61tYI35DKuxyUBk+Wzd9vFdp wX4fiPH06S0mEn/tbjo0WOYPxI2Qk4fZvOt+vZpXz8GqQ4EAt+YodeL5Y+mCsyv5ZTYy 3o/o1xWdcBsccyawXmwIwFbs2OG2rcrCAH8Pr05joCMVY851ZI7zIl8ndMZyWHjjfPzM I6q8f1jmphhTKS8hDdLT081Vngeodtr7Uki7m8Jyqw2cygiN9DTSgXnpZIHHVGHp2Ni5 p1fMLdCzivgt5oJF7ubLmoATX29YyQq+immm73pC9M9HvqlEwAGrycweiJASY7BLCqbU Cx3g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=hsOEJmFh; 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 bq6-20020a170906d0c600b007837bab66fasi6898128ejb.557.2022.09.29.00.39.54; Thu, 29 Sep 2022 00:40:27 -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=hsOEJmFh; 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 S235314AbiI2Hdp (ORCPT + 99 others); Thu, 29 Sep 2022 03:33:45 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57130 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235274AbiI2Hdf (ORCPT ); Thu, 29 Sep 2022 03:33:35 -0400 Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 322C1138F0D for ; Thu, 29 Sep 2022 00:33:33 -0700 (PDT) Received: by mail-wr1-x430.google.com with SMTP id v28so777091wrd.3 for ; Thu, 29 Sep 2022 00:33:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:to:from:date:from:to:cc :subject:date; bh=atACqxLtygvoatmuSiOUnja6i+2u6x+rxoy2apBcCBk=; b=hsOEJmFhBKFbH0GhXrJKHUxne+LtxAIa76tyBJcZVLXdKpf4nNr26PhlcBT0DRGqsm u4nuyhxyohof8xdQKBda/RvQmhKqfjCx8qM5PEasl4ZvbvmxGbni5+mHouFrF/43VcRM pSBwbvxUWK4SSh9wc+kYLKRJUXOx4r1Nb3x51OvHtGu+/6qrLq3Ug5Vebf5RDlo+FDcU LHybNFRvEDSCPfiDF0nKF+DPjqPto6PRCqG7jkfKwHgg3dgAISMTNaYA+qTCvDg9zqQG CF0s8xmsf/Tbm4azqMxygMUlqueRh71Bd8kORz1GFVoFS69QrqS4/VZdBmHwIj0bEbLq ClDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:to:from:date :x-gm-message-state:from:to:cc:subject:date; bh=atACqxLtygvoatmuSiOUnja6i+2u6x+rxoy2apBcCBk=; b=O1bymPGQY1ZWLbKgm8EtvIb36UAawHb1pvcEQFbSpfZq7tItvJQvPMKMN5QNwa0aeX cPTm0HfiVeKo05YEIMzQm3Ww/7DgiEnNf80rxEzPaAqrOZZuSNoz8sruuyDo7r+FdXeW U0YRRRaBqE0A3VfdP7zAmF/XPR9rRiVpYiVzIZq3+oJgD8R26nh80/qMx77tUwfX+AiD 0IAoQVnnMhCbyHxkwfbcZ5j6uiJxY6GENXNRGOVHnUnmQArSnZvo/jEQSpADuFifDk1W BGh2b6Qm4gycUw9C3V0nbq9T/vbBNKidlnTTnUDO4m/lKEHaqo/hfML5qNCqBM6297nm CK+g== X-Gm-Message-State: ACrzQf0CzEuJN1KpYh+xqZMLeGWgOZx7ea2RDjADTk1dxyF8XblvUHhK BK1tSA4E0g1ZwtSqVW5Hbcaa7A== X-Received: by 2002:a5d:4c4c:0:b0:22c:cb1f:f7dc with SMTP id n12-20020a5d4c4c000000b0022ccb1ff7dcmr1077874wrt.504.1664436811363; Thu, 29 Sep 2022 00:33:31 -0700 (PDT) Received: from Red ([2a01:cb1d:3d5:a100:264b:feff:fe03:2806]) by smtp.googlemail.com with ESMTPSA id u4-20020adff884000000b0022a2dbc80fdsm5950328wrp.10.2022.09.29.00.33.30 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 29 Sep 2022 00:33:30 -0700 (PDT) Date: Thu, 29 Sep 2022 09:33:27 +0200 From: LABBE Corentin To: heiko@sntech.de, davem@davemloft.net, herbert@gondor.apana.org.au, krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org, 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 Subject: Re: [PATCH RFT 0/5] crypto: rockchip: add crypto offloader V2 Message-ID: References: <20220927080048.3151911-1-clabbe@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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=unavailable 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 Le Tue, Sep 27, 2022 at 11:34:58PM +0200, Aurelien Jarno a ?crit : > On 2022-09-27 08:00, Corentin Labbe wrote: > > 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. > > I did a quick test, and it doesn't seem to work. I get: > > rk3588-crypto fe380000.crypto: DMA timeout > rk3588-crypto fe380000.crypto: DMA timeout > > That's on an ODROID-M1 board, so with the set of patches I sent > yesterday to support it. Thanks for testing it, probably I did something wrong because I got a successfull test by someone on #linux-rockchip. But I dont know on which board it is, and it was on my debug tree, so probably cleaned something wrong before sending the patchs. If I sent you a link to my tree, could you retry ? Regards