Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934268AbcLMPeA (ORCPT ); Tue, 13 Dec 2016 10:34:00 -0500 Received: from mail-wj0-f194.google.com ([209.85.210.194]:33054 "EHLO mail-wj0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933334AbcLMPdq (ORCPT ); Tue, 13 Dec 2016 10:33:46 -0500 Date: Tue, 13 Dec 2016 16:33:15 +0100 From: Corentin Labbe To: PrasannaKumar Muralidharan Cc: Herbert Xu , davem@davemloft.net, maxime.ripard@free-electrons.com, Chen-Yu Tsai , linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2] crypto: sun4i-ss: support the Security System PRNG Message-ID: <20161213153315.GC10647@Red> References: <1480934922-20732-1-git-send-email-clabbe.montjoie@gmail.com> <20161205123705.GA10732@gondor.apana.org.au> <20161205125738.GA13525@Red> <20161207120900.GC20680@gondor.apana.org.au> <20161207125127.GB28218@Red> <20161208090618.GB22932@gondor.apana.org.au> <20161213141059.GB10647@Red> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 835 Lines: 16 On Tue, Dec 13, 2016 at 08:53:54PM +0530, PrasannaKumar Muralidharan wrote: > > What do you think about those two solutions ? > > I prefer the second solution's idea of using two files (/dev/hwrng and > /dev/hwprng). Upon having a quick glance it looks like (based on > current_rng == prng check) that your current implementation allows > only one rng device to be in use at a time. It would be better to have > both usable at the same time. So applications that need pseudo random > data at high speed can use /dev/prng while applications that require > true random number can use /dev/rng. Please feel free to correct if my > understanding of the code is incorrect. Along with this change I think > changing the algif_rng to use this code if this solution is going to > be used. > No, there could be both device at the same time.