[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPj87rPyt2+cWjM7KmpRzY4sBgaUzZBOS3FJoxF+PjkijapTag@mail.gmail.com>
Date: Tue, 20 Jan 2026 11:23:02 +0000
From: Daniel Stone <daniel@...ishbar.org>
To: Michel Dänzer <michel.daenzer@...lbox.org>
Cc: Tomasz Pakuła <tomasz.pakula.oficjalny@...il.com>,
alexander.deucher@....com, harry.wentland@....com, sunpeng.li@....com,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org, tzimmermann@...e.de,
airlied@...il.com, simona@...ll.ch, siqueira@...lia.com,
dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, bernhard.berger@...il.com
Subject: Re: [PATCH 15/17] drm/amd/display: Trigger ALLM if it's available
Hi,
On Tue, 20 Jan 2026 at 10:33, Michel Dänzer <michel.daenzer@...lbox.org> wrote:
> On 1/19/26 02:11, Tomasz Pakuła wrote:
> > [Why]
> > ALLM automatically puts TVs into low latency modes (gaming modes) which
> > we basically always want for PC use, be it gaming, or using precise
> > inputs like mice and keyboards.
>
> How about e.g. video playback though?
>
> It might make sense to let the Wayland compositor control this, e.g. via the Wayland content type hint protocol.
Yes, I think this should be a connector property. We'll happily
implement support for Weston as the uAPI vehicle.
Cheers,
Daniel
Powered by blists - more mailing lists