Re: [PATCH] TXx9: Add TX4939 RNG support
- From: Matt Mackall <mpm@xxxxxxxxxxx>
- Date: Sun, 31 May 2009 12:32:50 -0500
On Mon, 2009-06-01 at 02:23 +0900, Atsushi Nemoto wrote:
On Sun, 31 May 2009 12:01:29 -0500, Matt Mackall <mpm@xxxxxxxxxxx> 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?
I found the source of my confusion: you've given the init function in
both files exactly the same name. So when I saw .._init at the bottom of
the second patch, I assumed it was referring to the possibly not loaded
driver's init code.
--
http://selenic.com : development and support for Mercurial and Linux
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] TXx9: Add TX4939 RNG support
- From: Atsushi Nemoto
- Re: [PATCH] TXx9: Add TX4939 RNG support
- From: Atsushi Nemoto
- Re: [PATCH] TXx9: Add TX4939 RNG support
- From: Matt Mackall
- Re: [PATCH] TXx9: Add TX4939 RNG support
- From: Atsushi Nemoto
- [PATCH] TXx9: Add TX4939 RNG support
- Prev by Date: Re: [PATCH] TXx9: Add TX4939 RNG support
- Next by Date: Re: [PATCH] coredump: Retry writes where appropriate
- Previous by thread: Re: [PATCH] TXx9: Add TX4939 RNG support
- Next by thread: [PATCH] hwrng: Add TX4939 RNG driver
- Index(es):
Relevant Pages
|
