From: "Padhi, Beleswar" <b-padhi@ti.com>
To: Siddharth Karanam <sid9.karanam@gmail.com>,
<andersson@kernel.org>, <mathieu.poirier@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-remoteproc@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] remoteproc: Merge ti_sci_dev and ti_sci_proc abstraction
Date: Tue, 27 Oct 2026 19:41:44 +0530 [thread overview]
Message-ID: <11c794c1-6fb2-4a21-a127-4762c6f45699@ti.com> (raw)
In-Reply-To: <20261014103241.3847-1-sid9.karanam@gmail.com>
On 10/14/2026 4:02 PM, Siddharth Karanam wrote:
> The previous version of the patch had a new header ti_sci_dev.h,
> that mirrors ti_sci_proc.h in terms of the struct decl and
> its helper function structure, with the goal of abstracting
> all ti_sci_handle's members like ti_sci_dev_ops from being
> invoked directly in the driver code.
>
> Lore link to the v1 patch:
> https://lore.kernel.org/all/20260922191453.324983-1-sid9.karanam@gmail.com/
>
> Upon discussing in the original patch thread, it seemed
> better to combine ti_sci_proc.h and ti_sci_dev.h's structs
> and merge all their helpers into a single header. That is
> what ti_sci_ctrl.h aims to do: It has the union of tsd
> (ti_sci_dev) and tsp (ti_sci_proc) and both their helper
> functions are prefixed with ti_sci_ctrl_dev and
> ti_sci_ctrl_proc respectively.
>
> The goal of the patch (v2) is to maintain a single source of origin
> for all ti_sci_dev/proc_ops call sites. Any stray calls
> to dev_ops/proc_ops function pointer members in driver code should
> eventually be abstracted through this header (ti_sci_ctrl.h).
>
> In the future we can try to abstract tsd's dev_ops even further
> through pm_runtime, but there are some roadblocks that
> I am unaware of, so that warranties a different patch.
You might be interested in this:
https://lore.kernel.org/all/20261027140751.2465743-1-b-padhi@ti.com/
Thanks,
Beleswar
>
> Siddharth Karanam (2):
> remoteproc: Add ti_sci_dev_ops abstraction
> remoteproc: Merge ti_sci_dev and ti_sci_proc abstraction
>
> drivers/remoteproc/ti_k3_common.c | 21 +--
> drivers/remoteproc/ti_k3_common.h | 6 +-
> drivers/remoteproc/ti_k3_dsp_remoteproc.c | 26 ++--
> drivers/remoteproc/ti_k3_m4_remoteproc.c | 23 ++-
> drivers/remoteproc/ti_k3_r5_remoteproc.c | 66 +++-----
> drivers/remoteproc/ti_sci_ctrl.h | 177 ++++++++++++++++++++++
> drivers/remoteproc/ti_sci_proc.h | 130 ----------------
> 7 files changed, 231 insertions(+), 218 deletions(-)
> create mode 100644 drivers/remoteproc/ti_sci_ctrl.h
> delete mode 100644 drivers/remoteproc/ti_sci_proc.h
>
next prev parent reply other threads:[~2026-10-27 14:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 10:32 Siddharth Karanam
2026-10-14 10:32 ` [PATCH v2 1/2] remoteproc: Add ti_sci_dev_ops abstraction Siddharth Karanam
2026-10-29 8:37 ` Padhi, Beleswar
2026-10-29 10:52 ` Beleswar Prasad Padhi
2026-10-14 10:32 ` [PATCH v2 2/2] remoteproc: Merge ti_sci_dev and ti_sci_proc abstraction Siddharth Karanam
2026-10-29 8:33 ` Padhi, Beleswar
2026-10-29 10:24 ` Sidd
2026-10-29 10:45 ` Beleswar Prasad Padhi
2026-10-29 11:00 ` Sidd
2026-10-29 13:04 ` Padhi, Beleswar
2026-10-30 11:49 ` Sidd
2026-11-03 4:14 ` Beleswar Prasad Padhi
2026-10-22 16:45 ` [PATCH v2 0/2] " Mathieu Poirier
2026-10-27 14:11 ` Padhi, Beleswar [this message]
2026-10-28 6:31 ` Sidd
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=11c794c1-6fb2-4a21-a127-4762c6f45699@ti.com \
--to=b-padhi@ti.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=sid9.karanam@gmail.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®