From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: anish kumar <yesanishhere@gmail.com>
Cc: andersson@kernel.org, corbet@lwn.net,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-remoteproc@vger.kernel.org
Subject: Re: [RESEND PATCH V6 1/3] Documentation: remoteproc: update introduction section
Date: Wed, 13 Nov 2024 09:49:58 -0700 [thread overview]
Message-ID: <ZzTYtn5jple+dbMU@p14s> (raw)
In-Reply-To: <20241106051016.89113-2-yesanishhere@gmail.com>
On Tue, Nov 05, 2024 at 09:10:14PM -0800, anish kumar wrote:
> Update the intrduction section to add key components
> provided by remote processor framework.
>
> Signed-off-by: anish kumar <yesanishhere@gmail.com>
> ---
> Documentation/staging/remoteproc.rst | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/Documentation/staging/remoteproc.rst b/Documentation/staging/remoteproc.rst
> index 348ee7e508ac..eeebbeca71de 100644
> --- a/Documentation/staging/remoteproc.rst
> +++ b/Documentation/staging/remoteproc.rst
> @@ -29,6 +29,23 @@ remoteproc will add those devices. This makes it possible to reuse the
> existing virtio drivers with remote processor backends at a minimal development
> cost.
>
> +The primary purpose of the remoteproc framework is to download firmware
> +for remote processors and manage their lifecycle. The framework consists
> +of several key components:
> +
> +- **Character Driver**: Provides userspace access to control the remote
> + processor.
> +- **ELF Utility**: Offers functions for handling ELF files and managing
> + resources requested by the remote processor.
> +- **Remoteproc Core**: Manages firmware downloads and recovery actions
> + in case of a remote processor crash.
> +- **Coredump**: Provides facilities for coredumping and tracing from
> + the remote processor in the event of a crash.
> +- **Userspace Interaction**: Uses sysfs and debugfs to manage the
> + lifecycle and status of the remote processor.
> +- **Virtio Support**: Facilitates interaction with the virtio and
> + rpmsg bus.
Some of the above is either inaccurate or incomplete. It would be fairly time
consuming for me to point out where the problems are, especially since I don't
see a lot of value in adding this section.
> +
> User API
> ========
>
> --
> 2.39.3 (Apple Git-146)
>
next prev parent reply other threads:[~2024-11-13 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 5:10 [RESEND PATCH V6 0/3] remoteproc documentation update anish kumar
2024-11-06 5:10 ` [RESEND PATCH V6 1/3] Documentation: remoteproc: update introduction section anish kumar
2024-11-13 16:49 ` Mathieu Poirier [this message]
2024-11-06 5:10 ` [RESEND PATCH V6 2/3] Documentation: remoteproc: add overview section anish kumar
2024-11-13 17:13 ` Mathieu Poirier
2024-11-06 5:10 ` [RESEND PATCH V6 3/3] Documentation: remoteproc: add a note to rproc_add anish kumar
2024-11-12 20:09 ` Jonathan Corbet
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=ZzTYtn5jple+dbMU@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--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).