[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241106051016.89113-4-yesanishhere@gmail.com>
Date: Tue, 5 Nov 2024 21:10:16 -0800
From: anish kumar <yesanishhere@...il.com>
To: andersson@...nel.org,
mathieu.poirier@...aro.org,
corbet@....net
Cc: linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org,
linux-remoteproc@...r.kernel.org,
anish kumar <yesanishhere@...il.com>
Subject: [RESEND PATCH V6 3/3] Documentation: remoteproc: add a note to rproc_add
Added a note to the rproc_add description regarding
the availability of the resource-managed variant of the API.
Signed-off-by: anish kumar <yesanishhere@...il.com>
---
Documentation/staging/remoteproc.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/staging/remoteproc.rst b/Documentation/staging/remoteproc.rst
index e0bf68ceade8..658ef7a28dd2 100644
--- a/Documentation/staging/remoteproc.rst
+++ b/Documentation/staging/remoteproc.rst
@@ -223,6 +223,14 @@ If found, those virtio devices will be created and added, so as a result
of registering this remote processor, additional virtio drivers might get
probed.
+.. note::
+
+ there is a resource managed version of this api called devm_rproc_add.
+ Most of the times, you should use that unless you need to explicitly
+ control the rproc registration with the core. If you are using devm
+ variant of this api, then rproc_del will automatically get called when
+ driver is unloaded.
+
::
int rproc_del(struct rproc *rproc)
--
2.39.3 (Apple Git-146)
Powered by blists - more mailing lists