From: Igor Paunovic <royalnet026@gmail.com>
To: Tomeu Vizoso <tomeu@tomeuvizoso.net>
Cc: Igor Paunovic <royalnet026@gmail.com>,
Oded Gabbay <ogabbay@kernel.org>,
Jiaxing Hu <gahing@gahingwoo.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Sidong Yang <sidong.yang@furiosa.ai>,
Diederik de Haas <diederik@cknow-tech.com>,
Heiko Stuebner <heiko@sntech.de>,
dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] accel/rocket: request the core clocks by name
Date: Wed, 12 Aug 2026 10:33:56 +0200 [thread overview]
Message-ID: <20260812083357.60014-1-royalnet026@gmail.com> (raw)
In-Reply-To: <20260811212818.10487-1-royalnet026@gmail.com>
A correction to my own message above, before it stands uncorrected in
the archive.
I wrote that the two test reports cover "the two NanoPC-T6 variants
besides my own board". That is wrong, and it misattributes Sidong's
work. Sidong tested on a Radxa ROCK 5B+, not on a NanoPC-T6:
https://lore.kernel.org/all/20260802131328.75038-1-sidong.yang@furiosa.ai/
Diederik's report is the one covering the two NanoPC-T6 variants. So the
coverage is three boards besides mine, on three different designs:
Tested-by: Sidong Yang <sidong.yang@furiosa.ai> # Radxa ROCK 5B+
Tested-by: Diederik de Haas <diederik@cknow-tech.com> # NanoPC-T6 LTS, NanoPC-T6 Plus
Apologies to Sidong for getting his hardware wrong - his report was the
more thorough of the two, with clk_summary before and after, 90 runtime
PM cycles across the three cores, and bit-exact inference results, and
it deserved to be quoted accurately.
Nothing else in that message changes.
Igor
prev parent reply other threads:[~2026-08-12 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 13:07 Igor Paunovic
2026-08-02 13:13 ` Sidong Yang
2026-08-05 18:43 ` Diederik de Haas
2026-08-05 21:15 ` Sebastian Reichel
2026-08-11 21:28 ` Igor Paunovic
2026-08-12 8:33 ` Igor Paunovic [this message]
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=20260812083357.60014-1-royalnet026@gmail.com \
--to=royalnet026@gmail.com \
--cc=diederik@cknow-tech.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gahing@gahingwoo.com \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=ogabbay@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=sidong.yang@furiosa.ai \
--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
all inboxes | Powered by JetHome®