public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: thierry.reding@gmail.com, mperttunen@nvidia.com,
	airlied@gmail.com, simona@ffwll.ch, jonathanh@nvidia.com
Cc: dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH 0/5] drm/tegra: fbdev: Use client buffers
Date: Tue, 21 Apr 2026 09:29:04 +0200	[thread overview]
Message-ID: <20260421073646.144712-1-tzimmermann@suse.de> (raw)

A client buffer holds the DRM framebuffer for an in-kernel DRM
client. Until now, tegra created an internal ad-hoc framebuffer for
its fbdev emulation, while by-passing the regular interfaces used by
user-space compositors.

Convert tegra's fbdev emulation to use client buffers. Replacing the
existing code with a client buffer allows for stream-lining tegra code
and later also the fbdev helpers. The new framebuffer will be registered
against the client's file and will support handles for GEM objects. It
is then just another framebuffer within the DRM ecosystem.

Patches 1 and 2 fix problems in the fbdev-emulation code.

Patches 3 and 4 convert fbdev emulation to shared DRM interfaces and
client buffers.

Patch 5 cleans up.

Thomas Zimmermann (5):
  drm/tegra: fbdev: Do not assign to struct drm_fb_helper.info
  drm/tegra: fbdev: Remove offset into framebuffer memory
  drm/tegra: fbdev: Calculate buffer geometry with format helpers
  drm/tegra: fbdev: Use a DRM client buffer
  drm/tegra: Make tegra_fb_alloc() an internal interface

 drivers/gpu/drm/tegra/drm.h   |  5 --
 drivers/gpu/drm/tegra/fb.c    |  1 +
 drivers/gpu/drm/tegra/fbdev.c | 88 ++++++++++++++++++-----------------
 3 files changed, 47 insertions(+), 47 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-04-21  7:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21  7:29 Thomas Zimmermann [this message]
2026-04-21  7:29 ` [PATCH 1/5] drm/tegra: fbdev: Do not assign to struct drm_fb_helper.info Thomas Zimmermann
2026-04-21  7:29 ` [PATCH 2/5] drm/tegra: fbdev: Remove offset into framebuffer memory Thomas Zimmermann
2026-04-21  7:29 ` [PATCH 3/5] drm/tegra: fbdev: Calculate buffer geometry with format helpers Thomas Zimmermann
2026-04-21  7:29 ` [PATCH 4/5] drm/tegra: fbdev: Use a DRM client buffer Thomas Zimmermann
2026-04-21  7:29 ` [PATCH 5/5] drm/tegra: Make tegra_fb_alloc() an internal interface Thomas Zimmermann

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=20260421073646.144712-1-tzimmermann@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mperttunen@nvidia.com \
    --cc=simona@ffwll.ch \
    --cc=thierry.reding@gmail.com \
    /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