From: Nishanth Menon <nm@ti.com>
To: Suman Anna <s-anna@ti.com>, Paul Walmsley <paul@pwsan.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
Afzal Mohammed <afzal@ti.com>, Tero Kristo <t-kristo@ti.com>,
Rajendra Nayak <rnayak@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: hwmod: check for module address space during init
Date: Mon, 7 Oct 2013 16:19:54 -0500 [thread overview]
Message-ID: <5253257A.2070301@ti.com> (raw)
In-Reply-To: <1380819546-53631-1-git-send-email-s-anna@ti.com>
On 10/03/2013 11:59 AM, Suman Anna wrote:
> The hwmod init sequence involves initializing and idling all the
> hwmods during bootup. If a module class has sysconfig, the init
> sequence utilizes the module register base for performing any
> sysc configuration.
>
> The module address space is being removed from hwmod database and
> retrieved from the <reg> property of the corresponding DT node.
> If a hwmod does not have its corresponding DT node defined and the
> memory address space is not defined in the corresponding
> omap_hwmod_ocp_if, then the module register target address space
> would be NULL and any sysc programming would result in a NULL
> pointer dereference and a kernel boot hang.
>
> Handle this scenario by checking for a valid module address space
> during the _init of each hwmod, and leaving it in the registered
> state if no module register address base is defined in either of
> the hwmod data or the DT data.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> ---
> This patch helps break the dependencies between hwmod entries and
> corresponding DT entries (especially on OMAP5, where most of the
> address spaces are already cleaned up and the current data files
> have minimal entries) and fixes any boot issues due to missing
> addresses. See for reference,
> http://marc.info/?t=138005421400003&r=1&w=2
>
> Tested on BeagleXM, Panda4, BeagleBone Black and Panda5 using
> Tero's v7 clk DT patches and Benoit's for-3.13/dts on top of
> 3.12-rc3
>
> arch/arm/mach-omap2/omap_hwmod.c | 29 +++++++++++++++++++----------
> 1 file changed, 19 insertions(+), 10 deletions(-)
Mandatory to have this patch for OMAP5uEVM to boot after Tero's v7 [1]
series is merged else the delta between dts and hwmod entries cause
OMAP5 platforms to croak and die - at least worked around as seen in
[2] :(
Tested-by: Nishanth Menon <nm@ti.com>
[1] http://marc.info/?t=138009899400001&r=1&w=2
[2] OMAP5uEVM: http://pastebin.com/jtEMwTY5
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-10-07 21:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 16:59 [PATCH] ARM: OMAP2+: hwmod: check for module address space during init Suman Anna
2013-10-03 17:05 ` Santosh Shilimkar
2013-10-07 21:19 ` Nishanth Menon [this message]
2013-10-07 22:04 ` Suman Anna
2013-10-08 18:09 ` Tony Lindgren
2013-10-08 21:44 ` Suman Anna
2013-10-09 5:35 ` Paul Walmsley
2013-10-09 17:54 ` Suman Anna
-- strict thread matches above, loose matches on Subject: below --
2013-11-20 22:14 Paul Walmsley
2013-11-20 22:14 ` Paul Walmsley
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=5253257A.2070301@ti.com \
--to=nm@ti.com \
--cc=afzal@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=s-anna@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.