On Mon, 2024-01-08 at 11:44 +0200, Hogander, Jouni wrote:
> On Mon, 2024-01-08 at 11:20 +0200, Imre Deak wrote:
> > On Mon, Jan 08, 2024 at 10:31:07AM +0200, Hogander, Jouni wrote:
> > > On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> >
> > > > An unexpected modeset or connector detection by
On Mon, 2024-01-08 at 11:20 +0200, Imre Deak wrote:
> On Mon, Jan 08, 2024 at 10:31:07AM +0200, Hogander, Jouni wrote:
> > On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
>
> > > An unexpected modeset or connector detection by a user (user
> > > space
> > > or FB console) during the initializa
On Mon, Jan 08, 2024 at 10:31:07AM +0200, Hogander, Jouni wrote:
> On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> > An unexpected modeset or connector detection by a user (user space
> > or FB console) during the initialization/shutdown sequence is
> > possible either via a hotplug IRQ hand
On Thu, 2024-01-04 at 10:30 +0200, Imre Deak wrote:
> An unexpected modeset or connector detection by a user (user space or
> FB
> console) during the initialization/shutdown sequence is possible
> either
> via a hotplug IRQ handling work or via the connector sysfs
> (status/detect) interface. Thes
An unexpected modeset or connector detection by a user (user space or FB
console) during the initialization/shutdown sequence is possible either
via a hotplug IRQ handling work or via the connector sysfs
(status/detect) interface. These modesets/detections should be prevented
by disabling/flushing
