All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiaxing Hu <gahing@gahingwoo.com>
To: royalnet026@gmail.com
Cc: tomeu@tomeuvizoso.net, linux-rockchip@lists.infradead.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] accel/rocket: search every core slot when a core is removed
Date: Sat,  5 Sep 2026 21:01:34 +1200	[thread overview]
Message-ID: <20260905090134.239404-1-gahing@gahingwoo.com> (raw)
In-Reply-To: <20260904125936.26234-1-royalnet026@gmail.com>

Hi Igor,

Two unbind and bind rounds on a Radxa ROCK 4D: bound: 0, then bound: 2
with the cores numbered 0 and 1 both times, and nine models decoded
identically afterwards. Moved here from the DVFS thread so that b4 can
collect it.

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

Jiaxing

WARNING: multiple messages have this Message-ID (diff)
From: Jiaxing Hu <gahing@gahingwoo.com>
To: royalnet026@gmail.com
Cc: tomeu@tomeuvizoso.net, linux-rockchip@lists.infradead.org,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] accel/rocket: search every core slot when a core is removed
Date: Sat,  5 Sep 2026 21:01:34 +1200	[thread overview]
Message-ID: <20260905090134.239404-1-gahing@gahingwoo.com> (raw)
In-Reply-To: <20260904125936.26234-1-royalnet026@gmail.com>

Hi Igor,

Two unbind and bind rounds on a Radxa ROCK 4D: bound: 0, then bound: 2
with the cores numbered 0 and 1 both times, and nine models decoded
identically afterwards. Moved here from the DVFS thread so that b4 can
collect it.

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

Jiaxing

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

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 12:59 [PATCH] accel/rocket: search every core slot when a core is removed Igor Paunovic
2026-09-04 12:59 ` Igor Paunovic
2026-09-04 13:15 ` sashiko-bot
2026-09-04 13:59 ` Igor Paunovic
2026-09-04 13:59   ` Igor Paunovic
2026-09-05  9:01 ` Jiaxing Hu [this message]
2026-09-05  9:01   ` Jiaxing Hu
2026-09-05 15:13   ` Igor Paunovic
2026-09-05 15:13     ` Igor Paunovic
2026-09-05 13:25 ` Sidong Yang
2026-09-05 13:25   ` Sidong Yang
2026-09-05 15:11   ` Igor Paunovic
2026-09-05 15:11     ` Igor Paunovic

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