From: Boqun Feng <boqun.feng@gmail.com>
To: Daniel Almeida <daniel.almeida@collabora.com>
Cc: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Stone" <daniels@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Alice Ryhl" <alice.ryhl@google.com>,
"Beata Michalska" <beata.michalska@arm.com>,
"Carsten Haitzler" <carsten.haitzler@foss.arm.com>,
"Boris Brezillon" <boris.brezillon@collabora.com>,
"Ashley Smith" <ashley.smith@collabora.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
rust-for-linux@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH] Introduce Tyr
Date: Fri, 27 Jun 2025 15:56:39 -0700 [thread overview]
Message-ID: <aF8hp5-e5LrHTWfT@tardis.local> (raw)
In-Reply-To: <20250627-tyr-v1-1-cb5f4c6ced46@collabora.com>
On Fri, Jun 27, 2025 at 07:34:04PM -0300, Daniel Almeida wrote:
[...]
> +#[pin_data]
> +pub(crate) struct TyrData {
> + pub(crate) pdev: ARef<platform::Device>,
> +
> + #[pin]
> + clks: Mutex<Clocks>,
> +
> + #[pin]
> + regulators: Mutex<Regulators>,
> +
> + // Some inforation on the GPU. This is mainly queried by userspace (mesa).
> + pub(crate) gpu_info: GpuInfo,
> +}
> +
> +unsafe impl Send for TyrData {}
> +unsafe impl Sync for TyrData {}
I think you better just mark Clk (which is just a refcount to `struct
clk`) and Regulator `Send` and `Sync`?
Then `TyrData` will be `Send` and `Sync` automatically. And the total
number of `unsafe` in this patch goes down to 1.
Regards,
Boqun
> +
[...]
> +// This can be queried by userspace to get information about the GPU.
> +#[repr(C)]
> +pub(crate) struct GpuInfo {
> + pub(crate) gpu_id: u32,
> + pub(crate) csf_id: u32,
> + pub(crate) gpu_rev: u32,
> + pub(crate) core_features: u32,
> + pub(crate) l2_features: u32,
> + pub(crate) tiler_features: u32,
> + pub(crate) mem_features: u32,
> + pub(crate) mmu_features: u32,
> + pub(crate) thread_features: u32,
> + pub(crate) max_threads: u32,
> + pub(crate) thread_max_workgroup_size: u32,
> + pub(crate) thread_max_barrier_size: u32,
> + pub(crate) coherency_features: u32,
> + pub(crate) texture_features: [u32; 4],
> + pub(crate) as_present: u32,
> + pub(crate) shader_present: u64,
> + pub(crate) tiler_present: u64,
> + pub(crate) l2_present: u64,
> +}
> +
[...]
next prev parent reply other threads:[~2025-06-27 22:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 22:34 Daniel Almeida
2025-06-27 22:36 ` Daniel Almeida
2025-06-27 22:39 ` Boqun Feng
2025-06-27 22:56 ` Boqun Feng [this message]
2025-06-27 23:12 ` Danilo Krummrich
2025-06-28 0:12 ` Daniel Almeida
2025-06-28 9:31 ` Miguel Ojeda
2025-06-30 13:52 ` Rob Herring
2025-06-30 14:01 ` Daniel Almeida
2025-06-30 17:29 ` Miguel Ojeda
2025-06-30 16:06 ` Boris Brezillon
2025-06-30 16:12 ` Danilo Krummrich
2025-07-01 9:11 ` Boris Brezillon
2025-06-28 9:44 ` Miguel Ojeda
2025-06-28 13:05 ` Daniel Almeida
2025-06-28 13:49 ` FUJITA Tomonori
2025-06-28 14:29 ` Miguel Ojeda
2025-06-30 15:22 ` Daniel Almeida
2025-06-30 17:29 ` Miguel Ojeda
2025-06-28 19:55 ` Maíra Canal
2025-06-30 13:53 ` Daniel Almeida
2025-07-03 10:45 ` Maíra Canal
2025-06-30 10:11 ` Steven Price
2025-06-30 14:56 ` Daniel Almeida
2025-06-30 15:31 ` Steven Price
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=aF8hp5-e5LrHTWfT@tardis.local \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=alice.ryhl@google.com \
--cc=aliceryhl@google.com \
--cc=ashley.smith@collabora.com \
--cc=beata.michalska@arm.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boris.brezillon@collabora.com \
--cc=carsten.haitzler@foss.arm.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ojeda@kernel.org \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
--cc=tzimmermann@suse.de \
/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®