Rust for Linux List
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@kernel.org>
To: dakr@kernel.org, aliceryhl@google.com,
	daniel.almeida@collabora.com, boris.brezillon@collabora.com,
	deborah.brouwer@collabora.com, gary@garyguo.net
Cc: dri-devel@lists.freedesktop.org, rust-for-linux@vger.kernel.org
Subject: [PATCH 0/2] drm: tyr: use lifetime-bound IoMem
Date: Fri, 29 May 2026 02:00:52 +0200	[thread overview]
Message-ID: <20260529000106.2257996-1-dakr@kernel.org> (raw)

Adopt the driver core lifetime infrastructure for tyr.

Separate the driver type from the driver data and use lifetime-bound
IoMem directly in probe instead of wrapping it in Devres and Arc,
simplifying register access.

Changes in v2:
  - Don't return Result from GpuInfo::new()
  - Use "drm/tyr:" commit message prefix

Danilo Krummrich (2):
  drm/tyr: separate driver type from driver data
  drm/tyr: use IoMem directly instead of Devres

 drivers/gpu/drm/tyr/driver.rs | 29 ++++++++++++-----------------
 drivers/gpu/drm/tyr/gpu.rs    | 17 +++++------------
 drivers/gpu/drm/tyr/tyr.rs    |  4 ++--
 3 files changed, 19 insertions(+), 31 deletions(-)


base-commit: a3e50e7279996cd987001fd8a3db36e72665f8f7
-- 
2.54.0


             reply	other threads:[~2026-05-29  0:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29  0:00 Danilo Krummrich [this message]
2026-05-29  0:00 ` [PATCH v2 1/2] drm/tyr: separate driver type from driver data Danilo Krummrich
2026-05-29  1:57   ` Alexandre Courbot
2026-05-29  0:00 ` [PATCH v2 2/2] drm/tyr: use IoMem directly instead of Devres Danilo Krummrich
2026-06-01  9:35   ` Alice Ryhl
2026-06-01  9:54     ` Danilo Krummrich
2026-06-02  1:12     ` Deborah Brouwer
2026-06-02  0:50   ` Deborah Brouwer
  -- strict thread matches above, loose matches on Subject: below --
2026-05-25 23:01 [PATCH 0/2] drm: tyr: use lifetime-bound IoMem Danilo Krummrich

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=20260529000106.2257996-1-dakr@kernel.org \
    --to=dakr@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=boris.brezillon@collabora.com \
    --cc=daniel.almeida@collabora.com \
    --cc=deborah.brouwer@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=rust-for-linux@vger.kernel.org \
    /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