From: r.schwebel@pengutronix.de (Robert Schwebel)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] remoteproc for 4.2
Date: Fri, 3 Jul 2015 22:24:33 +0200 [thread overview]
Message-ID: <20150703202433.GI21222@pengutronix.de> (raw)
In-Reply-To: <5594F86B.1040801@melag.de>
On Thu, Jul 02, 2015 at 10:38:03AM +0200, Enrico Weigelt, metux IT consult wrote:
> >for you to fetch changes up to 8de3dbd0895bebe52d069a82feae8e3fb51c1bdf:
> >
> > remoteproc: fix !CONFIG_OF build breakage (2015-06-18 11:44:41 +0300)
>
> Just curious: could this rproc framework also be used for more specific
> coprocessors like the VPUs found on various SoCs ? (eg. CODA on imx53)
No. And there is already a driver in mainline that handles the VPU.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2015-07-03 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 14:14 [GIT PULL] remoteproc for 4.2 Ohad Ben-Cohen
2015-07-02 8:38 ` Enrico Weigelt, metux IT consult
2015-07-03 20:24 ` Robert Schwebel [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=20150703202433.GI21222@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).