Received: by 2002:a05:6a10:6006:0:0:0:0 with SMTP id w6csp599119pxa; Thu, 27 Aug 2020 10:26:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzzhDq0GuPXbLsVZvepFr4uv36YPKObIT7/x9Ptn/qh+BuxloemLUE1WEZscVNioLn5BwJV X-Received: by 2002:a17:906:b28f:: with SMTP id q15mr5118390ejz.129.1598549169341; Thu, 27 Aug 2020 10:26:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1598549169; cv=none; d=google.com; s=arc-20160816; b=aWABYPkjIQLYj2ck9WaIzhVE8RZokNEOGgVS3oIu+1CerdlBYvJcGQEYCq79EO1/x2 vdVqOT2SuQ/R2W4lGKYp3YGrNwkgLd2sw9YknbAMSlx6Zsreo2GltInFXt62awT3Cu44 RExDdcTJFjWYxDgjuBkCveg0PIFOcjY199MgA2yKdBF6oezhwhsA1rgN2aFQ9VwIFZS7 rvQGkfCKLPgfOThC7VqdvNyIOpU5x7v9b1raaD5mzYp5JqjOHpxGPeykQgvjUc/6T+PW kuZE1Ze/S9hu2H/jz45+d9hs1BmzV/DXGrOXPQ0NrZbjIW10SQS3Omu7r7GueYUkDtKA y27w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:reply-to:from:date; bh=F1LKdfnd0WmHy3UZG8nY63+NGonqpN1tzUssm95oaJM=; b=Ptm2IiKvkkiiBSJKnNhgAmm0iQxnQEW9LcA5xnQC3CRZd1dAM7R0ZCvR3L9WxkujJR tTImmYzj37/gxRJNGBdiqxpWp4RHh8GqquQZW9SnL6Lmtnd+eXHtB3re8PA+5va9LvWv W873M8T7klTvE5yy0pQMfDr8NT8nmemGS0sG+S6m8jfIsymSoUVgzY5JriUw5OjtTaRi EWnvvnoZKLOkb3YGduJ5b2OrSCo9o/kfsbjBgUEVkYU9zg5eLVALgUUSNayQ0RJdXpjw ZOqOJK/CTPCjTVm4gbmcMOqxlflWk4g+BjhLBws4WtJxGr5NGxE81S7Ql2vR0JnVjQtj xLfw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w19si1847831eds.303.2020.08.27.10.25.36; Thu, 27 Aug 2020 10:26:09 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726232AbgH0RZe (ORCPT + 99 others); Thu, 27 Aug 2020 13:25:34 -0400 Received: from gw.c-home.cz ([89.24.150.100]:41048 "EHLO dmz.c-home.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726157AbgH0RZe (ORCPT ); Thu, 27 Aug 2020 13:25:34 -0400 Received: from dmz.c-home.cz (localhost [127.0.0.1]) by dmz.c-home.cz (8.14.4+Sun/8.14.4) with ESMTP id 07RHN0fg019155; Thu, 27 Aug 2020 19:23:05 +0200 (CEST) Received: from localhost (martin@localhost) by dmz.c-home.cz (8.14.4+Sun/8.14.4/Submit) with ESMTP id 07RHMrKp019152; Thu, 27 Aug 2020 19:22:53 +0200 (CEST) X-Authentication-Warning: dmz.c-home.cz: martin owned process doing -bs Date: Thu, 27 Aug 2020 19:22:53 +0200 (CEST) From: Martin Cerveny Reply-To: Martin Cerveny To: Corentin Labbe cc: Martin Cerveny , Maxime Ripard , Chen-Yu Tsai , linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [SOLVED] Re: PROBLEM: SHA1 on Allwinner V3s failed In-Reply-To: <20200826115209.GA830@Red> Message-ID: References: <20200826090738.GA6772@Red> <20200826115209.GA830@Red> User-Agent: Alpine 2.00 (GSO 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Ok. I will send patch ASAP. Regards, Martin On Wed, 26 Aug 2020, Corentin Labbe wrote: > On Wed, Aug 26, 2020 at 01:33:20PM +0200, Martin Cerveny wrote: >> Hello. >> >> On Wed, 26 Aug 2020, Corentin Labbe wrote: >>> On Wed, Aug 26, 2020 at 09:52:30AM +0200, Martin Cerveny wrote: >>>> Hello. >>>> >>>> [1.] One line summary of the problem: >>>> >>>> SHA1 on Allwinner V3s failed >>>> >>> Since only SHA1 is failling, could you try to use the "allwinner,sun8i-a33-crypto", just in case V3s has the same SHA1 HW quirck than A33. >> >> Yes. This do the trick. All startup verification passes now. >> Performance (SHA1 with sha1-sun4i-ss) "tcrypt mode=303 sec=1" test output attached. >> So, all seems to be working now. Released new patch with possibility to merge. >> >> https://github.com/mcerveny/linux/commit/e3c76436de3d8cd2b2ddaeadef879a4a4d723bf4 >> >> Regards, Martin > > For proper solution, a new compatible "allwinner,sun8i-v3s-crypto" should be added instead. > Furthermore it should be added in sun4i-ss-core.s along with a new variant for v3s with .sha1_in_be = True. > > The new compatible should also be added in Documentation/devicetree/bindings/crypto/allwinner,sun4i-a10-crypto.yaml > > Regards >