[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220209090342.13220-1-p-mohan@ti.com>
Date: Wed, 9 Feb 2022 14:33:40 +0530
From: Puranjay Mohan <p-mohan@...com>
To: <puranjay12@...il.com>, <kishon@...com>, <vigneshr@...com>,
<s-anna@...com>, <bjorn.andersson@...aro.org>,
<mathieu.poirier@...aro.org>, <linux-remoteproc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
CC: Puranjay Mohan <p-mohan@...com>
Subject: [PATCH v4 0/2] remoteproc sysfs fixes/improvements
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 deny_sysfs_ops flag
Suman Anna (1):
remoteproc: wkup_m3: Set deny_sysfs_ops flag
drivers/remoteproc/remoteproc_sysfs.c | 18 +++++++++++++++++-
drivers/remoteproc/wkup_m3_rproc.c | 1 +
include/linux/remoteproc.h | 2 ++
3 files changed, 20 insertions(+), 1 deletion(-)
--
2.17.1
Powered by blists - more mailing lists