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 053F4C36002 for ; Wed, 9 Apr 2025 10:35:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:CC:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=XfJBdscMAuy5EECJZSerJxBpkDTViYEqbsATQalfosg=; b=gDvMKF+mxq793xEJIDGXtNELEo zuluYUaca6Wzpl3JMoo/1ixart506ne200vDsqTLVuKBRkydHjRmXr0IvQ5Vv47c55sjliSVEgAiM pSlTEdCc/HUEvj/QOEuz1h0g5cY7aPdoCXXKA2MfF/DmAeSoy7oXKZWu2ft0ueA1uMmyQ7Wled7zM po+RUw6rJwNo51VeI/vmYZXVxjyU5+ZsJbvAHo6e6MWQdPsoLGg0iXRz5u7a4VIcAIZh5gYTtxw2F eHMuKpgRgjp1/bxsKMNoHovFlPqczPqlnQYocqzEjIIexRwmVsLqwhpcFbUcN05x+8ekS16oZ//ms 7P7qsFLA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1u2Slp-00000006qoP-2qL5; Wed, 09 Apr 2025 10:35:01 +0000 Received: from lelvem-ot01.ext.ti.com ([198.47.23.234]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1u2Sk2-00000006qOe-0WON for linux-arm-kernel@lists.infradead.org; Wed, 09 Apr 2025 10:33:11 +0000 Received: from lelv0266.itg.ti.com ([10.180.67.225]) by lelvem-ot01.ext.ti.com (8.15.2/8.15.2) with ESMTPS id 539AX57Y953872 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 9 Apr 2025 05:33:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1744194785; bh=XfJBdscMAuy5EECJZSerJxBpkDTViYEqbsATQalfosg=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=npCcLBSEFWz4wtrE6nTraC7XfFfo6JTsKc9LjoUpIkuthwzoCXpb+MVSiMPU97sSr bnBoi9STFfjYSD5W0s6pgr2cU1HStCmC9nIuIE0Bzd/7CX6BSG9tyw1lBBgzg18dIC 8Nih9YBBgJCY5nD776dTh+WbAgtmh3UMVbGVKm/A= Received: from DLEE103.ent.ti.com (dlee103.ent.ti.com [157.170.170.33]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 539AX5ih094021 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 9 Apr 2025 05:33:05 -0500 Received: from DLEE103.ent.ti.com (157.170.170.33) by DLEE103.ent.ti.com (157.170.170.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Wed, 9 Apr 2025 05:33:04 -0500 Received: from lelvsmtp6.itg.ti.com (10.180.75.249) by DLEE103.ent.ti.com (157.170.170.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Wed, 9 Apr 2025 05:33:04 -0500 Received: from localhost (uda0497581-hp.dhcp.ti.com [172.24.227.253]) by lelvsmtp6.itg.ti.com (8.15.2/8.15.2) with ESMTP id 539AX45A026841; Wed, 9 Apr 2025 05:33:04 -0500 Date: Wed, 9 Apr 2025 16:03:03 +0530 From: Manorit Chawdhry To: Michael Walle CC: "Kumar, Udit" , Nishanth Menon , Vignesh Raghavendra , Tero Kristo , Rob Herring , Krzysztof Kozlowski , Conor Dooley , , , Subject: Re: [PATCH] arm64: dts: ti: k3-am62p-j722s: add rng node Message-ID: <20250409103303.dkrrvp7mdctx32pd@uda0497581-HP> References: <20250313144155.2382316-1-mwalle@kernel.org> <837cba5f-f49e-4cbf-9cbe-2b25f7c9d4b8@ti.com> <1ad2d8c2-6a0d-419d-984d-4974adb0e1f0@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-C2ProcessedOrg: 333ef613-75bf-4e12-a4b1-8e3623f5dcea X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20250409_033310_269996_9A449408 X-CRM114-Status: GOOD ( 25.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: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Michael, On 13:09-20250401, Michael Walle wrote: > Hi Udit, > > > > > > > > --- a/arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi > > > > > > > [..] > > > > > > For completeness , this is ok to add this node but > > > > > > should be kept disabled > > > > > Shouldn't it be "reserved" then, see [1]. > > > > yes, should be reserved. > > > > > > > > With marking status as reserved. > > > > > > > > Please use Reviewed-by: Udit Kumar > > > Thanks. > > > > > > > > > similar to > > > > > > > > > > > > https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/ti/k3-j7200-mcu-wakeup.dtsi#L662 > > > > > j784s4, j721e and j721s2 have them enabled. What is the rule here? > > > > J784s4, j721e and j721s2 SOCs has two TRNG blocks, > > > > > > > > example for j721e, one is used by kernel [0] and another by > > > > optee [1]. > > > > > > > > > > > > > You also disable the hwrng in optee in your evm according to [2]: > > > > > CFG_WITH_SOFTWARE_PRNG=y > > > > We are planning to use this hardware block by secure firmware. > > > > > > > > Therefore request not to use by optee as well > > > How will you be able to access the RNG from linux and u-boot? I'm > > > asking because I'll need it in u-boot for the lwip stack and the > > > HTTPS protocol. > > > > For now,  If you need TRNG then I can suggest to use optee TRNG (ie > > build > > optee with HW TRNG). > > I'll be using an uboot TRNG driver. But how will that work in > the future if the RNG is used by the secure firmware? Wondering if this would be of interest to you [0]. I think since this device only has one TRNG, there has to be a master around and we can mitigate that from OP-TEE as of now, incase anything changes in future then the communication channel between OP-TEE and the secure firmware can be established but currently it's still at work. I think the best way to go forward is to get the numbers from OP-TEE atm IMHO. [0]: https://github.com/u-boot/u-boot/blob/master/drivers/rng/optee_rng.c Regards, Manorit > > -michael