From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id B1F16C3DA7F for ; Tue, 30 Jul 2024 12:08:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Reply-To:List-Subscribe: List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: Content-Transfer-Encoding:Content-Type:Cc:To:Subject:Message-ID:Date:From: In-Reply-To:References:MIME-Version:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=YbJAwpxrKIzQfn1nWb8Lnx4AzupZPXhP4fCHpRlP/KI=; b=QciTVH06RSB2Xn 77nPgxv237Hn5gXiD2uAkwlIBUYT49NEC9nWQoL/AySb+7c4x3El1iUhIC8jRlfZDU+os3Rpeafdc cJ/7zPfJVb4gc45vKbNFZIM5xGVhl1FpnEGGfQowoIwIEfAzYYUHWBV7rOCWd3HktFjTywMzY8Uo8 2wlepOtf5Z3Tab/zi/LJtKWSoL54yGV4DGz/Zj/hnu3i5ybF4yPr1Kdj6MNLh120nmyISbZU9YesR b+7GhfuqF1Oc4EkVHmB2KOVcSEd0oaFQgAmAFd9OfwZHdaawiCE5Lmea1bLB9f8aCNq5hpGXQBIGf Hld87+6UKa0Q0drGtv9w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sYler-0000000F30s-2uA8; Tue, 30 Jul 2024 12:08:49 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sYleP-0000000F2tH-1nvR; Tue, 30 Jul 2024 12:08:22 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 5722D61E9F; Tue, 30 Jul 2024 12:08:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B7A71C4AF10; Tue, 30 Jul 2024 12:08:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1722341299; bh=pPjpBfbivKL6cAv5q8a1r5/0D4K3ehqMUNcKDTlaZW8=; h=References:In-Reply-To:Reply-To:From:Date:Subject:To:Cc:From; b=FhoKyhBwlE5KAF61bGSntzRr7kl53sTSu/xykZvfmLRgajXu3ecq9K2BPuXOpNMQG RJR+GKm6G/0Ox9UEp+ToWbP3PmBzRruOg5A8z7oOo1I+idyScmPoCtuklB+xGtTsJo xcCwVB7hM4omI4xl8AE2vvNiOgFqldoSwXtMZ1pG8GCfk0+ZRv7tooqUnHM/OGZEWZ hrk8ioBYhzHaOyBeyrr0FZcu8sKDWaBlixHe7BkhoN7/rmS2EnYFdO7duEtCaQMNci wsrst8amyTth0X5Twgby5vRpU1Mv1spZK0V7rVrx3qACqnGoSuC24lZ1LCV0F6Qx/r IXHMhZsZCTIUw== Received: by mail-lj1-f180.google.com with SMTP id 38308e7fff4ca-2f035ae1083so59562101fa.3; Tue, 30 Jul 2024 05:08:19 -0700 (PDT) X-Forwarded-Encrypted: i=1; AJvYcCXbNrh6zejJKoQmL7sIW7X1w5Nkb5N+L6D7dr2etTUyrUJwfnQ5EQMn2eqPKxwFK3BeeBw/grItSn3FabZkanZ42KF6RFMqmqMPC4r0gcZqz1g+/k5ZL/S/hl+0cWL9cPLZxisCyCAzy18ZMEAOZxvWCqmY8zlrobs= X-Gm-Message-State: AOJu0YxpZ7Om9B1J+lvxFf+1znRooPVbreje3mhwsxvD5iFfpjMZMmOo vpjHVxR7Vg5l/NWFbruZQJkJNFPSOeGyunlPrIUDvzE7u2hzZKVb6XXqzcrzF/uqh3SJfg45Vnx 9IzlfAX3HVgVQHU+ZHDHPM3OnL10= X-Google-Smtp-Source: AGHT+IEew2ptwjzerzes/DjMQPGgSwoLU7EI7pt/rY+1Yqs+CFA3dSUw8u2GOoxP5Z1uV8X2YApMbOoHS69Zl0l9/D8= X-Received: by 2002:a2e:91d4:0:b0:2ef:1f68:eae1 with SMTP id 38308e7fff4ca-2f12ee077famr71560271fa.17.1722341298040; Tue, 30 Jul 2024 05:08:18 -0700 (PDT) MIME-Version: 1.0 References: <6690040.iosknibmi9@bagend> <17577153.5WZRyvrzyv@diego> In-Reply-To: <17577153.5WZRyvrzyv@diego> From: Chen-Yu Tsai Date: Tue, 30 Jul 2024 20:08:04 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v7 0/3] hwrng: add hwrng support for Rockchip RK3568 To: =?UTF-8?Q?Heiko_St=C3=BCbner?= Cc: Dragan Simic , Daniel Golle , Diederik de Haas , linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org, Rob Herring , Conor Dooley , linux-kernel@vger.kernel.org, Herbert Xu , Martin Kaiser , Sascha Hauer , Sebastian Reichel , Ard Biesheuvel , =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , devicetree@vger.kernel.org, linux-crypto@vger.kernel.org, Philipp Zabel , Olivia Mackall , Krzysztof Kozlowski , Aurelien Jarno Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240730_050821_620069_D672228A X-CRM114-Status: GOOD ( 30.59 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: wens@kernel.org Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Jul 30, 2024 at 6:37=E2=80=AFPM Heiko St=C3=BCbner wrote: > > Am Dienstag, 30. Juli 2024, 11:03:06 CEST schrieb Diederik de Haas: > > On Tuesday, 30 July 2024 01:18:37 CEST Daniel Golle wrote: > > > On Wed, Jul 24, 2024 at 08:07:51AM +0200, Dragan Simic wrote: > > > > Thanks a lot for the testing. Though, such wildly different test r= esults > > > > can, regrettably, lead to only one conclusion: the HWRNG found in = RK3566 > > > > is unusable. :/ > > > > FTR: I agree with Dragan, unfortunately. > > > > > The results on RK3568 look much better and the series right now also > > > only enabled the RNG on RK3568 systems. However, we have only seen fe= w > > > boards with RK3568 up to now, and I only got a couple of NanoPi R5C > > > here to test, all with good hwrng results. > > > > > > Do you think it would be agreeable to only enable the HWRNG for RK356= 8 > > > as suggested in this series? Or are we expecting quality to also vary > > > as much as it (sadly) does for RK3566? > > > > Unless we get *evidence* to the contrary, we should assume that the HWR= NG on > > RK3568 is fine as the currently available test results are fine. > > So I think enabling it only for RK3568 is the right thing to do. > > > > So a 'revert' to v7 variant seems appropriate, but with the following c= hanges: > > - Add `status =3D "disabled";` property to the definition in rk356x.dts= i > > - Add a new commit where you enable it only for rk3568 and document in = the > > commit message why it's not enabled on rk3566 with a possible link to t= he v7 > > thread for clarification on why that is > > I was going to protest about the "disable" until reading the 2nd part :-D= . > > And yeah that makes a lot of sense, "add" it to rk356x.dtsi, as the IP is > part of both variants, but only enable it in rk3568.dtsi because of the > seemingly faulty implementation on the rk3566. Better yet, mark it as "broken" in rk3566.dtsi to reflect the tests that we've all done. ChenYu > > You could probably also integrate that into 1 commit, but make sure tha= t the > > commit summary and description match the implementation. > > IMO that wasn't 'technically' the case in v8 as the rng node was added = to > > rk356x, but it was only enabled on rk3568. > > > > My 0.02 > > > >