linux-kernel - Re: [PATCH 09/29] drm/modeset: Create atomic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250915-radical-vagabond-jaguar-b45157@penduick>
Date: Mon, 15 Sep 2025 13:37:28 +0200
From: Maxime Ripard <mripard@...nel.org>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, 
	Thomas Zimmermann <tzimmermann@...e.de>, David Airlie <airlied@...il.com>, 
	Simona Vetter <simona@...ll.ch>, Andrzej Hajda <andrzej.hajda@...el.com>, 
	Neil Armstrong <neil.armstrong@...aro.org>, Robert Foss <rfoss@...nel.org>, Jonas Karlman <jonas@...boo.se>, 
	Jernej Skrabec <jernej.skrabec@...il.com>, Jyri Sarha <jyri.sarha@....fi>, 
	Tomi Valkeinen <tomi.valkeinen@...asonboard.com>, Devarsh Thakkar <devarsht@...com>, 
	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 09/29] drm/modeset: Create atomic_reset hook

On Tue, Sep 02, 2025 at 11:04:45PM +0200, Laurent Pinchart wrote:
> On Tue, Sep 02, 2025 at 10:32:37AM +0200, Maxime Ripard wrote:
> > Since we're about to integrate some infrastructure to implement hardware
> > state readout, we need a way to differentiate between drivers wanting to
> > start from a pristine state, with the classic reset sequence, and
> > drivers that want to pickup their initial state from reading out the
> > hardware state.
> > 
> > To do so we can create an optional reset hook in
> > drm_mode_config_helper_funcs that will default to the classic reset
> > implementation, and can be setup to a helper we will provide in a later
> > patch to read the hardware state.
> 
> I'm a bit puzzled by this. Isn't the whole point of the existing reset
> operations to allow drivers to read out the hardware state if they wish
> ? Why do we need something new ?

I'm creating a callback for drivers to select whether they want the
current reset behaviour (ie, start from a pristine, default state) or
implement readout through a set of helpers.

What's puzzling you?

Download attachment "signature.asc" of type "application/pgp-signature" (270 bytes)