From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Suraj Kandpal <suraj.kandpal@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/7] Enable YCbCr420 format for VDSC
Date: Wed, 08 Mar 2023 14:47:08 +0200 [thread overview]
Message-ID: <87r0tzbeb7.fsf@intel.com> (raw)
In-Reply-To: <6bd9b493-01da-0542-2a21-10602dba6a1a@linaro.org>
On Wed, 08 Mar 2023, Dmitry Baryshkov <dmitry.baryshkov@linaro.org> wrote:
> On 08/03/2023 13:30, Jani Nikula wrote:
>> On Wed, 22 Feb 2023, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
>>> This patch series aims to enable the YCbCr420 format
>>> for DSC. Changes are mostly compute params related for
>>> hdmi,dp and dsi along with the addition of new rc_tables
>>> for native_420 and corresponding changes to macros used to
>>> fetch them.
>>> There have been discussions prior to this series in which some patches
>>> have gotten rb and can be found in the below link
>>> https://patchwork.freedesktop.org/series/113729
>>
>> I think it would be useful to get [1] from Dmitry merged to
>> drm-misc-next first, have that in drm-next, and again backmerged to
>> drm-intel-next before this. At least patches 1-5.
>>
>> There's not much point in all drivers duplicating the parameters, and we
>> need to move towards common code. Dmitry has been helpful in
>> contributing this to us.
>
> Note, while I slightly reworked the calculate_rc_params() function, I
> did not touch the intel_qp_tables (mostly since we do not need them for
> drm/msm (at least for now). Our current plan is to use fixed params (at
> least in the short notice). We might have to reconsider it at some point.
Yeah, this isn't a big conflict, but AFAICT it'll conflict in
intel_vdsc.c.
> However it might be wise to merge them with amdgpu's qp tables. amdgpu
> driver also contains code to calculate RC params. It might be worth
> moving RC calculation to the common helper.
Agreed.
BR,
Jani.
>
>>
>> BR,
>> Jani.
>>
>>
>> [1] https://patchwork.freedesktop.org/series/114473/
>>
>>>
>>> Ankit Nautiyal (2):
>>> drm/dp_helper: Add helper to check DSC support with given o/p format
>>> drm/i915/dp: Check if DSC supports the given output_format
>>>
>>> Suraj Kandpal (4):
>>> drm/i915: Adding the new registers for DSC
>>> drm/i915: Enable YCbCr420 for VDSC
>>> drm/i915/display: Fill in native_420 field
>>> drm/i915/vdsc: Check slice design requirement
>>>
>>> Swati Sharma (1):
>>> drm/i915/dsc: Add debugfs entry to validate DSC output formats
>>>
>>> drivers/gpu/drm/i915/display/icl_dsi.c | 2 -
>>> .../drm/i915/display/intel_crtc_state_dump.c | 4 +-
>>> .../drm/i915/display/intel_crtc_state_dump.h | 2 +
>>> .../drm/i915/display/intel_display_debugfs.c | 78 ++++++++
>>> .../drm/i915/display/intel_display_types.h | 1 +
>>> drivers/gpu/drm/i915/display/intel_dp.c | 39 +++-
>>> .../gpu/drm/i915/display/intel_qp_tables.c | 187 ++++++++++++++++--
>>> .../gpu/drm/i915/display/intel_qp_tables.h | 4 +-
>>> drivers/gpu/drm/i915/display/intel_vdsc.c | 108 +++++++++-
>>> drivers/gpu/drm/i915/i915_reg.h | 28 +++
>>> include/drm/display/drm_dp_helper.h | 13 ++
>>> 11 files changed, 442 insertions(+), 24 deletions(-)
>>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-08 12:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 5:31 [Intel-gfx] [PATCH 0/7] Enable YCbCr420 format for VDSC Suraj Kandpal
2023-02-22 5:31 ` [Intel-gfx] [PATCH 1/7] drm/dp_helper: Add helper to check DSC support with given o/p format Suraj Kandpal
2023-03-08 10:50 ` Shankar, Uma
2023-02-22 5:31 ` [Intel-gfx] [PATCH 2/7] drm/i915/dp: Check if DSC supports the given output_format Suraj Kandpal
2023-03-08 10:55 ` Shankar, Uma
2023-02-22 5:31 ` [Intel-gfx] [PATCH 3/7] drm/i915: Adding the new registers for DSC Suraj Kandpal
2023-03-08 10:58 ` Shankar, Uma
2023-03-08 11:26 ` Jani Nikula
2023-03-08 11:31 ` Shankar, Uma
2023-02-22 5:31 ` [Intel-gfx] [PATCH 4/7] drm/i915: Enable YCbCr420 for VDSC Suraj Kandpal
2023-03-08 10:59 ` Shankar, Uma
2023-02-22 5:31 ` [Intel-gfx] [PATCH 5/7] drm/i915/display: Fill in native_420 field Suraj Kandpal
2023-03-03 5:34 ` [Intel-gfx] [PATCH v2 " Suraj Kandpal
2023-03-08 11:21 ` Shankar, Uma
2023-02-22 5:31 ` [Intel-gfx] [PATCH 6/7] drm/i915/vdsc: Check slice design requirement Suraj Kandpal
2023-03-08 11:23 ` Shankar, Uma
2023-02-22 5:31 ` [Intel-gfx] [PATCH 7/7] drm/i915/dsc: Add debugfs entry to validate DSC output formats Suraj Kandpal
2023-02-22 6:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Enable YCbCr420 format for VDSC Patchwork
2023-02-22 6:31 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-03-03 10:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Enable YCbCr420 format for VDSC (rev2) Patchwork
2023-03-06 17:57 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-03-08 11:30 ` [Intel-gfx] [PATCH 0/7] Enable YCbCr420 format for VDSC Jani Nikula
2023-03-08 12:32 ` Dmitry Baryshkov
2023-03-08 12:47 ` Jani Nikula [this message]
2023-03-28 13:20 ` Kandpal, Suraj
2023-03-28 13:27 ` Dmitry Baryshkov
2023-04-03 6:08 ` Shankar, Uma
2023-04-03 7:15 ` Shankar, Uma
2023-04-07 2:57 ` Dmitry Baryshkov
2023-04-07 3:11 ` Kandpal, Suraj
2023-04-13 14:33 ` Dmitry Baryshkov
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=87r0tzbeb7.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=suraj.kandpal@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