From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: anish kumar <yesanishhere@gmail.com>
Cc: ohad@wizery.com, bjorn.andersson@linaro.org, corbet@lwn.net,
linux-remoteproc@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V4 1/7] Remoteproc: Documentation: add the main index
Date: Thu, 24 Oct 2024 09:42:13 -0600 [thread overview]
Message-ID: <Zxpq1RGltdWiE5sA@p14s> (raw)
In-Reply-To: <20241023053357.5261-2-yesanishhere@gmail.com>
On Tue, Oct 22, 2024 at 10:33:51PM -0700, anish kumar wrote:
> In prepration of moving the remoteproc documentation
> from staging to mainline and also for enhancing
> the documentation.
>
> Signed-off-by: anish kumar <yesanishhere@gmail.com>
> ---
> Documentation/driver-api/index.rst | 1 +
> Documentation/driver-api/remoteproc/index.rst | 20 +++++++++++++++++++
> 2 files changed, 21 insertions(+)
> create mode 100644 Documentation/driver-api/remoteproc/index.rst
>
> diff --git a/Documentation/driver-api/index.rst b/Documentation/driver-api/index.rst
> index c57c609ad2eb..ec9d669b92e5 100644
> --- a/Documentation/driver-api/index.rst
> +++ b/Documentation/driver-api/index.rst
> @@ -30,6 +30,7 @@ available subsections can be seen below.
> frame-buffer
> regulator
> reset
> + remoteproc/index
This patch doesn't apply to rproc-next and I'm pretty sure it is the same for
Jonathan's tree.
> iio/index
> input
> usb/index
> diff --git a/Documentation/driver-api/remoteproc/index.rst b/Documentation/driver-api/remoteproc/index.rst
> new file mode 100644
> index 000000000000..8b8c8f512e2b
> --- /dev/null
> +++ b/Documentation/driver-api/remoteproc/index.rst
> @@ -0,0 +1,20 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +========================================================================
> +remoteproc - remote processor subsystem in Linux(TM) kernel
> +========================================================================
> +
> +Authors:
> + - anish kumar <yesanishhere@gmail.com>
> +
> + remote processor subsystem is a way to manage the lifecycle of
> + a subsytem that is external to the Linux. The remoteproc framework
... external to the Linux kernel.
> + allows different platforms/architectures to control (power on,
> + load firmware, power off) those remote processors while abstracting
> + the hardware differences, so the entire driver doesn't need to be
> + duplicated.
> +
> +Mailing List
> +------------
> +To post a message, send an email to
> +linux-remoteproc@vger.kernel.org
> --
> 2.39.3 (Apple Git-146)
>
next prev parent reply other threads:[~2024-10-24 15:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 5:33 [PATCH 0/1] remoteproc documentation changes anish kumar
2024-10-23 5:33 ` [PATCH V4 1/7] Remoteproc: Documentation: add the main index anish kumar
2024-10-24 15:42 ` Mathieu Poirier [this message]
2024-10-24 17:51 ` anish kumar
2024-10-23 5:33 ` [PATCH V4 2/7] Documentation: remoteproc: move from staging anish kumar
2024-10-23 5:33 ` [PATCH V4 3/7] Documentation: remoteproc: add more information anish kumar
2024-10-24 15:53 ` Mathieu Poirier
2024-10-24 18:17 ` anish kumar
2024-10-25 14:57 ` Mathieu Poirier
2024-10-25 15:13 ` anish kumar
2024-10-25 15:18 ` Mathieu Poirier
2024-10-23 5:33 ` [PATCH V4 4/7] Remoteproc: Documentation: add driver api anish kumar
2024-10-23 5:33 ` [PATCH V4 5/7] Remoteproc: Documentation: add userspace api anish kumar
2024-10-23 5:33 ` [PATCH V4 6/7] MAINTAINERS: remoteproc documentation path update anish kumar
2024-10-23 5:33 ` [PATCH V4 7/7] rpmsg: Documentation: update the path anish kumar
2024-10-23 13:53 ` [PATCH 0/1] remoteproc documentation changes Jonathan Corbet
2024-10-23 14:43 ` Jonathan Corbet
2024-10-23 15:35 ` Mathieu Poirier
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=Zxpq1RGltdWiE5sA@p14s \
--to=mathieu.poirier@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=yesanishhere@gmail.com \
/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).