mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Beleswar Prasad Padhi <b-padhi@ti.com>
To: <andersson@kernel.org>, <mathieu.poirier@linaro.org>
Cc: <afd@ti.com>, <hnagalla@ti.com>, <u-kumar1@ti.com>, <jm@ti.com>,
	<jan.kiszka@siemens.com>, <christophe.jaillet@wanadoo.fr>,
	<jkangas@redhat.com>, <eballetbo@redhat.com>,
	<linux-remoteproc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v9 00/26] Refactor TI K3 R5, DSP and M4 Remoteproc Drivers
Date: Mon, 7 Apr 2025 18:34:22 +0530	[thread overview]
Message-ID: <0e299cf4-da72-4ce1-b2c8-a625fe74040b@ti.com> (raw)
In-Reply-To: <20250317120622.1746415-1-b-padhi@ti.com>


On 17/03/25 17:35, Beleswar Padhi wrote:
> This series refactors a lot of functions & callbacks from
> ti_k3_dsp_remoteproc.c, ti_k3_r5_remoteproc.c and ti_k3_m4_remoteproc.c
> drivers. This is a consolidated and final series as part of the
> refactoring of K3 remoteproc drivers. Below is the breakdown:
> 1. PATCHES #1-#5 does the pre-cleanup and aligns R5, DSP, M4 data structures.
> 2. PATCHES #6-#8 fixes important bugs in R5 and DSP drivers before refactoring
> them into a common driver.
> 3. PATCHES #9-#26 does the actual refactoring from into ti_k3_common.c driver.


Requesting review on this patchset.

Thanks,
Beleswar

