Re: [PATCH 13/13] mailbox: omap: Remove kernel FIFO message queuing

2024-04-01 Thread Hari Nagalla
On 3/25/24 12:20, Andrew Davis wrote: The kernel FIFO queue has a couple issues. The biggest issue is that it causes extra latency in a path that can be used in real-time tasks, such as communication with real-time remote processors. The whole FIFO idea itself looks to be a leftover from before

Re: [PATCH 12/13] mailbox: omap: Reverse FIFO busy check logic

2024-04-01 Thread Hari Nagalla
On 3/25/24 12:20, Andrew Davis wrote: static int omap_mbox_chan_send_noirq(struct omap_mbox *mbox, u32 msg) { - int ret = -EBUSY; + if (mbox_fifo_full(mbox)) + return -EBUSY; - if (!mbox_fifo_full(mbox)) { - omap_mbox_enable_irq(mbox, IRQ_RX); -

[PATCH v7 3/5] remoteproc: k3: Move out functions common with M4 driver

2024-02-02 Thread Hari Nagalla
From: Martyn Welch In the next commit we will be adding the M4F driver which shares a lot of commonality with the DSP driver. Move this shared functionality out so that it can be used by both drivers. Signed-off-by: Martyn Welch Signed-off-by: Hari Nagalla --- Changes since v2: - New patch

[PATCH v7 4/5] remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem

2024-02-02 Thread Hari Nagalla
and the other, a local reset is only for the M4F processing core. When loading the image, the driver first releases the subsystem reset, loads the firmware image and then releases the local reset to let the M4F processing core run. Signed-off-by: Martyn Welch Signed-off-by: Hari Nagalla

[PATCH v7 1/5] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs

2024-02-02 Thread Hari Nagalla
subsystems. The YAML binding document provides the various node properties to be configured by the consumers of the M4F subsystem. Signed-off-by: Martyn Welch Signed-off-by: Hari Nagalla --- Changes since v1: - Spelling corrections - Corrected to pass DT checks Changes since v2: - Missed spelling

[PATCH v7 5/5] arm64: defconfig: Enable TI K3 M4 remote proc driver

2024-02-02 Thread Hari Nagalla
Enable CONFIG_TI_K3_M4_REMOTEPROC Some K3 platform devices (AM64x, AM62x) have a Cortex M4 core. Build the M4 remote proc driver as a module for these platforms. Signed-off-by: Hari Nagalla --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs

[PATCH v7 2/5] remoteproc: k3: Move out data structures common with M4 driver

2024-02-02 Thread Hari Nagalla
From: Martyn Welch We will be adding the M4F driver which shares a lot of commonality with the DSP driver. Common data structures are introduced here. Signed-off-by: Martyn Welch Signed-off-by: Hari Nagalla --- Changes since v5: - Created a separate patch for data structures to ease review

[PATCH v7 0/5] TI K3 M4F support on AM64x and AM62x SoCs

2024-02-02 Thread Hari Nagalla
/5ba77847343f22b5f9ec2b7aeabc410aaf8cdf45 Hari Nagalla (2): dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs arm64: defconfig: Enable TI K3 M4 remote proc driver Martyn Welch (3): remoteproc: k3: Move out data structures common with M4 driver remoteproc: k3: Move out functions common with M4

Re: [PATCH v3 3/5] remoteproc: k3-r5: Add support for IPC-only mode for all R5Fs

2023-12-08 Thread Hari Nagalla
On 11/2/23 11:43, Jan Kiszka wrote: RTI1 watchdog also powers up R5F core 1. And this could happen either in When writing "... also powers up...", other than R5F core 1, what else is being powered? Would be a question for the SoC vendor - I assumed that only mcu_rti1 [1] goes on when enabling

Re: [PATCH v6 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs

2023-09-13 Thread Hari Nagalla
.yaml# >> +$schema:http://devicetree.org/meta-schemas/core.yaml# >> + >> +title: TI K3 M4F processor subsystems >> + >> +maintainers: >> + - Hari Nagalla >> + - Mathieu Poirier > Are you sure Mathieu has this device and is a maintainer of this device?

[PATCH v6 3/4] remoteproc: k3: Split out functions common with M4 driver

2023-09-13 Thread Hari Nagalla
From: Martyn Welch In the next commit we will be adding the M4F driver which shares a lot of commonality with the DSP driver. Split this shared functionality out so that it can be used by both drivers. Signed-off-by: Martyn Welch Signed-off-by: Hari Nagalla --- Changes since v2: - New patch

[PATCH v6 4/4] remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem

2023-09-13 Thread Hari Nagalla
and the other, a local reset is only for the M4F processing core. When loading the image, the driver first releases the subsystem reset, loads the firmware image and then releases the local reset to let the M4F processing core run. Signed-off-by: Martyn Welch Signed-off-by: Hari Nagalla

[PATCH v6 1/4] dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs

2023-09-13 Thread Hari Nagalla
subsystems. The YAML binding document provides the various node properties to be configured by the consumers of the M4F subsystem. Signed-off-by: Martyn Welch Signed-off-by: Hari Nagalla --- Changes since v1: - Spelling corrections - Corrected to pass DT checks Changes since v2: - Missed spelling

[PATCH v6 0/4] TI K3 M4F support on AM64x and AM62x SoCs

2023-09-13 Thread Hari Nagalla
2022) for further details: https://www.ti.com/lit/pdf/SPRUIV7A Hari Nagalla (1): dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs Martyn Welch (3): remoteproc: k3: Split out data structures common with M4 driver remoteproc: k3: Split out functions common with M4 driver remoteproc: k3-m4

[PATCH v6 2/4] remoteproc: k3: Split out data structures common with M4 driver

2023-09-13 Thread Hari Nagalla
From: Martyn Welch We will be adding the M4F driver which shares a lot of commonality with the DSP driver. Common data structures are introduced here. Signed-off-by: Martyn Welch Signed-off-by: Hari Nagalla --- Changes in v6: - Created a separate patch for data structures to ease review