dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Brian Starkey <brian.starkey@arm.com>
Cc: nd@arm.com, airlied@linux.ie, alexandru-cosmin.gheorghe@arm.com,
	liviu.dudau@arm.com, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	Ayan Kumar Halder <ayan.halder@arm.com>
Subject: Re: [PATCH] drm: check_pixel_format() should return true if no modifiers are passed for a supported pixel format
Date: Fri, 25 May 2018 19:08:05 +0300	[thread overview]
Message-ID: <20180525160805.GG23723@intel.com> (raw)
In-Reply-To: <20180525154859.GB1139@e107564-lin.cambridge.arm.com>

On Fri, May 25, 2018 at 04:48:59PM +0100, Brian Starkey wrote:
> Hi Ayan,
> 
> On Fri, May 25, 2018 at 04:35:41PM +0100, Ayan Kumar Halder wrote:
> >If a plane supports a pixel format and the framebuffer does not pass any
> >modifiers, then drm_plane_check_pixel_format() should always return true
> >for the given format regardless of whether the plane supports any
> >modifiers or not.
> >
> >Signed-off-by: Ayan Kumar Halder <ayan.halder@arm.com>
> >---
> > drivers/gpu/drm/drm_plane.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> >diff --git a/drivers/gpu/drm/drm_plane.c b/drivers/gpu/drm/drm_plane.c
> >index 6d2a6e4..873c084 100644
> >--- a/drivers/gpu/drm/drm_plane.c
> >+++ b/drivers/gpu/drm/drm_plane.c
> >@@ -564,6 +564,9 @@ int drm_plane_check_pixel_format(struct drm_plane *plane,
> > 	if (!plane->modifier_count)
> > 		return 0;
> >
> >+	if (modifier == DRM_FORMAT_MOD_NONE)
> >+		return 0;
> >+
> 
> There can be drivers which have formats which are only supported when
> a modifier is used - so I don't think this check is right to have in
> the core.
> 
> Drivers need to check if they support the format with no modifier
> (same as DRM_FORMAT_MOD_LINEAR) in their format_mod_supported()
> callback.

BTW I tried to make the core hide the "did the request have modifiers
or not" difference as much as possible, and to validate that there is
at least one plane that can use the created fb:
https://patchwork.freedesktop.org/series/39814/

Not sure we ever figured out a good solution in the end, but at least
Eric's approach in https://patchwork.freedesktop.org/series/40133/
would avoid some of the problems I was having in my attempts. I guess 
I should try to revisit that patchset and see if I can make it less
objectionable this time around.

> 
> Thanks,
> -Brian
> 
> > 	for (i = 0; i < plane->modifier_count; i++) {
> > 		if (modifier == plane->modifiers[i])
> > 			break;
> >-- 
> >2.7.4
> >
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-05-25 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 15:35 [PATCH] drm: check_pixel_format() should return true if no modifiers are passed for a supported pixel format Ayan Kumar Halder
2018-05-25 15:48 ` Brian Starkey
2018-05-25 16:08   ` Ville Syrjälä [this message]
2018-05-25 15:54 ` Ville Syrjälä

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=20180525160805.GG23723@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=alexandru-cosmin.gheorghe@arm.com \
    --cc=ayan.halder@arm.com \
    --cc=brian.starkey@arm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liviu.dudau@arm.com \
    --cc=nd@arm.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;
as well as URLs for NNTP newsgroup(s).