From: Chen Baozi <baozich@gmail.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
List Xen Developer <xen-devel@lists.xen.org>
Subject: Re: Problems when using latest git tree to boot xen on OMAP5
Date: Tue, 8 Oct 2013 21:54:33 +0800 [thread overview]
Message-ID: <09C3DD3C-4749-4974-A85D-81EF122E11A7@gmail.com> (raw)
In-Reply-To: <5252D6EF.3040900@linaro.org>
On Oct 7, 2013, at 11:44 PM, Julien Grall <julien.grall@linaro.org> wrote:
> On 10/07/2013 04:28 PM, Chen Baozi wrote:
>
>>
>> addr2line would lead to __raw_readl() in arch/arm/include/asm/io.h. So
>> it doesn't that useful.
>
> Ah right ... but __raw_readl is usually inlined so you can use objdump
> and find the instruction. After that, if you go a bit above you can find
> the caller name.
It is called by omap_hwmod_read(). And it is mostly like to be called
ultimately by omap_device_build_from_dt in _omap_device_notifier_call.
I guess it might relate to the OCP platform bus initialization and
hard coded "omap_hwmod" information. But I can't point out the exact
calling stack of omap_hwmod_read sadly...
Cheers,
Baozi
next prev parent reply other threads:[~2013-10-08 13:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 14:11 Problems when using latest git tree to boot xen on OMAP5 Chen Baozi
2013-10-06 14:21 ` Chen Baozi
2013-10-07 8:39 ` Ian Campbell
2013-10-07 9:58 ` Chen Baozi
2013-10-07 10:01 ` Ian Campbell
2013-10-07 10:59 ` Julien Grall
2013-10-07 15:28 ` Chen Baozi
2013-10-07 15:44 ` Julien Grall
2013-10-08 13:54 ` Chen Baozi [this message]
2013-10-09 7:46 ` Chen Baozi
2013-10-09 8:11 ` Ian Campbell
2013-10-09 9:09 ` Chen Baozi
2013-10-09 11:15 ` Julien Grall
2013-10-09 11:19 ` Ian Campbell
2013-10-09 11:29 ` Stefano Stabellini
2013-10-09 12:01 ` Ian Campbell
2013-10-09 12:11 ` Stefano Stabellini
2013-10-09 11:29 ` Julien Grall
2013-10-09 12:05 ` Ian Campbell
2013-10-15 8:41 ` Chen Baozi
2013-10-10 8:05 ` Chen Baozi
2013-10-10 11:07 ` Julien Grall
2013-10-10 11:36 ` Chen Baozi
2013-10-10 12:04 ` Vaibhav Bedia
2013-10-07 10:19 ` Julien Grall
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=09C3DD3C-4749-4974-A85D-81EF122E11A7@gmail.com \
--to=baozich@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=xen-devel@lists.xen.org \
/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.