From: Quentin Schulz <foss+kernel@0leil.net>
To: Tomeu Vizoso <tomeu@tomeuvizoso.net>, Oded Gabbay <ogabbay@kernel.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: [PATCH] accel/rocket: factor out code with find_core_for_dev in rocket_remove
Date: Mon, 15 Dec 2025 18:07:56 +0100 [thread overview]
Message-ID: <20251215-rocket-reuse-find-core-v1-1-be86a1d2734c@cherry.de> (raw)
From: Quentin Schulz <quentin.schulz@cherry.de>
There already is a function to return the offset of the core for a given
struct device, so let's reuse that function instead of reimplementing
the same logic.
There's one change in behavior when a struct device is passed which
doesn't match any core's. Before, we would continue through
rocket_remove() but now we exit early, to match what other callers of
find_core_for_dev() (rocket_device_runtime_resume/suspend()) are doing.
This however should never happen. Aside from that, no intended change in
behavior.
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
drivers/accel/rocket/rocket_drv.c | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/accel/rocket/rocket_drv.c b/drivers/accel/rocket/rocket_drv.c
index 5c0b63f0a8f00..28bf6c602f802 100644
--- a/drivers/accel/rocket/rocket_drv.c
+++ b/drivers/accel/rocket/rocket_drv.c
@@ -180,17 +180,18 @@ static int rocket_probe(struct platform_device *pdev)
return rocket_core_init(&rdev->cores[core]);
}
+static int find_core_for_dev(struct device *dev);
+
static void rocket_remove(struct platform_device *pdev)
{
struct device *dev = &pdev->dev;
+ int core = find_core_for_dev(dev);
- for (unsigned int core = 0; core < rdev->num_cores; core++) {
- if (rdev->cores[core].dev == dev) {
- rocket_core_fini(&rdev->cores[core]);
- rdev->num_cores--;
- break;
- }
- }
+ if (core < 0)
+ return;
+
+ rocket_core_fini(&rdev->cores[core]);
+ rdev->num_cores--;
if (rdev->num_cores == 0) {
/* Last core removed, deinitialize DRM device. */
---
base-commit: a619746d25c8adafe294777cc98c47a09759b3ed
change-id: 20251215-rocket-reuse-find-core-8ecb7ed24cab
Best regards,
--
Quentin Schulz <quentin.schulz@cherry.de>
reply other threads:[~2025-12-15 17:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20251215-rocket-reuse-find-core-v1-1-be86a1d2734c@cherry.de \
--to=foss+kernel@0leil.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=ogabbay@kernel.org \
--cc=quentin.schulz@cherry.de \
--cc=tomeu@tomeuvizoso.net \
/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;
as well as URLs for NNTP newsgroup(s).