From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: ohad@wizery.com, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] remoteproc: add some kind of help
Date: Fri, 30 Dec 2016 04:01:16 -0800 [thread overview]
Message-ID: <20161230120116.GA9118@builder> (raw)
In-Reply-To: <20161219092250.GA13640@amd>
On Mon 19 Dec 01:22 PST 2016, Pavel Machek wrote:
>
> Top level config option without any kind of help... is kind of
> strange. Remote processors could also mean some kind of distributed
> computing...
>
> Signed-off-by: Pavel Machek <pavel@ucw.cz>
Thanks, applied.
Regards,
Bjorn
>
> diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig
> index 8f9cf0b..a5e8880 100644
> --- a/drivers/remoteproc/Kconfig
> +++ b/drivers/remoteproc/Kconfig
> @@ -7,6 +7,9 @@ config REMOTEPROC
> select FW_LOADER
> select VIRTIO
> select VIRTUALIZATION
> + help
> + Support for remote processors (such as DSP coprocessors). These
> + are mainly used on embedded systems.
>
> if REMOTEPROC
>
> @@ -25,11 +28,11 @@ config OMAP_REMOTEPROC
>
> Currently only supported on OMAP4.
>
> - Usually you want to say y here, in order to enable multimedia
> + 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
> + It's safe to say N here if you're not interested in multimedia
> offloading or just want a bare minimum kernel.
>
> config WKUP_M3_RPROC
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2016-12-30 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 9:22 [PATCH] remoteproc: add some kind of help Pavel Machek
2016-12-30 12:01 ` Bjorn Andersson [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=20161230120116.GA9118@builder \
--to=bjorn.andersson@linaro.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--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