pings
lists respectively.
Signed-off-by: Beleswar Padhi
---
Testing:
1. Tested IPC with remoteprocs in attach mode in TI platforms.
[However, TI K3 platforms do not use resource table for carveouts,
all the memory regions are reserved statically in Device Tree.]
drivers/remoteproc/remoteproc_
The .detach rproc ops implementations in TI K3 R5, DSP and M4
remoteproc drivers are NOPs. Refactor the implementations into
ti_k3_common.c driver as k3_rproc_detach() and register this common
function as .detach ops in R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith
: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-20-b-pa...@ti.com/
v11: Changelog:
1. Split [v10 17/33] into [v11 18/35] and [v11 19/35].
2. Carried T/B tag.
Link to v10
is done to align the
rproc_request_mbox() implementation with R5 and DSP drivers which can be
factored out at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104
The k3_dsp_rproc_release() function erroneously deasserts the local
reset even for devices which do not support it. Even though it results
in a no-operation, Update the logic to explicitly deassert only the
global reset for devices that do not have a local reset.
Signed-off-by: Beleswar Padhi
in R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-36-b-pa...@ti.com/
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https
DDR and internal memory regions in R5, DSP and M4 drivers.
Note: The R5 SRAM memory translations are still handled in the .da_to_va
ops of the R5 remoteproc driver.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Added R/B tag.
Link to v11
The .attach rproc ops implementations in TI K3 R5, DSP and M4 drivers
are NOPs. Refactor the implementations into ti_k3_common.c driver
as k3_rproc_attach() and register this common function as .attach ops in
R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-34-b-pa...@ti.com/
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all
#x27; DT property in k3_r5_core_of_get_internal_memories().
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Assign data->num_mems to num_mems. [Mathieu]
2. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-33-b-pa...@ti.com/
v11: Change
drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-35-b-pa...@ti.com/
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all
k3_get_loaded_rsc_table() and register this common function as
.get_loaded_rsc_table ops in R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-31-b-pa
this common function when
releasing the reset on the remote processor.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-27-b-pa...@ti.com/
v11: Changelog:
1
The .stop rproc ops implementations in TI K3 DSP and M4 remoteproc
drivers put the remote processor into reset. Refactor the
implementations into ti_k3_common.c driver as k3_rproc_stop() and
register this common function as .stop ops in DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by
: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Updated the check in k3_rproc_unprepare() to look for RPROC_DETACHED.
2. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-26-b-pa...@ti.com/
v11: Changelog:
1. Carried T/B
as .prepare ops in
the DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-25-b-pa...@ti.com/
v11: Changelog:
1. Carried T/B tag.
Link to v10
it ensures local reset is asserted for subsequent core
start operations from sysfs. This is done to align the .prepare callback
of DSP with the M4 driver which can be factored out at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12
drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-22-b-pa...@ti.com/
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all
-only mode or in remoteproc mode but not both.
This is done to align the rproc ops implementations of DSP driver with
M4 driver and can be factored out at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link
The rproc_reset() implementations in TI K3 DSP and M4 remoteproc drivers
assert reset in the same way. Refactor the above function into the
ti_k3_common.c driver as k3_rproc_reset() and use it throughout DSP and
M4 drivers for resetting the remote processor.
Signed-off-by: Beleswar Padhi
Tested
release implementation with DSP
remoteproc driver and can be factored out later.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-19-b-pa...@ti.com/
v11
-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-15-b-pa...@ti.com/
v11: Changelog:
1. Don't deassert lreset back if asserting module reset fails. [Andrew]
2. Put if
The .kick rproc ops implementations in TI K3 R5, DSP and M4 remoteproc
drivers sends a mailbox message to the remote processor in the same
way. Refactor the implementations into a common function
'k3_rproc_kick()' in the ti_k3_common.c driver.
Signed-off-by: Beleswar Padhi
Acked-by: An
, k3_m4_rproc_reset() which
handles both type of devices (with and without local resets), and use it
throughout the driver to put the remote processor into reset. This is
done to align the reset implementation with DSP remoteproc driver and
can be factored out later.
Signed-off-by: Beleswar Padhi
Tested-by: Judith
The TI K3 R5, DSP and M4 remoteproc drivers share the same data
structure definitions. Refactor the shared data structures into a new
common header file, 'ti_k3_common.h', and update the drivers to use the
unified data structures.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
The ti_k3_m4_remoteproc.c driver previously hardcoded device memory
region addresses and names. Change this to use the k3_rproc_mem_data
structure to store memory information. This aligns with DSP and R5
drivers, and can be refactored out later.
Signed-off-by: Beleswar Padhi
Tested-by: Judith
The mailbox .rx_callback implementations in TI K3 R5, DSP and M4
remoteproc drivers handle inbound mailbox messages in the same way.
Introduce a common driver 'ti_k3_common.c' and refactor the
implementations into a common function 'k3_rproc_mbox_callback'() in it.
Signed-of
driver which can be
factored out at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-9-b-pa...@ti.com/
v11: Changelog:
1. Carried T/B tag
Add a pointer to the rproc struct within k3_m4_rproc internal struct.
This is done to align the M4 internal rproc data structure with R5
driver which can be factored out at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1
The ti_k3_r5_remoteproc.c driver previously hardcoded device memory
region addresses and names. Change this to use the k3_r5_rproc_mem_data
structure to store memory information. This aligns with K3 DSP and M4
drivers, and can be refactored out later.
Signed-off-by: Beleswar Padhi
Reviewed-by
lly, introduce a void *priv pointer in k3_r5_rproc that can be
typecasted to point to the k3_r5_core structure. This abstraction is
done to ensure common functionalities across R5, DSP and M4 drivers can
be refactored at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed
he tsp handle,
above k3_r5_cluster_rproc_init(), so that the later can register the
former as a devm action.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to v11:
https://lore.kernel.org/all/20250425104135.830255-6-b-pa...@ti.
invoked by the later.
While at it, also re-order the k3_r5_core_of_get_sram_memories() to keep
all the internal memory initialization functions at one place.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Reviewed-by: Andrew Davis
---
v12: Changelog:
1. Carried R/B tag.
Link to
ly mode; which leads to
resetting the rproc in detach routine.
Therefore, correct the IPC-only mode detection logic to look for
"RPROC_DETACHED" in k3_m4_rproc_unprepare() function.
Fixes: ebcf9008a895 ("remoteproc: k3-m4: Add a remoteproc driver for M4F
subsystem")
Signed-of
they deal with Core Run/Halt
operations, and as such, there is no constraint in Running or Halting
the cores of a cluster in order.
Fixes: 61f6f68447ab ("remoteproc: k3-r5: Wait for core0 power-up before
powering up core1")
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
Revie
v1: https://lore.kernel.org/all/20220110040650.18186-1-hnaga...@ti.com/
Thanks,
Beleswar
Beleswar Padhi (34):
remoteproc: k3-r5: Refactor sequential core power up/down operations
remoteproc: k3-m4: Don't assert reset in detach routine
remoteproc: k3-r5: Re-order internal memory initiali
nction triggers the probe of the Virtio
RPMsg devices associated with the remote core, which require that the
"k3_dsp_rproc_kick()" and "k3_dsp_rproc_mbox_callback()" callbacks are
functional. Hence, drop the check in the callbacks.
Fixes: ea1d6fb5b571 ("remoteproc: k3-d
nction triggers the probe of the Virtio
RPMsg devices associated with the remote core, which require that the
"k3_r5_rproc_kick()" and "k3_r5_rproc_mbox_callback()" callbacks are
functional. Hence, drop the check in the callbacks.
Fixes: f3f11cfe8907 ("remoteproc: k3-r5: Ac
drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-20-b-pa...@ti.com/
v10: Changelog:
1. Split [v9 14/26] into [v10 18/33] and [v10 19/33] patches.
Link to v9:
https
: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-24-b-pa...@ti.com/
v10: Changelog:
1. Don't remove dsp func override. Already done by [v10 20/33] patch.
Link to v9:
https://lore.kernel.or
release implementation with DSP
remoteproc driver and can be factored out later.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
0. New patch in this series.
1. Split [v10 17/33] into [v11 18/35] and [v11 19/35].
Link to v10:
https://lore.kernel.org/all
he tsp handle,
above k3_r5_cluster_rproc_init(), so that the later can register the
former as a devm action.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-6-b-pa...@ti.com/
v10: Changelog:
Add a pointer to the rproc struct within k3_m4_rproc internal struct.
This is done to align the M4 internal rproc data structure with R5
driver which can be factored out at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10
, k3_m4_rproc_reset() which
handles both type of devices (with and without local resets), and use it
throughout the driver to put the remote processor into reset. This is
done to align the reset implementation with DSP remoteproc driver and
can be factored out later.
Signed-off-by: Beleswar Padhi
Tested-by: Judith
in R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-34-b-pa...@ti.com/
v10: Changelog:
1. Update commit message to call out changes in a better way.
Link to v9
drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-33-b-pa...@ti.com/
v10: Changelog:
1. Update commit message to call out changes in a better way.
Link to v9:
https
.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-32-b-pa...@ti.com/
v10: Changelog:
1. Update commit message to call out changes in a better way.
Link to v9:
https://lore.kernel.org
#x27; DT property in k3_r5_core_of_get_internal_memories().
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-31-b-pa...@ti.com/
v10: Changelog:
1. Updated commit message to call out the changes better.
Link to v9:
htt
DDR and internal memory regions in R5, DSP and M4 drivers.
Note: The R5 SRAM memory translations are still handled in the .da_to_va
ops of the R5 remoteproc driver.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org
k3_get_loaded_rsc_table() and register this common function as
.get_loaded_rsc_table ops in R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-29-b-pa...@ti.com/
v10: Changelog:
1
The .detach rproc ops implementations in TI K3 R5, DSP and M4
remoteproc drivers are NOPs. Refactor the implementations into
ti_k3_common.c driver as k3_rproc_detach() and register this common
function as .detach ops in R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith
The .attach rproc ops implementations in TI K3 R5, DSP and M4 drivers
are NOPs. Refactor the implementations into ti_k3_common.c driver
as k3_rproc_attach() and register this common function as .attach ops in
R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11
it ensures local reset is asserted for subsequent core
start operations from sysfs. This is done to align the .prepare callback
of DSP with the M4 driver which can be factored out at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag
The .stop rproc ops implementations in TI K3 DSP and M4 remoteproc
drivers put the remote processor into reset. Refactor the
implementations into ti_k3_common.c driver as k3_rproc_stop() and
register this common function as .stop ops in DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by
this common function when
releasing the reset on the remote processor.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-25-b-pa...@ti.com/
v10: Changelog:
1. Don't remove dsp func ove
as .prepare ops in
the DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-23-b-pa...@ti.com/
v10: Changelog:
1. Split [v9 15/26] into [v10 21/33] and [v10 22/33
-only mode or in remoteproc mode but not both.
This is done to align the rproc ops implementations of DSP driver with
M4 driver and can be factored out at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https
is done to align the
rproc_request_mbox() implementation with R5 and DSP drivers which can be
factored out at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-19-b-pa...@ti
The k3_dsp_rproc_release() function erroneously deasserts the local
reset even for devices which do not support it. Even though it results
in a no-operation, Update the logic to explicitly deassert only the
global reset for devices that do not have a local reset.
Signed-off-by: Beleswar Padhi
: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Split [v10 17/33] into [v11 18/35] and [v11 19/35].
2. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-18-b-pa...@ti.com/
v10: Changelog:
1. Split [v9 13/26] into [v10 16/33] and [v10 17/33] patches
The rproc_reset() implementations in TI K3 DSP and M4 remoteproc drivers
assert reset in the same way. Refactor the above function into the
ti_k3_common.c driver as k3_rproc_reset() and use it throughout DSP and
M4 drivers for resetting the remote processor.
Signed-off-by: Beleswar Padhi
Tested
The .kick rproc ops implementations in TI K3 R5, DSP and M4 remoteproc
drivers sends a mailbox message to the remote processor in the same
way. Refactor the implementations into a common function
'k3_rproc_kick()' in the ti_k3_common.c driver.
Signed-off-by: Beleswar Padhi
Acked-by: An
-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Don't deassert lreset back if asserting module reset fails. [Andrew]
2. Put if-else block for code path with lreset and w/o lreset. [Andrew]
3. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905
The mailbox .rx_callback implementations in TI K3 R5, DSP and M4
remoteproc drivers handle inbound mailbox messages in the same way.
Introduce a common driver 'ti_k3_common.c' and refactor the
implementations into a common function 'k3_rproc_mbox_callback'() in it.
Signed-of
The TI K3 R5, DSP and M4 remoteproc drivers share the same data
structure definitions. Refactor the shared data structures into a new
common header file, 'ti_k3_common.h', and update the drivers to use the
unified data structures.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mende
The ti_k3_m4_remoteproc.c driver previously hardcoded device memory
region addresses and names. Change this to use the k3_rproc_mem_data
structure to store memory information. This aligns with DSP and R5
drivers, and can be refactored out later.
Signed-off-by: Beleswar Padhi
Tested-by: Judith
lly, introduce a void *priv pointer in k3_r5_rproc that can be
typecasted to point to the k3_r5_core structure. This abstraction is
done to ensure common functionalities across R5, DSP and M4 drivers can
be refactored at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
driver which can be
factored out at a later stage.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kernel.org/all/20250417182001.3903905-9-b-pa...@ti.com/
v10: Changelog:
1. Split [v9 04/26] into [v10 08/33] and [v10 09
The ti_k3_r5_remoteproc.c driver previously hardcoded device memory
region addresses and names. Change this to use the k3_r5_rproc_mem_data
structure to store memory information. This aligns with K3 DSP and M4
drivers, and can be refactored out later.
Signed-off-by: Beleswar Padhi
Reviewed-by
they deal with Core Run/Halt
operations, and as such, there is no constraint in Running or Halting
the cores of a cluster in order.
Fixes: 61f6f68447ab ("remoteproc: k3-r5: Wait for core0 power-up before
powering up core1")
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11
nction triggers the probe of the Virtio
RPMsg devices associated with the remote core, which require that the
"k3_dsp_rproc_kick()" and "k3_dsp_rproc_mbox_callback()" callbacks are
functional. Hence, drop the check in the callbacks.
Fixes: ea1d6fb5b571 ("remoteproc: k3-d
invoked by the later.
While at it, also re-order the k3_r5_core_of_get_sram_memories() to keep
all the internal memory initialization functions at one place.
Signed-off-by: Beleswar Padhi
Tested-by: Judith Mendez
---
v11: Changelog:
1. Carried T/B tag.
Link to v10:
https://lore.kern
https://lore.kernel.org/all/20230801141117.2559-1-hnaga...@ti.com/
v3:
https://lore.kernel.org/all/20230302171450.1598576-1-martyn.we...@collabora.com/
v2:
https://lore.kernel.org/all/2023030323.1532479-4-martyn.we...@collabora.com/
v1: https://lore.kernel.org/all/20220110040650.18186-1-hnaga...@ti.com/
Than
nction triggers the probe of the Virtio
RPMsg devices associated with the remote core, which require that the
"k3_r5_rproc_kick()" and "k3_r5_rproc_mbox_callback()" callbacks are
functional. Hence, drop the check in the callbacks.
Fixes: f3f11cfe8907 ("remoteproc: k3-r5: Ac
-only mode or in remoteproc mode but not both.
This is done to align the rproc ops implementations of DSP driver with
M4 driver and can be factored out at a later stage.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. New patch. Gets rid of overriding function pointers. Makes further
commits
-off-by: Beleswar Padhi
---
v10: Changelog:
1. Split [v9 13/26] into [v10 16/33] and [v10 17/33] patches.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-14-b-pa...@ti.com/
drivers/remoteproc/ti_k3_dsp_remoteproc.c | 26 +++
1 file changed, 12 insertions
The .detach rproc ops implementations in TI K3 R5, DSP and M4
remoteproc drivers are NOPs. Refactor the implementations into
ti_k3_common.c driver as k3_rproc_detach() and register this common
function as .detach ops in R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1
invoked by the later.
While at it, also re-order the k3_r5_core_of_get_sram_memories() to keep
all the internal memory initialization functions at one place.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Re-ordered both core_of_get_{internal/sram}_memories() together.
2. Moved releas
The .kick rproc ops implementations in TI K3 R5, DSP and M4 remoteproc
drivers sends a mailbox message to the remote processor in the same
way. Refactor the implementations into a common function
'k3_rproc_kick()' in the ti_k3_common.c driver.
Signed-off-by: Beleswar Padhi
---
v10:
The ti_k3_m4_remoteproc.c driver previously hardcoded device memory
region addresses and names. Change this to use the k3_rproc_mem_data
structure to store memory information. This aligns with DSP and R5
drivers, and can be refactored out later.
Signed-off-by: Beleswar Padhi
---
v10: Changelog
#x27; DT property in k3_r5_core_of_get_internal_memories().
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Updated commit message to call out the changes better.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-24-b-pa...@ti.com/
drivers/remoteproc/ti_k3_common.c | 53 ++
-by: Beleswar Padhi
---
v10: Changelog:
1. Split [v9 12/26] into [v10 14/33] and [v10 15/33] patches.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-13-b-pa...@ti.com/
drivers/remoteproc/ti_k3_dsp_remoteproc.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff
DDR and internal memory regions in R5, DSP and M4 drivers.
Note: The R5 SRAM memory translations are still handled in the .da_to_va
ops of the R5 remoteproc driver.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Updated commit message to call out the changes better.
2. Don't remove dsp
is done to align the
rproc_request_mbox() implementation with R5 and DSP drivers which can be
factored out at a later stage.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Split [v9 14/26] into [v10 18/33] and [v10 19/33] patches.
Link to v9:
https://lore.kernel.org/all/20250317120622.17464
.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Update commit message to call out changes in a better way.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-25-b-pa...@ti.com/
drivers/remoteproc/ti_k3_common.c | 8
drivers/remoteproc/ti_k3_common.h
The .stop rproc ops implementations in TI K3 DSP and M4 remoteproc
drivers put the remote processor into reset. Refactor the
implementations into ti_k3_common.c driver as k3_rproc_stop() and
register this common function as .stop ops in DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
---
v10
in R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Update commit message to call out changes in a better way.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-27-b-pa...@ti.com/
drivers/remoteproc/ti_k3_common.c | 8
drivers
drivers.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Update commit message to call out changes in a better way.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-26-b-pa...@ti.com/
drivers/remoteproc/ti_k3_common.c | 70 +++
drivers/remoteproc
The .attach rproc ops implementations in TI K3 R5, DSP and M4 drivers
are NOPs. Refactor the implementations into ti_k3_common.c driver
as k3_rproc_attach() and register this common function as .attach ops in
R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Don&#
k3_get_loaded_rsc_table() and register this common function as
.get_loaded_rsc_table ops in R5, DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Don't remove dsp func override. Already done by [v10 20/33] patch.
2. Update commit message to call out changes in a better way.
Link
this common function when
releasing the reset on the remote processor.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Don't remove dsp func override. Already done by [v10 20/33] patch.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-18-b-pa...@ti.com/
drivers/remot
: Beleswar Padhi
---
v10: Changelog:
1. Don't remove dsp func override. Already done by [v10 20/33] patch.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-17-b-pa...@ti.com/
drivers/remoteproc/ti_k3_common.c | 30 ++
drivers/remoteproc/ti_k3_com
as .prepare ops in
the DSP and M4 drivers.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Split [v9 15/26] into [v10 21/33] and [v10 22/33] patches.
2. Don't remove dsp func override. Already done by [v10 20/33] patch.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-16
drivers.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Split [v9 14/26] into [v10 18/33] and [v10 19/33] patches.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-15-b-pa...@ti.com/
drivers/remoteproc/ti_k3_common.c | 36 ++
drivers/remoteproc
it ensures local reset is asserted for subsequent core
start operations from sysfs. This is done to align the .prepare callback
of DSP with the M4 driver which can be factored out at a later stage.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Split [v9 15/26] into [v10 21/33] and [v10 22
: Beleswar Padhi
---
v10: Changelog:
1. Split [v9 13/26] into [v10 16/33] and [v10 17/33] patches.
Link to v9:
https://lore.kernel.org/all/20250317120622.1746415-14-b-pa...@ti.com/
drivers/remoteproc/ti_k3_common.c | 27 ++
drivers/remoteproc/ti_k3_common.h | 1
The rproc_reset() implementations in TI K3 DSP and M4 remoteproc drivers
assert reset in the same way. Refactor the above function into the
ti_k3_common.c driver as k3_rproc_reset() and use it throughout DSP and
M4 drivers for resetting the remote processor.
Signed-off-by: Beleswar Padhi
---
v10
The mailbox .rx_callback implementations in TI K3 R5, DSP and M4
remoteproc drivers handle inbound mailbox messages in the same way.
Introduce a common driver 'ti_k3_common.c' and refactor the
implementations into a common function 'k3_rproc_mbox_callback'() in it.
Signed-of
The TI K3 R5, DSP and M4 remoteproc drivers share the same data
structure definitions. Refactor the shared data structures into a new
common header file, 'ti_k3_common.h', and update the drivers to use the
unified data structures.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
Non
Add a pointer to the rproc struct within k3_m4_rproc internal struct.
This is done to align the M4 internal rproc data structure with R5
driver which can be factored out at a later stage.
Signed-off-by: Beleswar Padhi
---
v10: Changelog:
1. Split [v9 04/26] into [v10 08/33] and [v10 09/33
1 - 100 of 205 matches
Mail list logo
