Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756041Ab3CaJ2S (ORCPT ); Sun, 31 Mar 2013 05:28:18 -0400 Received: from mail-wg0-f47.google.com ([74.125.82.47]:44234 "EHLO mail-wg0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750720Ab3CaJ2Q (ORCPT ); Sun, 31 Mar 2013 05:28:16 -0400 From: Pali =?utf-8?q?Roh=C3=A1r?= To: Tony Lindgren Subject: Re: [PATCH] OMAP3 ROM Random Number Generator support Date: Sun, 31 Mar 2013 11:28:12 +0200 User-Agent: KMail/1.13.7 (Linux/3.5.0-27-generic; KDE/4.10.1; x86_64; ; ) Cc: Juha Yrjola , Russell King , Matt Mackall , Herbert Xu , linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, =?utf-8?q?=D0=98=D0=B2=D0=B0=D0=B9=D0=BB=D0=BE?= =?utf-8?q?_=D0=94=D0=B8=D0=BC=D0=B8=D1=82=D1=80=D0=BE=D0=B2?= References: <201302281905.48546@pali> <201303281854.02847@pali> <20130328214411.GZ10155@atomide.com> In-Reply-To: <20130328214411.GZ10155@atomide.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4508047.TXkkfaCaca"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201303311128.12698@pali> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3026 Lines: 103 --nextPart4508047.TXkkfaCaca Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Thursday 28 March 2013 22:44:11 Tony Lindgren wrote: > * Pali Roh=C3=A1r [130328 10:58]: > > Here is new version of patch: > >=20 > > --- a/arch/arm/mach-omap2/devices.c > > +++ b/arch/arm/mach-omap2/devices.c > > @@ -486,6 +486,23 @@ static void omap_init_mcspi(void) > >=20 > > static inline void omap_init_mcspi(void) {} > > #endif > >=20 > > +extern u32 *omap3_rom_rng_call(u32 id, u32 proc, u32 flags, > > u32 va_ptr); + > > +static struct platform_device omap3_rom_rng_device =3D { > > + .name =3D "omap3-rom-rng", > > + .id =3D -1, > > + .dev =3D { > > + .platform_data =3D omap3_rom_rng_call, > > + }, > > +}; > > + > > +static void omap_init_rom_rng(void) > > +{ > > + if (!cpu_is_omap34xx() || omap_type() =3D=3D > > OMAP2_DEVICE_TYPE_GP) + return; > > + platform_device_register(&omap3_rom_rng_device); > > +} > > + > >=20 > > /** > > =20 > > * omap_init_rng - bind the RNG hwmod to the RNG > > omap_device * >=20 > This driver probably only works on Nokia boards because of the > different SMC call numbering. Until it's been verified on some > other HS omap34xx, I'd probably register this only from the > Nokia board-*.c file. >=20 =46reemangordon, can you look at this smc and errara 430973 code if=20 they could be merged? Really omap3_rom_rng_call function looks=20 like n900 specific. Link: https://lkml.org/lkml/2013/3/28/398 > > --- /dev/null > > +++ b/drivers/char/hw_random/omap3-rom-rng.c > > +static int omap3_rom_rng_probe(struct platform_device > > *pdev) +{ > > + printk(KERN_INFO "%s: initializing\n", > > omap3_rom_rng_name); + > > + omap3_rom_rng_call =3D pdev->dev.platform_data; > > + if (!omap3_rom_rng_call) { > > + printk(KERN_ERR "%s: omap3_rom_rng_call is NULL\n", > > + omap3_rom_rng_name); > > + return -EINVAL; > > + } > > + > > + setup_timer(&idle_timer, omap3_rom_idle_rng, 0); > > + rng_clk =3D clk_get_sys("omap_rng", "ick"); > > + if (IS_ERR(rng_clk)) { > > + printk(KERN_ERR "%s: unable to get RNG clock\n", > > + omap3_rom_rng_name); > > + return IS_ERR(rng_clk); > > + } >=20 > You can use regular clk_get if you add the alias to > struct omap_clk omap3xxx_clks table. >=20 > Regards, >=20 > Tony Tony, can you show me how? =2D-=20 Pali Roh=C3=A1r pali.rohar@gmail.com --nextPart4508047.TXkkfaCaca Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEABECAAYFAlFYAawACgkQi/DJPQPkQ1J4eACgj3BxpHuap4RtxayaL9La1C9y 8vkAn1WzN6qDwLLOlk4ZvwJTweq/KnOT =2mr3 -----END PGP SIGNATURE----- --nextPart4508047.TXkkfaCaca-- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/