| author | Suman Anna <s-anna@ti.com> | |
| Tue, 19 Feb 2019 02:03:11 +0000 (20:03 -0600) | ||
| committer | Suman Anna <s-anna@ti.com> | |
| Sun, 24 Feb 2019 01:20:51 +0000 (19:20 -0600) | ||
| commit | f21ae007405457dc0b6fec6c4506561c96c30410 | |
| tree | 3e8cc36b0456a2081ed61dacb52ac8bdf360df3d | tree | snapshot (tar.xz tar.gz zip) |
| parent | 134a38de54986da890e45aa73d3a8ca4e76d3ac0 | commit | diff |
remoteproc/pru: deny rproc sysfs ops for PRU client driven boots
The PRU remoteproc driver is not configured for 'auto-boot' by default,
and allows to be booted either by in-kernel PRU client drivers or by
userspace using the generic remoteproc sysfs interfaces. The sysfs
interfaces should not be permitted to change the remoteproc firmwares
or states when a PRU is being managed by an in-kernel client driver.
Use the newly introduced remoteproc generic 'deny_sysfs_ops' flag to
provide these restrictions by setting and clearing it appropriately
during the PRU acquire and release steps.
Signed-off-by: Suman Anna <s-anna@ti.com>
The PRU remoteproc driver is not configured for 'auto-boot' by default,
and allows to be booted either by in-kernel PRU client drivers or by
userspace using the generic remoteproc sysfs interfaces. The sysfs
interfaces should not be permitted to change the remoteproc firmwares
or states when a PRU is being managed by an in-kernel client driver.
Use the newly introduced remoteproc generic 'deny_sysfs_ops' flag to
provide these restrictions by setting and clearing it appropriately
during the PRU acquire and release steps.
Signed-off-by: Suman Anna <s-anna@ti.com>
| drivers/remoteproc/pru_rproc.c | diff | blob | history |