public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Eric Anholt <eric@anholt.net>
Cc: Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	David Airlie <airlied@linux.ie>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Eben Upton <eben@raspberrypi.org>
Subject: Re: [PATCH] drm/vc4: Allow fb modifiers early enough to fill IN_FORMATS property
Date: Fri, 28 Dec 2018 13:08:48 +0100	[thread overview]
Message-ID: <20181228120848.GS9058@dvetter-linux.ger.corp.intel.com> (raw)
In-Reply-To: <878t0amtjf.fsf@anholt.net>

On Thu, Dec 27, 2018 at 03:36:20PM -0800, Eric Anholt wrote:
> Paul Kocialkowski <paul.kocialkowski@bootlin.com> writes:
> 
> > The KMS mode_config elements are currently configured in vc4_kms_load,
> > that is called after all components are binded (component_bind_all).
> > However, the CRTC component (for the Pixel Valve) needs to access the
> > allow_fb_modifiers element at bind time, when initializing its planes
> > through drm_universal_plane_init.
> >
> > This helpers checks allow_fb_modifiers to decide whether to fill the
> > IN_FORMATS property. Because allow_fb_modifiers is still set to false
> > at this point, the property is never filled and userspace cannot
> > retrieve the combination of supported formats and modifiers.
> >
> > Fix this by setting allow_fb_modifiers right after calling
> > drm_mode_config_init (which initializes the structure), before binding
> > the components of the driver.
> 
> This makes me wonder if the flag could be removed and replaced with "did
> non-NULL modifiers get supplied to plane init?"  I think I've tripped
> over this flag in other KMS hacking, too.

Sounds like a good idea to me. Just setting it in plane_init should work I
think ...
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2018-12-28 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-24 12:25 [PATCH] drm/vc4: Allow fb modifiers early enough to fill IN_FORMATS property Paul Kocialkowski
2018-12-27 23:36 ` Eric Anholt
2018-12-28 12:08   ` Daniel Vetter [this message]
2018-12-28 15:09     ` Paul Kocialkowski

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=20181228120848.GS9058@dvetter-linux.ger.corp.intel.com \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=eben@raspberrypi.org \
    --cc=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@bootlin.com \
    --cc=paul.kocialkowski@bootlin.com \
    --cc=thomas.petazzoni@bootlin.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