>
> NOTE:
> This series supersedes below series:
> https://lore.kernel.org/all/20250219091042.263819-1-b-padhi@ti.com/
> https://lore.kernel.org/all/20250103101231.1508151-1-b-padhi@ti.com/
> https://lore.kernel.org/all/20250108063727.1416324-1-b-padhi@ti.com/
>
> Testing Done:
> 1. Tested boot of R5Fs, C66x DSPs, C71x DSPs across Jacinto J7* devices in
> remoteproc mode and IPC-Only mode.
> 2. Tested boot of M4F core _only_ in _AM62xx SK_ board in Remoteproc mode and
> IPC-Only mode.
> 3. Tested Core stop and detach operations from sysfs for R5Fs, C66x DSPs, C71x DSPs
> 4. Tested device removal paths by executing 'modprobe -r ti_k3_dsp_remoteproc'
> and 'modprobe -r ti_k3_r5_remoteproc'.
> 5. Tested usecases where firmware not available at device probe time, but
> later in sysfs, able to load firmware into a remotecore and start it. [R5Fs]
> 6. Tested that each patch in this series generates no new warnings/errors.
>
> v9: Changelog:
> 1. Added R5 cleanup & refactoring along with existing DSP, M4 refactoring into this series. [Andrew]
> 2. Dropped Mailbox level IPC checks across R5, DSP, M4 drivers in IPC-only mode. [Andrew]
>
> Link to v8:
> https://lore.kernel.org/all/20250103101231.1508151-1-b-padhi@ti.com/
>
> v8: Changelog:
> 1. Broken down refactoring into patches, each patch dealing with one function
> for ease in review. [Andrew]
>
> Links to older versions:
> v7: https://lore.kernel.org/all/20240202175538.1705-1-hnagalla@ti.com/
> v6: https://lore.kernel.org/all/20230913111644.29889-1-hnagalla@ti.com/
> v5: https://lore.kernel.org/all/20230808044529.25925-1-hnagalla@ti.com/
> v4: https://lore.kernel.org/all/20230801141117.2559-1-hnagalla@ti.com/
> v3: https://lore.kernel.org/all/20230302171450.1598576-1-martyn.welch@collabora.com/
> v2:
> https://lore.kernel.org/all/20230301111323.1532479-4-martyn.welch@collabora.com/
> v1: https://lore.kernel.org/all/20220110040650.18186-1-hnagalla@ti.com/
>
> Thanks,
> Beleswar
>
> Beleswar Padhi (24):
>    remoteproc: k3-r5: Re-order internal memory initialization function
>    remoteproc: k3-r5: Refactor Data Structures to Align with DSP and M4
>    remoteproc: k3-r5: Use k3_r5_rproc_mem_data structure for memory info
>    remoteproc: k3-{m4/dsp}: Align internal rproc data structure with R5
>    remoteproc: k3-m4: Use k3_rproc_mem_data structure for memory info
>    remoteproc: k3-r5: Refactor sequential core power up/down operations
>    remoteproc: k3: Refactor shared data structures
>    remoteproc: k3: Refactor mailbox rx_callback functions into common
>      driver
>    remoteproc: k3: Refactor .kick rproc ops into common driver
>    remoteproc: k3: Refactor rproc_reset() implementation into common
>      driver
>    remoteproc: k3: Refactor rproc_release() implementation into common
>      driver
>    remoteproc: k3: Refactor rproc_request_mbox() implementations into
>      common driver
>    remoteproc: k3: Refactor .prepare rproc ops into common driver
>    remoteproc: k3: Refactor .unprepare rproc ops into common driver
>    remoteproc: k3: Refactor .start rproc ops into common driver
>    remoteproc: k3: Refactor .stop rproc ops into common driver
>    remoteproc: k3: Refactor .attach rproc ops into common driver
>    remoteproc: k3: Refactor .detach rproc ops into common driver
>    remoteproc: k3: Refactor .get_loaded_rsc_table ops into common driver
>    remoteproc: k3: Refactor .da_to_va rproc ops into common driver
>    remoteproc: k3: Refactor of_get_memories() functions into common
>      driver
>    remoteproc: k3: Refactor mem_release() functions into common driver
>    remoteproc: k3: Refactor reserved_mem_init() functions into common
>      driver
>    remoteproc: k3: Refactor release_tsp() functions into common driver
>
> Siddharth Vadapalli (2):
>    remoteproc: k3-r5: Drop check performed in
>      k3_r5_rproc_{mbox_callback/kick}
>    remoteproc: k3-dsp: Drop check performed in
>      k3_dsp_rproc_{mbox_callback/kick}
>
>   drivers/remoteproc/Makefile               |   4 +-
>   drivers/remoteproc/ti_k3_common.c         | 552 +++++++++++++
>   drivers/remoteproc/ti_k3_common.h         | 113 +++
>   drivers/remoteproc/ti_k3_dsp_remoteproc.c | 618 +--------------
>   drivers/remoteproc/ti_k3_m4_remoteproc.c  | 583 +-------------
>   drivers/remoteproc/ti_k3_r5_remoteproc.c  | 898 +++++++---------------
>   6 files changed, 1021 insertions(+), 1747 deletions(-)
>   create mode 100644 drivers/remoteproc/ti_k3_common.c
>   create mode 100644 drivers/remoteproc/ti_k3_common.h
>

      parent reply	other threads:[~2025-04-07 13:04 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 12:05 Beleswar Padhi
2025-03-17 12:05 ` [PATCH v9 01/26] remoteproc: k3-r5: Re-order internal memory initialization function Beleswar Padhi
2025-04-07 13:29   ` Andrew Davis
2025-04-08  8:14     ` Beleswar Prasad Padhi
2025-03-17 12:05 ` [PATCH v9 02/26] remoteproc: k3-r5: Refactor Data Structures to Align with DSP and M4 Beleswar Padhi
2025-04-07 13:33   ` Andrew Davis
2025-04-08  8:28     ` Beleswar Prasad Padhi
2025-03-17 12:05 ` [PATCH v9 03/26] remoteproc: k3-r5: Use k3_r5_rproc_mem_data structure for memory info Beleswar Padhi
2025-04-07 13:37   ` Andrew Davis
2025-03-17 12:06 ` [PATCH v9 04/26] remoteproc: k3-{m4/dsp}: Align internal rproc data structure with R5 Beleswar Padhi
2025-04-07 13:40   ` Andrew Davis
2025-03-17 12:06 ` [PATCH v9 05/26] remoteproc: k3-m4: Use k3_rproc_mem_data structure for memory info Beleswar Padhi
2025-04-07 13:43   ` Andrew Davis
2025-04-08  8:38     ` Beleswar Prasad Padhi
2025-03-17 12:06 ` [PATCH v9 06/26] remoteproc: k3-r5: Drop check performed in k3_r5_rproc_{mbox_callback/kick} Beleswar Padhi
2025-04-07 13:25   ` Andrew Davis
2025-03-17 12:06 ` [PATCH v9 07/26] remoteproc: k3-dsp: Drop check performed in k3_dsp_rproc_{mbox_callback/kick} Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 08/26] remoteproc: k3-r5: Refactor sequential core power up/down operations Beleswar Padhi
2025-04-07 13:45   ` Andrew Davis
2025-04-08  8:41     ` Beleswar Prasad Padhi
2025-03-17 12:06 ` [PATCH v9 09/26] remoteproc: k3: Refactor shared data structures Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 10/26] remoteproc: k3: Refactor mailbox rx_callback functions into common driver Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 11/26] remoteproc: k3: Refactor .kick rproc ops " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 12/26] remoteproc: k3: Refactor rproc_reset() implementation " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 13/26] remoteproc: k3: Refactor rproc_release() " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 14/26] remoteproc: k3: Refactor rproc_request_mbox() implementations " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 15/26] remoteproc: k3: Refactor .prepare rproc ops " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 16/26] remoteproc: k3: Refactor .unprepare " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 17/26] remoteproc: k3: Refactor .start " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 18/26] remoteproc: k3: Refactor .stop " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 19/26] remoteproc: k3: Refactor .attach " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 20/26] remoteproc: k3: Refactor .detach " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 21/26] remoteproc: k3: Refactor .get_loaded_rsc_table " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 22/26] remoteproc: k3: Refactor .da_to_va rproc " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 23/26] remoteproc: k3: Refactor of_get_memories() functions " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 24/26] remoteproc: k3: Refactor mem_release() " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 25/26] remoteproc: k3: Refactor reserved_mem_init() " Beleswar Padhi
2025-03-17 12:06 ` [PATCH v9 26/26] remoteproc: k3: Refactor release_tsp() " Beleswar Padhi
2025-04-07 13:04 ` Beleswar Prasad Padhi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0e299cf4-da72-4ce1-b2c8-a625fe74040b@ti.com \
    --to=b-padhi@ti.com \
    --cc=afd@ti.com \
    --cc=andersson@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=eballetbo@redhat.com \
    --cc=hnagalla@ti.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jkangas@redhat.com \
    --cc=jm@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=u-kumar1@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®