Re: [PATCH] drm/doc: Define KMS atomic state set

From: Pekka Paalanen
Date: Tue Dec 05 2023 - 03:36:20 EST


On Mon, 4 Dec 2023 10:21:03 +0100
Maxime Ripard <mripard@xxxxxxxxxx> wrote:

> Hi
>
> On Fri, Dec 01, 2023 at 06:03:48PM +0200, Pekka Paalanen wrote:
> > On Fri, 1 Dec 2023 14:20:55 +0100
> > Maxime Ripard <mripard@xxxxxxxxxx> wrote:
> >
> > > On Fri, Dec 01, 2023 at 12:06:48PM +0200, Pekka Paalanen wrote:

...

> > Is it really "global" too? Or is it device-wide? Or is it just the bits
> > that userspace bothered to mention in an atomic commit?
>
> As far as I'm concerned, global == "device-wide", so I'm not entirely
> sure what is the distinction you want to raise here, so I might be off.
>
> But to answer the latter part of your question, drm_atomic_state
> contains the changes of all the objects affected by the commit userspace
> mentioned to bother. Which is is why I found the "global" to be
> confusing, because it's not a device-wide-global state, it's a
> commit-global state.

I think the word "global" should be simply avoided. Nothing here is
truly global (machine wide? kernel instance wide? worldwide like
UUID?), and its meaning varies by speaker and context.


Thanks,
pq

Attachment: pgp4svvIcAhlw.pgp
Description: OpenPGP digital signature