Hello Anish,
On 10/26/24 23:22, anish kumar wrote:
> Added details as below:
> 1. added sysfs information
> 2. verbose details about remoteproc driver/framework
>responsibilites.
> 3. example for resource request
>
> Signed-off-by: anish kumar
> ---
> V5:
> based on comment from mathieu poir
On Fri, Nov 01, 2024 at 09:41:26AM -0600, Mathieu Poirier wrote:
> Before spinning off another revision I encourage you to spend time looking at
> existing documentation. Reading various mailing lists with a special
> focus on how people split their patches based on topics would also be
> benefici
On Fri, Nov 1, 2024 at 8:41 AM Mathieu Poirier
wrote:
>
> On Sat, Oct 26, 2024 at 02:22:59PM -0700, anish kumar wrote:
> > Added details as below:
> > 1. added sysfs information
> > 2. verbose details about remoteproc driver/framework
> >responsibilites.
> > 3. example for resource request
> >
On Sat, Oct 26, 2024 at 02:22:59PM -0700, anish kumar wrote:
> Added details as below:
> 1. added sysfs information
> 2. verbose details about remoteproc driver/framework
>responsibilites.
> 3. example for resource request
>
> Signed-off-by: anish kumar
> ---
> V5:
> based on comment from mat
On Sat, Oct 26, 2024 at 02:22:59PM -0700, anish kumar wrote:
> +The rproc device structure looks like this::
> +
> + struct rproc {
> + struct list_head node;
> + struct iommu_domain *domain;
> + const char *name;
> + const char *firmware;
> + void *priv;
> + struct rproc_o
Added details as below:
1. added sysfs information
2. verbose details about remoteproc driver/framework
responsibilites.
3. example for resource request
Signed-off-by: anish kumar
---
V5:
based on comment from mathieu poirier, remove all files
and combined that in the original file and as he a
