From: Sebastian Reichel <sre@kernel.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] mobile phones
Date: Sun, 2 Jul 2017 14:03:21 +0200 [thread overview]
Message-ID: <20170702120321.tskgcrbfehg4fccx@earth> (raw)
In-Reply-To: <20170628202722.GC18101@amd>
[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]
Hi,
On Wed, Jun 28, 2017 at 10:27:22PM +0200, Pavel Machek wrote:
> > > Oh, another major piece is DSP coprocessor that is there. Unlike
> > > graphics, we don't even know how support for it should like.
> >
> > https://www.kernel.org/doc/Documentation/remoteproc.txt
> >
> > config OMAP_REMOTEPROC
> > tristate "OMAP remoteproc support"
> > [...]
> > help
> > Say y here to support OMAP's remote processors (dual M3
> > and DSP on OMAP4) via the remote processor framework.
> >
> > Currently only supported on OMAP4.
> >
> > Usually you want to say Y here, in order to enable multimedia
> > use-cases to run on your platform (multimedia codecs are
> > offloaded to remote DSP processors using this framework).
> >
> > It's safe to say N here if you're not interested in multimedia
> > offloading or just want a bare minimum kernel.
> >
> > I have been told by some Nokia people (I do not remember who it
> > was, possibly Sakari), that the DSP is not that powerful and any
> > calculation should also be possible on CPU (wasting a bit of
> > energy).
>
> Ok, we probably don't care about DSP, but lets say we had really
> fast DSP or really cared about power.
>
> We'd need remoteproc. Sure. But that has no interface for userland,
> right?
remoteproc is only for start/stop + fw loading. The actual
communication is done using rpmsg, which does not yet have a
userspace API afaik.
> So we'd need to introduce interface for userland... fine.
>
> And then we'd need cross-compilers for the DSP used. Ok.
Yes. As far as I know there is currently no open source toolchain
for the TI DSP.
> And then we'd need to split mpg123 to CPU and DSP parts, and modify it
> so that it can run the DSP parts using remoteproc, when available?
>
> That starts to be ... complex, with changes all over the system :-(.
With little gain expected on N900...
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-02 12:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 10:48 Pavel Machek
2017-06-25 23:55 ` NeilBrown
2017-06-26 6:43 ` Geert Uytterhoeven
2017-06-26 6:49 ` Tony Lindgren
2017-06-26 11:12 ` Pavel Machek
2017-06-26 11:49 ` Tony Lindgren
2017-06-26 13:14 ` Pavel Machek
2017-06-26 13:49 ` Tony Lindgren
2017-06-26 20:49 ` Pavel Machek
2017-06-27 7:18 ` Tony Lindgren
2017-06-27 12:14 ` Sebastian Reichel
2017-06-27 21:57 ` Pavel Machek
2017-06-28 16:01 ` Sebastian Reichel
2017-06-28 20:27 ` Pavel Machek
2017-07-02 12:03 ` Sebastian Reichel [this message]
2017-06-27 21:57 ` Pavel Machek
2017-06-26 8:34 ` Pavel Machek
2017-06-26 11:20 ` Mark Brown
2017-06-26 12:22 ` Pavel Machek
2017-06-27 11:40 ` Mark Brown
2017-06-28 18:37 ` Pavel Machek
2017-07-02 12:11 ` Sebastian Reichel
2017-06-26 22:23 ` Alexandre Belloni
2017-06-27 7:06 ` Pavel Machek
2017-06-27 12:39 ` Sebastian Reichel
2017-06-27 21:57 ` Pavel Machek
2017-06-28 16:45 ` Sebastian Reichel
2017-06-28 21:10 ` Pavel Machek
2017-07-02 11:28 ` Sebastian Reichel
2017-07-02 18:14 ` Pavel Machek
2017-06-26 10:54 ` Mark Brown
2017-06-26 11:14 ` Pavel Machek
2017-06-26 11:49 ` Mark Brown
2017-06-26 12:38 ` Pavel Machek
2017-06-26 16:34 ` Mark Brown
2017-06-27 11:41 ` Sebastian Reichel
2017-06-28 14:38 ` Linus Walleij
2017-06-28 15:58 ` Arnd Bergmann
2017-06-28 16:04 ` Laurent Pinchart
2017-06-28 16:25 ` Pavel Machek
2017-06-28 18:26 ` Mark Brown
2017-06-28 17:01 ` Pavel Machek
2017-06-28 19:03 ` Tony Lindgren
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=20170702120321.tskgcrbfehg4fccx@earth \
--to=sre@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=pavel@ucw.cz \
/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