Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp15273931ybl; Tue, 31 Dec 2019 04:53:26 -0800 (PST) X-Google-Smtp-Source: APXvYqwFfogJgW6GvXmles7sKeR3Fsa3RiLnF51xsnynBa28G57xHm2XFkZseGMM4F7shG/eeQnF X-Received: by 2002:a9d:7519:: with SMTP id r25mr70511403otk.284.1577796806346; Tue, 31 Dec 2019 04:53:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577796806; cv=none; d=google.com; s=arc-20160816; b=o+E8Kwzx6mYo0+NMXdjnQQygEXFiSR13gEuqsDtBvLLz6md8SsVgtmxCF1AXieAiU8 V+xNHL48b57KmsUnnfpqyBkOkEOEnXRLy5N3jVJKHiVkmfXtSIJyX5Mx65RT5JWKnIPw LYKxpg69j08idp5f/Hs7LqtscuhJ6wm6vH6y3t9Cr/JdQN5m8+l7TaNIddl0/CiqB9r5 H7twbfCRR5zVdt5i7ITXn1L8MZCtmg1kt0YrkNXfZxRNeNlmVQ52gxgLO7s1HclHBBP9 wRfReHlwY6IUuuFcINvnQMveA/3SCx3SlzJ0/rlD5XHE492DWyA5dY/GA1ZE6IzhVrRm 3mgA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=aBhOARcicbiRL8oIBJ+zhmMwQC2n51nOUXKMXbfqIgA=; b=se5gEvaOivnOPeDl25k2DvwYy0M59jevys1BZRm1LY1LzNR7sFfoxLgfCT63QbSMqS 8RE3FHV9q6GpJCKWvHZqQnMpYaTdCQDj6gOlVrkLuRkcfzNCvyqdvVVR1Bsg8W0EyUz7 tAillrFIxh4EsJFk3EcjGUh3+8bjrzl4eVqm9RUPBW8z+6vkzGznkjDE9I7QGBnZ0eRW AosSdT+9P3YjO6swwLNgZ/HCbqbz1csrcgNQurTYfNR+AcqOL3zUjakB5uRmlQ/yJeDz wV2kNUBRgr2LcnZ7P0zfVFvdXNcb4RDe9q7BvPDfaZ1A4bqKNm1diLGlrWzQt75qull+ 1rHA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@chronox.de header.s=strato-dkim-0002 header.b=d0AW4pGf; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m7si13282897oih.7.2019.12.31.04.52.52; Tue, 31 Dec 2019 04:53:25 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@chronox.de header.s=strato-dkim-0002 header.b=d0AW4pGf; spf=pass (google.com: best guess record for domain of linux-crypto-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726673AbfLaMrs (ORCPT + 99 others); Tue, 31 Dec 2019 07:47:48 -0500 Received: from mo4-p00-ob.smtp.rzone.de ([81.169.146.217]:13684 "EHLO mo4-p00-ob.smtp.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726334AbfLaMrs (ORCPT ); Tue, 31 Dec 2019 07:47:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1577796466; s=strato-dkim-0002; d=chronox.de; h=References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=aBhOARcicbiRL8oIBJ+zhmMwQC2n51nOUXKMXbfqIgA=; b=d0AW4pGfNoDeecge16zecgATfisMCcLbCO2IxKNy5xSXetbSEUfFITwClsYqEzEMps gENALpGj4fNLztNBqLAwYk6hVVNewbQesOVkotFLcxrUSdNYo0Jl087niWw4nbwIkBJX 3SWZkKUrvYDi/kgFNzA3mg4yVRJJwwAzvVIa6D4qIWjlCNszm2Vnpan6ZPf6EXOlvS/T sp+H0kwud2ux99rl6jzzcf3UWHw0ACCuAtvAZa9Nw7PffNpacyqar62B5WzHwvJZYEt1 G4OdfGcmIMOQMywLWtiwMUWrK++4DSDgBVlSy9bf+Eue8CjaOMsmERgGqiIrmC6UlnQK v7ZQ== X-RZG-AUTH: ":P2ERcEykfu11Y98lp/T7+hdri+uKZK8TKWEqNyiHySGSa9k9xmwdNnzHHXDbIPScmBEU" X-RZG-CLASS-ID: mo00 Received: from tauon.chronox.de by smtp.strato.de (RZmta 46.1.3 DYNA|AUTH) with ESMTPSA id e09841vBVClkPmc (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Tue, 31 Dec 2019 13:47:46 +0100 (CET) From: Stephan Mueller To: Mohan Marutirao Dhanawade Cc: "linux-crypto@vger.kernel.org" Subject: Re: Hardware TRNG driver framework selection criteria Date: Tue, 31 Dec 2019 13:47:45 +0100 Message-ID: <64323166.GGM4aZ99Nc@tauon.chronox.de> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Am Montag, 30. Dezember 2019, 09:40:30 CET schrieb Mohan Marutirao Dhanawade: Hi Mohan, > Hi everyone, > > I am writing Linux driver to support TRNG hardware module for Xilinx SoC. I > am seeing two frameworks - crypto framework and hw_random (char driver) > which can be used to write driver for TRNG. Can someone please educate me > on what criteria is to be used to decide which framework to use for TRNG > (Crypto framework / hw_random char driver)? The crypto API RNG framework is used to implement deterministic RNGs which in turn need seending from a noise source. The HW RNG framework is used for accessing RNGs which have their own noise source and provide random data with appropriate entropy. These RNGs are available via /dev/hwrng. > > Regards, > Mohan > This email and any attachments are intended for the sole use of the named > recipient(s) and contain(s) confidential information that may be > proprietary, privileged or copyrighted under applicable law. If you are not > the intended recipient, do not read, copy, or forward this email message or > any attachments. Delete this email message and any attachments immediately. Ciao Stephan