All of lore.kernel.org
 help / color / mirror / Atom feed
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:15:24 -0500	[thread overview]
Message-ID: <4CB38C7C.5080702@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1010111519410.16871@utopia.booyaka.com>

On 10/11/2010 4:35 PM, Paul Walmsley wrote:
> On Mon, 11 Oct 2010, Tony Lindgren wrote:
>
>> Would be nice to get the dspbridge into working shape. Sounds we still
>> need the following:
>>
>> - memblock fixes
>> - this series to fix the control module related issues
>> - platform data for the boards
>>
>> Is that all, or are we also missing something else?
>
> A few other things should be done also.
>
> 1. Most of the code in drivers/staging/tidspbridge/code/tiomap3430.c in
> the bridge_brd_monitor(), bridge_brd_start(), and bridge_brd_stop() should
> be moved into a file in arch/arm/mach-omap2.  The DSPBridge driver should
> call those functions (to reset the DSP, start it, etc.) through
> platform_data function pointers.  Once that happens, patch 3 of the
> control module-related series would not be needed, since that code would
> be in arch/arm/mach-omap2 anyway.
>
> 2. The direct CM/PRM/RM register access should be removed from that
> arch/arm/mach-omap2 code.  That should be handled directly by the
> clock/hwmod/whatever code.
>
> 3. DSPBridge should be converted to use PM runtime, and the
> arch/arm/mach-omap2 portion should use omap_device, omap_hwmod, etc.
>

I was working on the 3rd point, but wanted to populate hmods for iommu 
and reuse the patches for hwmod mailbox too, before sending.

Also some stuff needed:

- iommu patches[2], this is under discussion, to get iommu + tidspbridge 
working.

Regards,

Omar


  reply	other threads:[~2010-10-11 22:15 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 [this message]
2010-10-11 22:16           ` Paul Walmsley
2010-10-11 22:32             ` Omar Ramirez Luna
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=4CB38C7C.5080702@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.