[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130918203949.GI9994@atomide.com>
Date: Wed, 18 Sep 2013 13:39:49 -0700
From: Tony Lindgren <tony@...mide.com>
To: Pali Rohár <pali.rohar@...il.com>
Cc: Matt Mackall <mpm@...enic.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Russell King <linux@....linux.org.uk>,
linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] RX-51: Add support for OMAP3 ROM Random Number
Generator
* Pali Rohár <pali.rohar@...il.com> [130918 13:15]:
> Signed-off-by: Pali Rohár <pali.rohar@...il.com>
Description please, then also add a note that this makes
sense to do as a platform device at least until we have
some ARM generic way to deal with SMC calls.
> arch/arm/mach-omap2/board-rx51.c | 10 ++++++++++
> arch/arm/mach-omap2/omap-secure.c | 11 +++++++++++
> arch/arm/mach-omap2/omap-secure.h | 1 +
> 3 files changed, 22 insertions(+)
>
> diff --git a/arch/arm/mach-omap2/board-rx51.c b/arch/arm/mach-omap2/board-rx51.c
> index db168c9..c2a3e39 100644
> --- a/arch/arm/mach-omap2/board-rx51.c
> +++ b/arch/arm/mach-omap2/board-rx51.c
> @@ -93,6 +93,14 @@ static struct omap_musb_board_data musb_board_data = {
> .power = 0,
> };
>
> +static struct platform_device omap3_rom_rng_device = {
> + .name = "omap_rng",
> + .id = -1,
> + .dev = {
> + .platform_data = rx51_secure_rng_call,
> + },
> +};
> +
> static void __init rx51_init(void)
> {
> struct omap_sdrc_params *sdrc_params;
> @@ -113,6 +121,8 @@ static void __init rx51_init(void)
> /* set IBE to 1 */
> rx51_secure_update_aux_cr(BIT(6), 0);
> #endif
> + pr_info("RX-51: Registring OMAP3 HWRNG device\n");
> + platform_device_register(&omap3_rom_rng_device);
> }
>
> /* Ensure SDRC pins are mux'd for self-refresh */
Maybe this should be in board-rx51-peripherals.c instead?
That way we can initialize the legacy platform devices
from there for DT based booting too and don't have to
move code around when moving to DT based booting.
Regards,
Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists