Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Paunovic <royalnet026@gmail.com>
To: Jiaxing Hu <gahing@gahingwoo.com>
Cc: Igor Paunovic <royalnet026@gmail.com>,
	tomeu@tomeuvizoso.net, linux-rockchip@lists.infradead.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [RFC] accel/rocket: DVFS on RK3588 - a hardware constraint, and some numbers
Date: Sat,  5 Sep 2026 09:01:16 +0200	[thread overview]
Message-ID: <20260905070121.37113-1-royalnet026@gmail.com> (raw)
In-Reply-To: <20260905051323.189794-1-gahing@gahingwoo.com>

Hi Jiaxing,

> Drop it. A Signed-off-by says I passed the patch along, and on your
> copy I did not.

Done for v2: 1/7 keeps your Reviewed-by and loses the Signed-off-by.

>   Tested-by: Jiaxing Hu <gahing@gahingwoo.com> # RK3576, two cores

Thank you. That is the second SoC for the fix, and the one where the
same code runs with a different core count. One request: the tag sits in
this thread rather than under the patch, so b4 will not see it when
Tomeu applies, and it drops a trailer I repost on your behalf as a
from/email mismatch. If you have a minute, a one-line reply with it on
the patch itself lets it be collected with the rest:

  https://lore.kernel.org/dri-devel/20260904125936.26234-1-royalnet026@gmail.com/

If not, I will carry it on the next revision should one be needed.

> an accel device takes the next free minor, so after two rebinds the
> NPU sat at /dev/accel/accel2

I saw the same here - the minor walked from 1 to 10 over ten unbind/bind
rounds, and only a module reload put it back to 0 - and I think it is
more than the next free minor. rocket_device_init() allocates the
drm_device with devm_drm_dev_alloc() against the module's "rknn"
platform device, so the drm_dev_put() that frees it hangs off that
device's devres, and that device is only unregistered in
rocket_unregister(). rocket_device_fini() calls drm_dev_unregister() and
nothing else. The minor's xa_erase() is a drmm action on the drm_device,
so it runs at the last drm_dev_put(), which does not come until module
exit. Every unbind therefore leaves one unregistered drm_device behind,
still holding its minor, and the reload is what finally frees them.
That is the devm leak the automated review raised on the fix; the
climbing minor is the visible half of it. It wants its own patch, not a
line in this thread - I will look at it once the series has had a first
round.

Glad the unbind path paid its hour back on your side. A bug found in
unsent work is the cheap kind.

Igor

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2026-09-05  7:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01 13:16 [RFC] accel/rocket: DVFS on RK3588 - a hardware constraint, and some numbers Igor Paunovic
2026-08-01 19:32 ` Jiaxing Hu
2026-08-02 12:04   ` Igor Paunovic
2026-08-15 18:24     ` Tomeu Vizoso
2026-08-17 18:22 ` Nicolas Dufresne
2026-08-18  7:27   ` Igor Paunovic
2026-08-18 12:12     ` Jonas Karlman
2026-08-18 12:30       ` Jonas Karlman
2026-08-19  5:52         ` Igor Paunovic
2026-08-19  9:40           ` Jonas Karlman
2026-08-19 12:59             ` Igor Paunovic
2026-08-19 16:20               ` Jonas Karlman
2026-08-19 18:48                 ` Igor Paunovic
2026-08-19 20:07                   ` Hüseyin BIYIK
2026-09-02 11:04                     ` Igor Paunovic
2026-09-03  9:16                       ` Igor Paunovic
     [not found]                         ` <2f88072c-6aa3-4294-a35d-722d1c7a405c@email.android.com>
2026-09-03 18:51                           ` Igor Paunovic
2026-09-04 11:08                         ` Jiaxing Hu
2026-09-04 12:46                           ` Igor Paunovic
2026-09-05  5:13                             ` Jiaxing Hu
2026-09-05  7:01                               ` Igor Paunovic [this message]
2026-08-19 18:47             ` Nicolas Dufresne
2026-09-04 11:19   ` Jiaxing Hu
     [not found] <DKDOBW9CJ2Y3.10EEIZDTXPYJZ@cknow-tech.com>
2026-08-01 14:40 ` Igor Paunovic
2026-08-01 16:29   ` Diederik de Haas

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=20260905070121.37113-1-royalnet026@gmail.com \
    --to=royalnet026@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gahing@gahingwoo.com \
    --cc=linux-rockchip@lists.infradead.org \
    --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