From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: ville.syrjala@intel.com, intel-gfx@lists.freedesktop.org,
martin.peres@intel.com, dri-devel@lists.freedesktop.org,
juha-pekka.heikkila@intel.com
Subject: Re: [PATCH v10 2/2] drm/i915: Adding YUV444 packed format support for skl+
Date: Thu, 25 Oct 2018 08:21:55 +0200 [thread overview]
Message-ID: <4710f260-6ba4-e97d-cf6b-2690bc6194a4@linux.intel.com> (raw)
In-Reply-To: <20181024171712.GA4105@mdroper-desk.amr.corp.intel.com>
Op 24-10-18 om 19:17 schreef Matt Roper:
> On Tue, Oct 23, 2018 at 01:39:10PM +0200, Maarten Lankhorst wrote:
>>
>> Op 02-10-18 om 13:15 schreef Stanislav Lisovskiy:
>>> PLANE_CTL_FORMAT_AYUV is already supported, according to hardware
>>> specification.
>>>
>>> v2: Edited commit message, removed redundant whitespaces.
>>>
>>> v3: Fixed fallthrough logic for the format switch cases.
>>>
>>> v4: Yet again fixed fallthrough logic, to reuse code from other case
>>> labels.
>>>
>>> v5: Started to use XYUV instead of AYUV, as we don't use alpha.
>>>
>>> v6: Removed unneeded initializer for new XYUV format.
>>>
>>> v7: Added scaling support for DRM_FORMAT_XYUV
>>>
>>> v8: Edited commit message to be more clear about skl+, renamed
>>> PLANE_CTL_FORMAT_AYUV to PLANE_CTL_FORMAT_XYUV as this format
>>> doesn't support per-pixel alpha. Fixed minor code issues.
>>>
>>> v9: Moved DRM format check to proper place in intel_framebuffer_init.
>>>
>>> v10: Added missing XYUV format to sprite planes for skl+.
>>>
>>> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
>>> ---
>>> drivers/gpu/drm/i915/i915_reg.h | 2 +-
>>> drivers/gpu/drm/i915/intel_display.c | 15 +++++++++++++++
>>> drivers/gpu/drm/i915/intel_sprite.c | 3 +++
>>> 3 files changed, 19 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
>>> index 09bc8e730ee1..ac24ac4b1d51 100644
>>> --- a/drivers/gpu/drm/i915/i915_reg.h
>>> +++ b/drivers/gpu/drm/i915/i915_reg.h
>>> @@ -6501,7 +6501,7 @@ enum {
>>> #define PLANE_CTL_FORMAT_XRGB_2101010 (2 << 24)
>>> #define PLANE_CTL_FORMAT_XRGB_8888 (4 << 24)
>>> #define PLANE_CTL_FORMAT_XRGB_16161616F (6 << 24)
>>> -#define PLANE_CTL_FORMAT_AYUV (8 << 24)
>>> +#define PLANE_CTL_FORMAT_XYUV (8 << 24)
>> It's the same format as AYUV, don't add a separate definition here for it.
>> The only difference is we ignore the alpha channel.
> I think he's just renaming the format that's already been added to be
> more consistent with how we name our other PLANE_CTL_FORMAT_
> definitions. I.e., all the rgb types use "XRGB" in the name.
>
Ah k, with your explanation it makes more sense then. :)
Yeah just zap the AYUV if there's no alpha channel.
~Maarten
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-25 6:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 11:15 [PATCH v10 0/2] Add XYUV format support Stanislav Lisovskiy
2018-10-02 11:15 ` [PATCH v10 1/2] drm: Introduce new DRM_FORMAT_XYUV Stanislav Lisovskiy
2018-10-02 15:28 ` Alexandru-Cosmin Gheorghe
2018-10-03 6:39 ` Lisovskiy, Stanislav
2018-10-03 8:07 ` Alexandru-Cosmin Gheorghe
2018-10-04 12:04 ` Lisovskiy, Stanislav
2018-10-04 12:25 ` Alexandru-Cosmin Gheorghe
2018-10-02 11:15 ` [PATCH v10 2/2] drm/i915: Adding YUV444 packed format support for skl+ Stanislav Lisovskiy
2018-10-23 11:39 ` Maarten Lankhorst
2018-10-23 11:55 ` Lisovskiy, Stanislav
2018-10-24 17:17 ` Matt Roper
2018-10-25 6:21 ` Maarten Lankhorst [this message]
2018-10-02 11:42 ` ✗ Fi.CI.CHECKPATCH: warning for Add XYUV format support (rev7) Patchwork
2018-10-02 12:01 ` ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-09-07 8:45 [PATCH v10 0/2] Add XYUV format support Stanislav Lisovskiy
2018-09-07 8:45 ` [PATCH v10 2/2] drm/i915: Adding YUV444 packed format support for skl+ Stanislav Lisovskiy
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=4710f260-6ba4-e97d-cf6b-2690bc6194a4@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=juha-pekka.heikkila@intel.com \
--cc=martin.peres@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=ville.syrjala@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