| author | Suman Anna <s-anna@ti.com> | |
| Thu, 18 Jun 2020 19:00:02 +0000 (14:00 -0500) | ||
| committer | Suman Anna <s-anna@ti.com> | |
| Fri, 19 Jun 2020 16:39:12 +0000 (11:39 -0500) | ||
| commit | db258889bfc7466a7db681073a8543ff58352d90 | |
| tree | b2ccebcd6faacaf2458544d74c9c6f76405c1d02 | tree | snapshot (tar.xz tar.gz zip) |
| parent | c4aa0ac6d5d35a09fd03d05410d3120f78012959 | commit | diff |
remoteproc/pru: Deprecate usage of pruss_intc_trigger()
The only user of the pruss_intc_trigger() API is the PRU remoteproc
driver itself. Use the API irq_set_irqchip_state() provided by the
kernel IRQ subsystem directly instead. This is in preparation for
dropping the pruss_intc_trigger() API and the corresponding header
fil, and is the recommended way going forward for any new PRU client
drivers as well.
Signed-off-by: Suman Anna <s-anna@ti.com>
The only user of the pruss_intc_trigger() API is the PRU remoteproc
driver itself. Use the API irq_set_irqchip_state() provided by the
kernel IRQ subsystem directly instead. This is in preparation for
dropping the pruss_intc_trigger() API and the corresponding header
fil, and is the recommended way going forward for any new PRU client
drivers as well.
Signed-off-by: Suman Anna <s-anna@ti.com>
| drivers/remoteproc/pru_rproc.c | diff | blob | history |