Hi Paul, On Thursday 29 August 2013 12:18 AM, Paul Walmsley wrote: > Hi > > On Tue, 6 Aug 2013, Lokesh Vutla wrote: > >> Add RNG hwmod data for AM33xx SoC. >> >> Signed-off-by: Lokesh Vutla <lokeshvutla@xxxxxx> > > I tried to queue this one, but it caused AM33xx boots to hang. > Thought it might be related to the patch ordering -- seems to me that > the clock change patch needed to come before this patch -- but if I > recall correctly, both BeagleBone and BeagleBone-LT still hung. This is because register address space is not passed in hwmod_data as it is passed from dt. So we need to include 3/3 patch in this series to boot. Ill fix this sparse warning and post a v2. PS: Probe for this driver will be failed even after this. Support for this version of rng ip is already posted and pushed into cryptodev-2.6 tree. Thanks and regards, Lokesh > > Also, this patch created a sparse warning. > > Could you take another look at this patch? Maybe try basing off of this > tag: > > git://git.kernel.org/pub/scm/linux/kernel/git/pjw/omap-pending.git tags/for-v3.12/omap-prcm-hwmod > > Fix the sparse problem, and see if the patch boots for you? > > thanks > > > - Paul > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
