From: Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
To: Ohad Ben-Cohen <ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
John Williams
<john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
Subject: Re: Remoteproc device-tree node description proposal
Date: Fri, 29 Jun 2012 07:01:00 +0200 [thread overview]
Message-ID: <4FED368C.1070201@monstr.eu> (raw)
In-Reply-To: <CAK=WgbbA2+oJARCEAgChct8rQ+s5=-cbR1esMPNekun3=ReGEA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 06/28/2012 09:54 AM, Ohad Ben-Cohen wrote:
> On Wed, Jun 27, 2012 at 8:17 AM, Michal Simek<monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org> wrote:
>> Ohad: What properties are required by TI to describe firmware?
>> I would like to add together all requirements and create any formal
>> remoteproc description.
>
> I'm not so sure about this.
>
> The low level remoteproc driver is platform specific and may look
> completely different on different platforms..
>
> I suggest you go ahead and add DTS remoteproc support for your
> platform, and when TI or others will get to it too, we will see if any
> commonality is in place.
ok.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
prev parent reply other threads:[~2012-06-29 5:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 5:17 Remoteproc device-tree node description proposal Michal Simek
[not found] ` <4FEA974F.9050908-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2012-06-28 7:54 ` Ohad Ben-Cohen
[not found] ` <CAK=WgbbA2+oJARCEAgChct8rQ+s5=-cbR1esMPNekun3=ReGEA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-29 5:01 ` Michal Simek [this message]
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=4FED368C.1070201@monstr.eu \
--to=monstr-psz03upnqpehxe+lvdladg@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
--cc=ohad-Ix1uc/W3ht7QT0dZR+AlfA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@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;
as well as URLs for NNTP newsgroup(s).