From: Eric Anholt <eric@anholt.net>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Promote .format_mod_supported() to the lead role
Date: Mon, 21 May 2018 12:21:01 -0700 [thread overview]
Message-ID: <877enwu86a.fsf@anholt.net> (raw)
In-Reply-To: <20180518162159.30305-1-ville.syrjala@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 913 bytes --]
Ville Syrjala <ville.syrjala@linux.intel.com> writes:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Up to now we've used the plane's modifier list as the primary
> source of information for which modifiers are supported by a
> given plane. In order to allow auxiliary metadata to be embedded
> within the bits of the modifier we need to stop doing that.
>
> Thus we have to make .format_mod_supported() aware of the plane's
> capabilities and gracefully deal with any modifier being passed
> in directly from userspace.
This seems like it would be a lot shorter if you just had a helper to
check if your format and modifier was in drm_plane->format_types and
drm_plane->modifiers, since then you wouldn't be duplicating your tables
and you wouldn't need has_ccs either.
However, it's not my driver and it unblocks vc4's patch, so:
Reviewed-by: Eric Anholt <eric@anholt.net>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-05-21 19:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 16:50 [PATCH] drm/i915: Promote .format_mod_supported() to the lead role Ville Syrjala
2018-03-19 18:16 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-03-19 18:31 ` ✓ Fi.CI.BAT: success " Patchwork
2018-03-19 21:17 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-03-19 21:23 ` Ville Syrjälä
2018-03-30 19:06 ` [PATCH] " Eric Anholt
2018-04-27 16:33 ` Ville Syrjälä
2018-05-18 16:21 ` [PATCH v2] " Ville Syrjala
2018-05-21 19:21 ` Eric Anholt [this message]
2018-05-22 16:36 ` Ville Syrjälä
2018-05-30 18:30 ` Eric Anholt
2018-05-30 20:10 ` Ville Syrjälä
2018-05-18 16:33 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Promote .format_mod_supported() to the lead role (rev2) Patchwork
2018-05-18 16:48 ` ✓ Fi.CI.BAT: success " Patchwork
2018-05-19 0:49 ` ✓ Fi.CI.IGT: " Patchwork
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=877enwu86a.fsf@anholt.net \
--to=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.