From: Suman Anna <s-anna@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: Paul Zimmerman <Paul.Zimmerman@synopsys.com>,
"tony@atomide.com" <tony@atomide.com>,
"lokeshvutla@ti.com" <lokeshvutla@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Benoit Cousson <bcousson@baylibre.com>
Subject: Re: Booting recent mainline on omap5-uevm
Date: Wed, 25 Sep 2013 13:20:17 -0500 [thread overview]
Message-ID: <52432961.3020005@ti.com> (raw)
In-Reply-To: <5242265E.6020204@ti.com>
Santosh,
On 09/24/2013 06:55 PM, Santosh Shilimkar wrote:
> On Tuesday 24 September 2013 07:48 PM, Suman Anna wrote:
>> On 09/24/2013 05:24 PM, Santosh Shilimkar wrote:
>>> On Tuesday 24 September 2013 04:30 PM, Paul Zimmerman wrote:
>>>>> From: Paul Zimmerman
>>>>> Sent: Tuesday, September 24, 2013 1:21 PM
>>>>>
>>>>> Hi,
>>>>>
>>>>> I have an OMAP5432 uEVM which I cannot get to boot with recent mainline
>>>>> (tried 3.11 and 3.12-rc1). I have the TI GLSDK for this board (v6.0.0.7),
>>>>> which comes with 3.8.4 which works fine.
>>>>>
>>>>> I found this thread: http://marc.info/?l=fedora-arm&m=137717811815777 and
>>>>
>>>> Wrong link, should have been http://marc.info/?l=linux-omap&m=137515583214350.
>>>>
>>> Its because of commit 03ab349ec{ARM: OMAP5: hwmod data: Add mailbox data} which
>>> added hwmod data but DT data for mailbox is missing. Reverting that makes
>>> things work. Looks like mailbox dt patches missed the last merge window.
>>
>> Yeah, the boot sequence tries to enable and idle all the hwmods, and
>> this results in an error while initializing the mailbox hwmod during the
>> sysc configuration. This is because the OMAP5 hwmod data file no longer
>> has the omap_hwmod_addr_space defined in the hwmod_ocp_if data. Two ways
>> for now to get past is either revert the mailbox hwmod commit as above
>> or add the DT node [2].
>>
> Would be good if you can get the mailbox dt node in rc cycles. But since
> CCF is still missing if if that doesn't happen in rc's thats ok.
Would mostly be 3.13, we do not want to add just the OMAP5 DT node patch
separately in a 3.12 rc, since there are other patches that add the DT
binding documentation and driver support. Will definitely need to be
queued up alongside the CCF patches when OMAP5 boot is being enabled.
regards
Suman
next prev parent reply other threads:[~2013-09-25 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 20:30 Booting recent mainline on omap5-uevm Paul Zimmerman
2013-09-24 22:24 ` Santosh Shilimkar
2013-09-24 23:48 ` Suman Anna
2013-09-24 23:55 ` Santosh Shilimkar
2013-09-25 18:20 ` Suman Anna [this message]
2013-09-24 23:59 ` Paul Zimmerman
2013-09-25 15:02 ` Santosh Shilimkar
2013-09-25 18:37 ` Suman Anna
2013-09-26 19:36 ` Paul Zimmerman
2013-09-26 20:35 ` Suman Anna
-- strict thread matches above, loose matches on Subject: below --
2013-09-24 20:20 Paul Zimmerman
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=52432961.3020005@ti.com \
--to=s-anna@ti.com \
--cc=Paul.Zimmerman@synopsys.com \
--cc=bcousson@baylibre.com \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=santosh.shilimkar@ti.com \
--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).