From: Siddharth Karanam <sid9.karanam@gmail.com>
To: andersson@kernel.org, mathieu.poirier@linaro.org
Cc: linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org,
Siddharth Karanam <sid9.karanam@gmail.com>
Subject: [PATCH 0/2] remoteproc: Add ti_sci_dev_ops abstraction
Date: Wed, 23 Sep 2026 00:44:51 +0530 [thread overview]
Message-ID: <20260922191453.324983-1-sid9.karanam@gmail.com> (raw)
Instead of invoking ti_sci_handle's ti_sci_dev_ops member directly
in the driver code, this abstracts the property read of
"ti,sci-dev-id" and the function pointers supported by
ti_sci_dev_ops such as is_on, get_device and put_device.
The goal of the patch is to maintain a single source
of origin for all ti_sci_dev_ops call sites. Any stray calls
to any dev_ops function pointer members in driver code should
eventually be abstracted through this header.
The second patch abstracts certain device ops' firmware logic
even further (such as get_device/put_device) via pm_runtime.
Siddharth Karanam (2):
remoteproc: Add ti_sci_dev_ops abstraction
remoteproc: k3: Abstract ti_sci_handle's dev_ops calls through
pm_runtime
drivers/remoteproc/ti_k3_common.c | 16 ++--
drivers/remoteproc/ti_k3_common.h | 4 +-
drivers/remoteproc/ti_k3_dsp_remoteproc.c | 14 ++--
drivers/remoteproc/ti_k3_m4_remoteproc.c | 13 ++--
drivers/remoteproc/ti_k3_r5_remoteproc.c | 40 ++++------
drivers/remoteproc/ti_sci_dev.h | 89 +++++++++++++++++++++++
6 files changed, 127 insertions(+), 49 deletions(-)
create mode 100644 drivers/remoteproc/ti_sci_dev.h
--
2.55.0
next reply other threads:[~2026-09-22 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 19:14 Siddharth Karanam [this message]
2026-09-22 19:14 ` [PATCH 1/2] remoteproc: Add ti_sci_dev_ops abstraction Siddharth Karanam
2026-09-28 14:39 ` Andrew Davis
2026-09-22 19:14 ` [PATCH 2/2] remoteproc: k3: Abstract ti_sci_handle's dev_ops calls through pm_runtime Siddharth Karanam
2026-09-25 16:00 ` [PATCH 0/2] remoteproc: Add ti_sci_dev_ops abstraction Mathieu Poirier
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=20260922191453.324983-1-sid9.karanam@gmail.com \
--to=sid9.karanam@gmail.com \
--cc=andersson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.