mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Austin Hu <austin.hu@intel.com>
To: ville.syrjala@linux.intel.com
Cc: austin.hu@intel.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, robin.clark@oss.qualcomm.com
Subject: Re: [PATCH] drm/atomic: clear the state of plane which is unused.
Date: Tue, 17 Mar 2026 13:07:46 -0700	[thread overview]
Message-ID: <20260317200746.501646-1-austin.hu@intel.com> (raw)
In-Reply-To: <abj79EU0bMEkcSD3@intel.com>

Hi Ville,

Thanks for your comments!

> The kernel isn't allowed to magically change the value of
> properties set by userspace, apart from a few special cases.
>
> No idea what you're actually trying to fix here, but sounds
> like your userspace might be broken and needs to be fixed.

I agree that userspace should reset unused plane properties.
Otherwise, the drm_plane_state UAPI "sticky" values may not
match what is actually programmed to hardware, which can be
confusing.

For example, i915_display_info debugfs shows:

    [PLANE:123:plane 4A]: type=OVL
        uapi: [FB:0] n/a,0x0,0x0,, visible=Y plane,
              src=125.000000x48.000000+0.000000+0.000000,
              dst=125x48+897+0, rotation=0 (0x00000001)
        planar: Linked to [PLANE:33:plane 1A] as a Y plane
        hw: [FB:567] NV12 little-endian (0x3231564e),
            0x100000000000010,2048x1088, visible=no,
            src=1920.000000x1080.000000+0.000000+0.000000,
            dst=1920x1080+0+0, rotation=0 (0x00000001)

That said, I was wondering if DRM could also reset unused
plane state defensively, in case userspace does not do so.
For example:

https://gitlab.freedesktop.org/drm-hwcomposer/drm-hwcomposer/-/blob/main/drm/DrmPlane.cpp#L464

Maybe this is not the right way, but my intention was to avoid
such mismatches.

Thanks,
Austin

      reply	other threads:[~2026-03-17 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 22:55 Austin Hu
2026-03-17  7:00 ` Ville Syrjälä
2026-03-17 20:07   ` Austin Hu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260317200746.501646-1-austin.hu@intel.com \
    --to=austin.hu@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.clark@oss.qualcomm.com \
    --cc=ville.syrjala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®