Linux Remote Processor Subsystem development
 help / color / mirror / Atom feed
From: Puranjay Mohan <p-mohan@ti.com>
To: <kishon@ti.com>, <vigneshr@ti.com>, <s-anna@ti.com>,
	<bjorn.andersson@linaro.org>, <mathieu.poirier@linaro.org>,
	<linux-remoteproc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Cc: Puranjay Mohan <p-mohan@ti.com>
Subject: [PATCH v5 0/2] remoteproc sysfs fixes/improvements
Date: Wed, 16 Feb 2022 13:42:22 +0530	[thread overview]
Message-ID: <20220216081224.9956-1-p-mohan@ti.com> (raw)

This is a refresh of the patches from an old series [1].
Patch 1 of that series is not required now as [2] serves its purpose.
Patch 2 has been improved and is being posted here.
Patch 3 is unchanged, it has been rebased and posted.

The features being introduced here will be needed by the recently posted PRU 
remoteproc driver [3] in addition to the existing Wkup M3 remoteproc driver.
Both of these drivers follow a client-driven boot methodology, with the latter
strictly booted by another driver in kernel. The PRU remoteproc driver will be
supporting both in-kernel clients as well as control from userspace orthogonally.
The logic though is applicable and useful to any remoteproc driver not using
'auto-boot' and using an external driver/application to boot the remoteproc.

[1] https://patchwork.kernel.org/project/linux-remoteproc/cover/20201121030156.22857-1-s-anna@ti.com/
[2] https://patchwork.kernel.org/project/linux-remoteproc/patch/20201126210642.897302-4-mathieu.poirier@linaro.org/
[3] https://patchwork.kernel.org/project/linux-remoteproc/cover/20201119140850.12268-1-grzegorz.jaszczyk@linaro.org/

Puranjay Mohan (1):
  remoteproc: Introduce sysfs_read_only flag

Suman Anna (1):
  remoteproc: wkup_m3: Set sysfs_read_only flag

 drivers/remoteproc/remoteproc_sysfs.c | 19 ++++++++++++++++++-
 drivers/remoteproc/wkup_m3_rproc.c    |  1 +
 include/linux/remoteproc.h            |  2 ++
 3 files changed, 21 insertions(+), 1 deletion(-)

-- 
2.17.1


             reply	other threads:[~2022-02-16  8:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16  8:12 Puranjay Mohan [this message]
2022-02-16  8:12 ` [PATCH v5 1/2] remoteproc: Introduce sysfs_read_only flag Puranjay Mohan
2022-02-16 20:04   ` Bjorn Andersson
2022-02-17  6:14     ` Puranjay Mohan
2022-02-18  5:00   ` Kishon Vijay Abraham I
2022-02-18  5:54     ` Bjorn Andersson
2022-03-03  8:00       ` [EXTERNAL] " Puranjay Mohan
2022-03-04 16:53         ` Mathieu Poirier
2022-02-16  8:12 ` [PATCH v5 2/2] remoteproc: wkup_m3: Set " Puranjay Mohan

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=20220216081224.9956-1-p-mohan@ti.com \
    --to=p-mohan@ti.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=kishon@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=s-anna@ti.com \
    --cc=vigneshr@ti.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