From: Felipe Balbi <me@felipebalbi.com>
To: tony@atomide.com, paul@pwsam.com
Cc: linux-omap@vger.kernel.org
Subject: L4 interconnect memory mapping
Date: Wed, 30 Dec 2009 01:25:34 +0200 [thread overview]
Message-ID: <1262129134.28789.96.camel@gandalf> (raw)
Hi Tony and Paul,
maybe a silly question, but here it goes:
Do we have any piece of code handling the L4 interconnect memory space ?
I mean, looking at omap3 TRM pages 212 - 219, I see that e.g. for the
musb block we have:
HS USB OTG 0x480AB000 - 0x480ABFFF 4KB Module
0x480AC000 - 0x480ACFFF 4KB L4 interconnect
So the first 4K is what we pass down to drivers via struct resource and
the second 4K ? What do we do with that ?
--
balbi
next reply other threads:[~2009-12-29 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 23:25 Felipe Balbi [this message]
2009-12-29 23:28 ` L4 interconnect memory mapping Felipe Balbi
2009-12-29 23:46 ` Tony Lindgren
2009-12-29 23:50 ` Felipe Balbi
2009-12-30 6:17 ` Shilimkar, Santosh
2009-12-30 9:16 ` Paul Walmsley
2009-12-30 11:56 ` Felipe Balbi
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=1262129134.28789.96.camel@gandalf \
--to=me@felipebalbi.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsam.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