[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210407155641.5501-1-s-anna@ti.com>
Date: Wed, 7 Apr 2021 10:56:38 -0500
From: Suman Anna <s-anna@...com>
To: Bjorn Andersson <bjorn.andersson@...aro.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>
CC: Grzegorz Jaszczyk <grzegorz.jaszczyk@...aro.org>,
Jan Kiszka <jan.kiszka@...mens.com>,
Vignesh Raghavendra <vigneshr@...com>,
Lokesh Vutla <lokeshvutla@...com>,
<linux-remoteproc@...r.kernel.org>, <linux-omap@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: [PATCH v2 0/3] PRU firmware event/interrupt mapping fixes
Hi All,
The following is a minor revised version of the series [1] that includes fixes
for various different issues associated with the PRU firmware event/interrupt
mapping configuration logic. Please see the v1 cover-letter [1] for additional
details.
There are currently no in-kernel dts nodes yet in mainline kernel (first
nodes will appear in v5.13-rc1) so these can be picked up for either v5.13
merge window or the current -rc cycle.
Changes in v2:
- Picked up Reviewed-by tags on Patches 1 and 2
- Revised Patch 3 to address additional error cleanup paths as
pointed out by Mathieu.
regards
Suman
[1] https://patchwork.kernel.org/project/linux-remoteproc/cover/20210323223839.17464-1-s-anna@ti.com/
Suman Anna (3):
remoteproc: pru: Fixup interrupt-parent logic for fw events
remoteproc: pru: Fix wrong success return value for fw events
remoteproc: pru: Fix and cleanup firmware interrupt mapping logic
drivers/remoteproc/pru_rproc.c | 41 ++++++++++++++++++++++++++--------
1 file changed, 32 insertions(+), 9 deletions(-)
--
2.30.1
Powered by blists - more mailing lists