All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Deepak Saxena <dsaxena@plexity.net>, Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
	tony@atomide.com, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [patch 0/5] HW RNG cleanup & new drivers
Date: Sat, 29 Oct 2005 18:09:35 -0400	[thread overview]
Message-ID: <4363F31F.2040303@pobox.com> (raw)
In-Reply-To: <20051029191229.562454000@omelas>

Deepak Saxena wrote:
> This patch adds support to the kernel for some more HW RNG devices
> and cleans up the code a bit.  My basic goal was to keep the same
> user space interface as exists, but not have to reproduce all
> the same 100 lines of user space interface code across every new
> driver (as we currently do with watchdogs...)
> 
> The new code separates the HW specific driver from the user 
> interface code and just adds a few function pointers so that
> the two can talk to each other. I opted out of using a sysfs
> class and all that complication b/c there will be one and only
> one RNG device at a time on a given system.
> 
> I've added drivers for Intels' IXP4xx and for the TI OMAP and
> these have both been tested.

I would prefer to let this live in -mm at least for a little while. 
Confirmation from AMD, Intel and VIA owners would be really nice, too. 
AMD and Intel might be a little bit hard to find.  I think Peter Anvin 
had an Intel ICH w/ RNG at one time...


> There was some discussion on lkml on the subject of killing
> the in-kernel driver and moving the whole implementation to
> user space but that cannot be done as some SOCs (MPC85xx for
> example) have the RNG unit as part of a larger device that
> needs kernel space code to manage command descriptor rings
> and other such things. We also want to be able to suspend/resume
> the RNG devices (see OMAP driver) and that needs to be done as part
> of the kernel PM path.

None of this precludes having this stuff in userspace.

That said, I don't object to your code being an intermediate step.

	Jeff (hw_random author)



  parent reply	other threads:[~2005-10-29 22:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 19:12 [patch 0/5] HW RNG cleanup & new drivers Deepak Saxena
2005-10-29 19:12 ` [patch 1/5] Remove existing hw_random implementation Deepak Saxena
2005-10-29 19:12 ` [patch 2/5] Core HW RNG support Deepak Saxena
2002-01-01  5:46   ` Pavel Machek
2005-10-29 19:12 ` [patch 3/5] Intel IXP4xx driver Deepak Saxena
2005-10-29 19:12 ` [patch 4/5] x86 driver Deepak Saxena
2005-10-29 19:12 ` [patch 5/5] TI OMAP driver Deepak Saxena
2005-10-29 22:09 ` Jeff Garzik [this message]
2005-10-29 22:25   ` [patch 0/5] HW RNG cleanup & new drivers Linus Torvalds
2005-10-29 22:33     ` Jeff Garzik
2005-10-30 19:58       ` Deepak Saxena
2005-10-30  0:23   ` Gene Heskett
2005-10-30 14:31     ` Alistair John Strachan
2005-10-30 18:08       ` Kalin KOZHUHAROV
2005-10-30 19:35         ` Folkert van Heusden
2005-10-30 20:02   ` Deepak Saxena
2005-10-30 22:35     ` Linus Torvalds
2005-10-30 23:04       ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4363F31F.2040303@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=dsaxena@plexity.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.