Devicetree
 help / color / mirror / Atom feed
From: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: "Cousson, Benoit" <b-cousson-l0cyMroinI0@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
	Discuss"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: TI OMAP device tree and DSPs?
Date: Thu, 8 Dec 2011 15:03:27 -0600	[thread overview]
Message-ID: <D7CA9494-73D0-4251-9A3E-F71206263D4A@kernel.crashing.org> (raw)
In-Reply-To: <4EE0ECB5.2030407-l0cyMroinI0@public.gmane.org>


On Dec 8, 2011, at 10:58 AM, Cousson, Benoit wrote:

> On 12/8/2011 5:07 PM, Kumar Gala wrote:
>> Seen a lot of ARM&  TI OMAP discussions on this list.  I was
>> wondering if the DSPs on any devices that have ARM + DSP are
>> represented in the device trees yet.
> 
> So far, for the OMAP case, the DSP node is mostly empty.
> 
> The issue is that I'm not sure we can represent in the same DT both MPU and DSP view, since the DT root is supposed to represent a processor.
> If we need the real DSP viewpoint, we will have to mostly duplicate the MPU view then remove MPU private peripherals and add the DSP private peripherals.
> 
> Regards,
> Benoit

Is there pointer to an example dts that show whatever you have for DSP ?

- k

  parent reply	other threads:[~2011-12-08 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-08 16:07 TI OMAP device tree and DSPs? Kumar Gala
     [not found] ` <F9C60F6C-BC0A-4987-B59E-DCCBD249424D-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2011-12-08 16:58   ` Cousson, Benoit
     [not found]     ` <4EE0ECB5.2030407-l0cyMroinI0@public.gmane.org>
2011-12-08 21:03       ` Kumar Gala [this message]
     [not found]         ` <D7CA9494-73D0-4251-9A3E-F71206263D4A-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2011-12-08 21:07           ` Cousson, Benoit

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=D7CA9494-73D0-4251-9A3E-F71206263D4A@kernel.crashing.org \
    --to=galak-xvmvhmargas8u2djnn8i7kb+6bgklq7r@public.gmane.org \
    --cc=b-cousson-l0cyMroinI0@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox