From: Lokesh Vutla <lokeshvutla@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
tony@atomide.com, devicetree@vger.kernel.org, rob@landley.net,
rnayak@ti.com, benoit.cousson@linaro.org
Subject: Re: [PATCH 1/3] ARM: AM33xx: hwmod: Add RNG module data
Date: Thu, 29 Aug 2013 14:52:18 +0530 [thread overview]
Message-ID: <521F12CA.8010608@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1308281845560.22040@utopia.booyaka.com>
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@ti.com>
>
> 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
>
next prev parent reply other threads:[~2013-08-29 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1375777984-6267-1-git-send-email-lokeshvutla@ti.com>
[not found] ` <1375777984-6267-2-git-send-email-lokeshvutla@ti.com>
2013-08-28 18:48 ` [PATCH 1/3] ARM: AM33xx: hwmod: Add RNG module data Paul Walmsley
2013-08-29 9:22 ` Lokesh Vutla [this message]
2013-08-29 11:30 ` Paul Walmsley
2013-08-29 12:05 ` Lokesh Vutla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=521F12CA.8010608@ti.com \
--to=lokeshvutla@ti.com \
--cc=benoit.cousson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=rob@landley.net \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).