Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3316755ybl; Sun, 2 Feb 2020 20:54:06 -0800 (PST) X-Google-Smtp-Source: APXvYqzWfrY5QTSOwg570aSOPPaS0BBOCdTaZhhRJxOC6FbtRy0HhF3UDnxMrHekksT3PzyRBteD X-Received: by 2002:a05:6830:154c:: with SMTP id l12mr16299080otp.275.1580705646643; Sun, 02 Feb 2020 20:54:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1580705646; cv=none; d=google.com; s=arc-20160816; b=yDcsGeVPOjmJF/KoKa4ZXZWCJZQtetAskXle7GSwm4dF3jaYQ9iH3pGaG1TkFDKoe3 cpEH0qdacBAbCOT8y09xIYQebwbdPVkXOMaag+te9DvQUkSTo51Hbi+LgftiZQzc5qef jpzmCnp6UtpDmThyqCJInojo/n8sHBzrUuHOAGNckr1HD896sC7NqPklGm43EOFTBv03 sW9BGHjgWp8bvkjatMxV766LCkd5sauIKxyB0qpWeheNyyAOsSJf9+WOHL8fVvDpsCe4 pl9x5zTjDa7Wnzc8kXAkAbWTpGAPba5WYdZpDFNYZ7c0d+XL48+51zh0trb+RoXSIk8H fQcw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:subject:cc:to:from:date:references :in-reply-to:message-id:mime-version:user-agent:dkim-signature :dkim-signature; bh=L2E9Vl0A6zDfiBzKRlHxwBS22SN7gw8Ni7HSCZmgD0c=; b=OmoC4jr02Lii1yMv/32YwgjmYCmzszdsdQyUBNPvDKhZYj0P7Lsp8+ncCF9xVrCAHI cBk1nlhrwXZ6QdkPeb7WZj7+rmtBZ0tDuMynOyfw40XpKKVjpCdEK27FqRpK1g7pH79L uK7h4IYpKE1D/55/6k8tHJPxKRI7YL2CD2RgGGERRffxS9xVagNzfE7BCfdkjdFByJPZ co+/uJrgz8iTJgpP0b9lnNjfy1wOP8vKif1yh4ythbBdD++dEbTZTbzMM13vC4MKpGRS xwDEx8PI7E77bAr/qBme6jV7XwiSEpXMSLsQBjOG0+4CCGxLS4QGmfqNAKXwdabFwilu Bulg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm1 header.b=a0uIK1I1; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=YDhwdctj; 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 f204si7472724oia.43.2020.02.02.20.53.43; Sun, 02 Feb 2020 20:54:06 -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=pass header.i=@aj.id.au header.s=fm1 header.b=a0uIK1I1; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=YDhwdctj; 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 S1727324AbgBCEHj (ORCPT + 99 others); Sun, 2 Feb 2020 23:07:39 -0500 Received: from new2-smtp.messagingengine.com ([66.111.4.224]:59549 "EHLO new2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727096AbgBCEHj (ORCPT ); Sun, 2 Feb 2020 23:07:39 -0500 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id 791A8647A; Sun, 2 Feb 2020 23:07:37 -0500 (EST) Received: from imap2 ([10.202.2.52]) by compute4.internal (MEProxy); Sun, 02 Feb 2020 23:07:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm1; bh=L2E9Vl0A6zDfiBzKRlHxwBS22SN7gw8 Ni7HSCZmgD0c=; b=a0uIK1I16pK/R0L/7jdmO1AfRzmSIFOIAEtcBGZbm+DjudG u+HYtskkc5PK1Bmgpjz61fLLRdZJOSA0C3XnPgzxr5L1nxDsuY5B4ilSghrb/AUU /CctlVldDLYBhX3I84zBiBdqqGxGl1xgNXIphoQ+xvExSdK3VOEKRRLcJRNCRjyi Ww5Xno7JkhzNVXOPM1+UAlhkbjQC2ecJLYMKa6Yo5tNQta2rlWq/6Ie9pvMj2mWE J+Zc0rSQOb/+Q1hxc5Bu1QDF3+PH+AyP3ir9CsPx7syyWo/+tYUPC/h3KSLEkzt4 cm0S3kc10dr0Xrb8cxdCDtmEZLDHVA+I02WG9kQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=L2E9Vl 0A6zDfiBzKRlHxwBS22SN7gw8Ni7HSCZmgD0c=; b=YDhwdctjhuNrquEhuL6BTd q8Zf2pczAhZ5LlXT1volMwZeV6F0j7CGxUgqAHRBcDIRD0Z0Q7pU17bg8rdMukCB nDfKF+SmzleJpAe8F2hcxD4frF3IF9t+9TcYi3Rt4Npj8oPHy7KOO85pslrrolKu +ltMSZac9gbhCWepvzUOXjcVnuRnLuLOICmc3gYWe1SEt9fC0fMpVDoPNEet1kY9 NNqz4U3WMRhBpugpfnmsyLKGi2ccgMpakCR2EiqJCheg+2GyUWZoX5o988sMamVB t2BymEcwCrXiAx1tEKgLND/t22J99Mh5v3aP8NBXwjFhafZ3m6z4rQraTcKu4A4w == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrgeeigdeiiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedftehnughr vgifucflvghffhgvrhihfdcuoegrnhgurhgvfiesrghjrdhiugdrrghuqeenucffohhmrg hinhepghhithhhuhgsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghm pehmrghilhhfrhhomheprghnughrvgifsegrjhdrihgurdgruh X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 5E131E00A2; Sun, 2 Feb 2020 23:07:31 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.7-802-g7a41c81-fmstable-20200203v1 Mime-Version: 1.0 Message-Id: In-Reply-To: <27c5505acd8d09f70ec9cd12982b2e3e@neuralgames.com> References: <20200120150113.2565-1-linux@neuralgames.com> <4446ffb694c7742ca9492c7360856789@neuralgames.com> <575811fd-24ca-409c-8d33-c2152ee401d7@www.fastmail.com> <136bbab84d13d8d56a5ac297e415975e@neuralgames.com> <27c5505acd8d09f70ec9cd12982b2e3e@neuralgames.com> Date: Mon, 03 Feb 2020 14:37:16 +1030 From: "Andrew Jeffery" To: "Oscar A Perez" Cc: "Joel Stanley" , "Matt Mackall" , "Herbert Xu" , "Rob Herring" , "Mark Rutland" , "Linux Crypto Mailing List" , devicetree , "Linux ARM" , linux-aspeed , "Linux Kernel Mailing List" Subject: Re: [PATCH 1/2] hwrng: Add support for ASPEED RNG Content-Type: text/plain Sender: linux-crypto-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Wed, 29 Jan 2020, at 10:56, linux@neuralgames.com wrote: > On 2020-01-27 18:53, Andrew Jeffery wrote: > > Not that I've looked, but is it feasible to augment timeriomem-rng with > > the ability to configure the RNG rather than implement a new driver? > > Why > > didn't you go that route? > > > > I decided to wrote the Aspeed-RNG driver because was under the > impression that the community would prefer dedicated drivers over > generic ones for these SOCs. I think we should leverage existing work where we can. Lets not make more extra for ourselves :) > However, enhancing timeriomem-rng module > is not hard at all. As I matter of fact, I'm currently testing changes > to timeriomem-rng and so far so good. If you would like to have a quick > look to my changes, I just pushed patches to the same repo a couple of > hours ago: > https://github.com/operezmuena/aspeed-rng-testing/tree/master/patches I think this is a good approach so long as we can create a clean interface to the control MMIO(s) inside the driver, i.e. we shouldn't be baking any Aspeed-specific information into generic sections of code. Usually this means sticking a pointer to an ops struct in the data member of the matching OF ID struct. Input from the RNG maintainers will be helpful here. Andrew