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?
signature.asc
Description: PGP signature
