| Message ID | 20201121030156.22857-1-s-anna@ti.com (mailing list archive) |
|---|---|
| Headers | show |
| Series | remoteproc sysfs fixes/improvements | expand |
Hi all. Am Sa., 21. Nov. 2020 um 04:05 Uhr schrieb Suman Anna <s-anna@ti.com>: > > Hi All, > > This is a refresh of the unaccepted patches from an old series [1]. > Patches 2 and 3 from that series were merged and these are rebased and > revised versions of the same patches. I had forgotten about these patches, > and am resurrecting these again. Patches are on top of latest 5.10-rc4. > > The features being introduced here will be needed by the recently posted PRU > remoteproc driver [2] 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. > > regards > Suman > > [1] https://patchwork.kernel.org/project/linux-remoteproc/cover/20180915003725.17549-1-s-anna@ti.com/ > [2] https://patchwork.kernel.org/project/linux-remoteproc/cover/20201119140850.12268-1-grzegorz.jaszczyk@linaro.org/ > > Suman Anna (3): > remoteproc: Fix unbalanced boot with sysfs for no auto-boot rprocs > remoteproc: Introduce deny_sysfs_ops flag > remoteproc: wkup_m3: Set deny_sysfs_ops flag > > drivers/remoteproc/remoteproc_sysfs.c | 28 ++++++++++++++++++++++++++- > drivers/remoteproc/wkup_m3_rproc.c | 1 + > include/linux/remoteproc.h | 2 ++ > 3 files changed, 30 insertions(+), 1 deletion(-) > > -- > 2.28.0 > Is there any update on this patch series?