From: "Maxime Ripard" <mripard@kernel.org>
To: "Thomas Zimmermann" <tzimmermann@suse.de>
Cc: airlied@gmail.com, alexander.deucher@amd.com,
amd-gfx@lists.freedesktop.org, christian.koenig@amd.com,
dakr@kernel.org, deller@gmx.de, dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, jani.nikula@linux.intel.com,
jfalempe@redhat.com, joonas.lahtinen@linux.intel.com,
linux-fbdev@vger.kernel.org, lukas@wunner.de, lyude@redhat.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
nouveau@lists.freedesktop.org, rodrigo.vivi@intel.com,
sashiko-reviews@lists.linux.dev, simona@ffwll.ch,
tursulin@ursulin.net, "Maxime Ripard" <mripard@kernel.org>
Subject: Re: [PATCH v2 3/7] vga_switcheroo: Add pre_switch callback to client ops
Date: Tue, 08 Sep 2026 15:26:59 +0000 [thread overview]
Message-ID: <467a6478db3c7140ca9f4d0e5c11d029@kernel.org> (raw)
In-Reply-To: <20260709092215.168172-4-tzimmermann@suse.de>
On Thu, 9 Jul 2026 11:15:59 +0200, Thomas Zimmermann wrote:
> Add pre_switch to struct vga_switcheroo_client_ops to inform the
> switcheroo client about upcoming switches of the outputs.
>
> This callback is intended to replace the hard-coded call to fbdev's
> fb_switch_outputs(). With DRM supporting more clients than just fbdev
>
> [ ... ]
Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2026-09-08 15:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 9:15 [PATCH v2 0/7] vga_switcheroo, drm: Push fbcon handling into DRM clients Thomas Zimmermann
2026-07-09 9:15 ` [PATCH v2 1/7] drm/edid: Include <linux/fb.h> Thomas Zimmermann
2026-09-08 15:23 ` Maxime Ripard
2026-07-09 9:15 ` [PATCH v2 2/7] drm/client: Add acquire_outputs callback; implement for fbdev emulation Thomas Zimmermann
2026-09-08 15:24 ` Maxime Ripard
2026-07-09 9:15 ` [PATCH v2 3/7] vga_switcheroo: Add pre_switch callback to client ops Thomas Zimmermann
2026-09-08 15:26 ` Maxime Ripard [this message]
2026-07-09 9:16 ` [PATCH v2 4/7] vga_switcheroo: Add post_switch " Thomas Zimmermann
2026-09-08 15:27 ` Maxime Ripard
2026-07-09 9:16 ` [PATCH v2 5/7] drm: Implement struct vga_switcheroo_client_ops.pre_switch Thomas Zimmermann
2026-09-08 15:27 ` Maxime Ripard
2026-07-09 9:16 ` [PATCH v2 6/7] drm: Implement vga_switcheroo_client_ops.post_switch Thomas Zimmermann
2026-09-08 15:28 ` Maxime Ripard
2026-07-09 9:16 ` [PATCH v2 7/7] vga-switcheroo: Remove unused interfaces Thomas Zimmermann
2026-09-08 15:29 ` Maxime Ripard
2026-07-09 11:08 ` ✓ i915.CI.BAT: success for vga_switcheroo, drm: Push fbcon handling into DRM clients (rev2) Patchwork
2026-07-10 6:15 ` ✗ i915.CI.Full: failure " Patchwork
2026-08-25 8:03 ` [PATCH v2 0/7] vga_switcheroo, drm: Push fbcon handling into DRM clients 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=467a6478db3c7140ca9f4d0e5c11d029@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dakr@kernel.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jfalempe@redhat.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=nouveau@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
--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;
as well as URLs for NNTP newsgroup(s).