| To: | mpm@selenic.com |
|---|---|
| Subject: | Re: [PATCH] TXx9: Add TX4939 RNG support |
| From: | Atsushi Nemoto <anemo@mba.ocn.ne.jp> |
| Date: | Mon, 01 Jun 2009 02:23:35 +0900 (JST) |
| Cc: | linux-mips@linux-mips.org, ralf@linux-mips.org, linux-kernel@vger.kernel.org, herbert@gondor.apana.org.au |
| In-reply-to: | <1243789289.22069.25.camel@calx> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <1243350141-883-2-git-send-email-anemo@mba.ocn.ne.jp> <20090601.015755.21367568.anemo@mba.ocn.ne.jp> <1243789289.22069.25.camel@calx> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Sun, 31 May 2009 12:01:29 -0500, Matt Mackall <mpm@selenic.com> wrote: > > > Not clear to me how this works when this is a module? > > > > This patch add a registration of a platform device for RNG to vmlinux. > > And the other patch add a driver module for the RNG. This strategy is > > fairly common for SoCs or embedded platforms. > > If your driver is built as a module (which your patch allows), the above > won't work, right? No, the rng driver can be used regardless of module or built-in, as like as other platform drivers. Any special issue for hw_rng? --- Atsushi Nemoto |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] hwrng: Add TX4939 RNG driver, Atsushi Nemoto |
|---|---|
| Next by Date: | Re: [PATCH] TXx9: Add TX4939 RNG support, Matt Mackall |
| Previous by Thread: | Re: [PATCH] TXx9: Add TX4939 RNG support, Matt Mackall |
| Next by Thread: | Re: [PATCH] TXx9: Add TX4939 RNG support, Matt Mackall |
| Indexes: | [Date] [Thread] [Top] [All Lists] |