From: Stefan Roese <stefan.roese@gmail.com>
To: Nishanth Menon <nm@ti.com>, Paul Walmsley <paul@pwsan.com>,
"Nayak, Rajendra" <rnayak@ti.com>,
"tony@atomide.com" <tony@atomide.com>
Cc: Suman Anna <s-anna@ti.com>, linux-omap <linux-omap@vger.kernel.org>
Subject: Re: AM335x board with disabled RTC crashes
Date: Thu, 21 Nov 2013 05:28:56 +0100 [thread overview]
Message-ID: <528D8C08.1020201@gmail.com> (raw)
In-Reply-To: <528CDAF6.7070905@ti.com>
On 11/20/2013 04:53 PM, Nishanth Menon wrote:
> Paul, Tony, Rajendra,
>
> On 11/20/2013 08:22 AM, Nishanth Menon wrote:
>> On 11/20/2013 08:18 AM, Stefan Roese wrote:
>>> Hi!
>>>
>>> I'm currently working on a custom AM335x based board, where the SoC
>>> RTC is disabled. As described in this page in the "RTC feature disabled"
>>> column:
>>>
>>> http://processors.wiki.ti.com/index.php/AM335x_Schematic_Checklist#RTC
>>>
>>> On this board the registers of the RTC are not accessible. But the OMAP
>>> hwmod code tries to read the sysc register unconditionally from the RTC.
>>> And this leads to this crash (using v3.12):
>>>
>>> ...
>>> [ 0.179491] CPU: Testing write buffer coherency: ok
>>> [ 0.187702] Setting up static identity map for 0xc04dfa90 - 0xc04dfb00
>>> [ 0.204665] devtmpfs: initialized
>>> [ 0.219513] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
>>> [ 0.237462] *** _update_sysc_cache (263): name=emif
>>> [ 0.246247] omap_hwmod: debugss: _wait_target_disable failed
>>> [ 0.252290] *** _update_sysc_cache (263): name=uart1
>>> [ 0.257668] *** _update_sysc_cache (263): name=rtc
>>> [ 0.262885] Unhandled fault: external abort on non-linefetch (0x1028) at 0xf9e3e078
>>> [ 0.270893] Internal error: : 1028 [#1] ARM
>>> [ 0.275302] Modules linked in:
>>> [ 0.278572] CPU: 0 PID: 1 Comm: swapper Not tainted 3.12.0-dirty #21
>>> [ 0.285222] task: c7047340 ti: c7048000 task.ti: c7048000
>>> [ 0.290909] PC is at _update_sysc_cache+0x44/0xb0
>>> [ 0.295861] LR is at _update_sysc_cache+0x1c/0xb0
>>> ...
>>>
>>> Disabling the RTC in the DT doesn't help (of course). So what's the
>>> recommended way to disable this hwmod access to the RTC registers?
>>
>>
>> http://www.spinics.net/lists/linux-omap/msg98207.html
>> might help you - we had thought it might get queued for 3.12, but it
>> was queued for 3.13 instead..
Unfortunately this patch doesn't fix the crash for me (yet). With this
patch applied and the RTC DT node completely removed from am33xx.dtsi it
works. But only disabling it (via status = "disabled" in the board dts
file) doesn't work.
I'll dig a bit deeper today...
Thanks,
Stefan
next prev parent reply other threads:[~2013-11-21 4:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 14:18 AM335x board with disabled RTC crashes Stefan Roese
2013-11-20 14:22 ` Nishanth Menon
[not found] ` <528CDAF6.7070905@ti.com>
2013-11-21 4:28 ` Stefan Roese [this message]
2013-11-21 4:32 ` Stefan Roese
2013-11-21 5:30 ` Nishanth Menon
2013-11-21 5:42 ` Stefan Roese
2013-11-21 5:52 ` Nishanth Menon
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=528D8C08.1020201@gmail.com \
--to=stefan.roese@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=s-anna@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).