From: Omar Ramirez Luna <omar.ramirez@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Tony Lindgren <tony@atomide.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
"Guzman Lugo, Fernando" <fernando.lugo@ti.com>,
"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/3] OMAP: control: add functions for DSP boot address/mode control
Date: Mon, 11 Oct 2010 17:32:50 -0500 [thread overview]
Message-ID: <4CB39092.4070303@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010111604430.16871@utopia.booyaka.com>
On 10/11/2010 5:16 PM, Paul Walmsley wrote:
>
> 4. If the DSP uses a peripheral, such as a GPTIMER or a McBSP, DSPBridge
> needs to reserve that device with the rest of Linux so some other Linux
> code isn't using it or doesn't try to use it, causing conflicts with
> DSPBridge. I guess the list that we need to worry about is in _tiomap.h
> as l4_peripheral_table[].
this is done by using dmtimer fwk, mcbsp are also requested using mcbsp
code (however I think functions to enable/disable mcbsp clocks should be
added to mcbsp fwk)... There is no code (that I'm aware of) to control
wdt3 nor ssi so this is still there. I still have to review the code to
find any place were the registers are written directly though.
The other peripherals, at the moment, doesn't have a direct interaction
with bridge, although they might be interconnected to iva. I guess we
can remove some of the mapped peripherals (like dsi, gpio, uart) and add
them back on request and by implementing the code to request them on arm
side.
- omar
next prev parent reply other threads:[~2010-10-11 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101011203659.24425.2381.stgit@twilight.localdomain>
2010-10-11 20:37 ` [PATCH 1/3] OMAP: control: add functions for DSP boot address/mode control Paul Walmsley
2010-10-11 20:47 ` Felipe Contreras
2010-10-11 20:53 ` Paul Walmsley
2010-10-11 21:16 ` Tony Lindgren
2010-10-11 21:35 ` Paul Walmsley
2010-10-11 22:15 ` Omar Ramirez Luna
2010-10-11 22:16 ` Paul Walmsley
2010-10-11 22:32 ` Omar Ramirez Luna [this message]
2010-10-12 11:01 ` Felipe Contreras
2010-10-12 20:58 ` Tony Lindgren
2010-10-11 20:37 ` [PATCH 2/3] OMAP3: PM: update DSP reset code to use new SCM DSP boot control functions Paul Walmsley
2010-10-11 20:37 ` [PATCH 3/3] DSPBridge: convert OMAP3430 adaptation layer to use new SCM DSP boot control fns Paul Walmsley
2010-10-23 1:04 [PATCH 1/3] OMAP: control: add functions for DSP boot address/mode control Omar Ramirez Luna
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=4CB39092.4070303@ti.com \
--to=omar.ramirez@ti.com \
--cc=felipe.contreras@gmail.com \
--cc=fernando.lugo@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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 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.