From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Shankar, Uma" <uma.shankar@intel.com>,
"Kandpal, Suraj" <suraj.kandpal@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 3/7] drm/i915: Adding the new registers for DSC
Date: Wed, 08 Mar 2023 13:26:58 +0200 [thread overview]
Message-ID: <87wn3rbi0t.fsf@intel.com> (raw)
In-Reply-To: <DM4PR11MB63608B360592329EF088351DF4B49@DM4PR11MB6360.namprd11.prod.outlook.com>
On Wed, 08 Mar 2023, "Shankar, Uma" <uma.shankar@intel.com> wrote:
>> -----Original Message-----
>> From: Kandpal, Suraj <suraj.kandpal@intel.com>
>> Sent: Wednesday, February 22, 2023 11:02 AM
>> To: dri-devel@lists.freedesktop.org; intel-gfx@lists.freedesktop.org
>> Cc: Shankar, Uma <uma.shankar@intel.com>; Nautiyal, Ankit K
>> <ankit.k.nautiyal@intel.com>; Kandpal, Suraj <suraj.kandpal@intel.com>; Kulkarni,
>> Vandita <vandita.kulkarni@intel.com>
>> Subject: [PATCH 3/7] drm/i915: Adding the new registers for DSC
>
> Nit: drm/i915/dsc would be better.
>
> Looks Good to me.
> Reviewed-by: Uma Shankar <uma.shankar@intel.com>
Except since c3f059483671 ("drm/i915/display: split out DSC and DSS
registers") the DSC registers need to go to display/intel_vdsc_regs.h.
BR,
Jani.
>
>> Adding new DSC register which are introducted MTL onwards
>>
>> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>> Reviewed-by: Vandita Kulkarni <Vandita.kulkarni@intel.com>
>> ---
>> drivers/gpu/drm/i915/i915_reg.h | 28 ++++++++++++++++++++++++++++
>> 1 file changed, 28 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
>> index 596efc940ee7..9e25e21d37e4 100644
>> --- a/drivers/gpu/drm/i915/i915_reg.h
>> +++ b/drivers/gpu/drm/i915/i915_reg.h
>> @@ -7715,6 +7715,8 @@ enum skl_power_gate {
>> #define ICL_DSC1_PICTURE_PARAMETER_SET_0(pipe) _MMIO_PIPE((pipe) -
>> PIPE_B, \
>>
>> _ICL_DSC1_PICTURE_PARAMETER_SET_0_PB, \
>>
>> _ICL_DSC1_PICTURE_PARAMETER_SET_0_PC)
>> +#define DSC_NATIVE_422_ENABLE BIT(23)
>> +#define DSC_NATIVE_420_ENABLE BIT(22)
>> #define DSC_ALT_ICH_SEL (1 << 20)
>> #define DSC_VBR_ENABLE (1 << 19)
>> #define DSC_422_ENABLE (1 << 18)
>> @@ -7959,6 +7961,32 @@ enum skl_power_gate {
>> #define DSC_SLICE_PER_LINE(slice_per_line) ((slice_per_line) << 16)
>> #define DSC_SLICE_CHUNK_SIZE(slice_chunk_size) ((slice_chunk_size)
>> << 0)
>>
>> +/* MTL Display Stream Compression registers */
>> +#define _MTL_DSC0_PICTURE_PARAMETER_SET_17_PB 0x782B4
>> +#define _MTL_DSC1_PICTURE_PARAMETER_SET_17_PB 0x783B4
>> +#define _MTL_DSC0_PICTURE_PARAMETER_SET_17_PC 0x784B4
>> +#define _MTL_DSC1_PICTURE_PARAMETER_SET_17_PC 0x785B4
>> +#define MTL_DSC0_PICTURE_PARAMETER_SET_17(pipe)
>> _MMIO_PIPE((pipe) - PIPE_B, \
>> +
>> _MTL_DSC0_PICTURE_PARAMETER_SET_17_PB, \
>> +
>> _MTL_DSC0_PICTURE_PARAMETER_SET_17_PC)
>> +#define MTL_DSC1_PICTURE_PARAMETER_SET_17(pipe)
>> _MMIO_PIPE((pipe) - PIPE_B, \
>> +
>> _MTL_DSC1_PICTURE_PARAMETER_SET_17_PB, \
>> +
>> _MTL_DSC1_PICTURE_PARAMETER_SET_17_PC)
>> +#define DSC_SL_BPG_OFFSET(offset) ((offset) << 27)
>> +
>> +#define _MTL_DSC0_PICTURE_PARAMETER_SET_18_PB 0x782B8
>> +#define _MTL_DSC1_PICTURE_PARAMETER_SET_18_PB 0x783B8
>> +#define _MTL_DSC0_PICTURE_PARAMETER_SET_18_PC 0x784B8
>> +#define _MTL_DSC1_PICTURE_PARAMETER_SET_18_PC 0x785B8
>> +#define MTL_DSC0_PICTURE_PARAMETER_SET_18(pipe)
>> _MMIO_PIPE((pipe) - PIPE_B, \
>> +
>> _MTL_DSC0_PICTURE_PARAMETER_SET_18_PB, \
>> +
>> _MTL_DSC0_PICTURE_PARAMETER_SET_18_PC)
>> +#define MTL_DSC1_PICTURE_PARAMETER_SET_18(pipe)
>> _MMIO_PIPE((pipe) - PIPE_B, \
>> +
>> _MTL_DSC1_PICTURE_PARAMETER_SET_18_PB, \
>> +
>> _MTL_DSC1_PICTURE_PARAMETER_SET_18_PC)
>> +#define DSC_NSL_BPG_OFFSET(offset) ((offset) << 16)
>> +#define DSC_SL_OFFSET_ADJ(offset) ((offset) << 0)
>> +
>> /* Icelake Rate Control Buffer Threshold Registers */
>> #define DSCA_RC_BUF_THRESH_0 _MMIO(0x6B230)
>> #define DSCA_RC_BUF_THRESH_0_UDW _MMIO(0x6B230 + 4)
>> --
>> 2.25.1
>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-08 11:27 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 [this message]
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
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=87wn3rbi0t.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=suraj.kandpal@intel.com \
--cc=uma.shankar@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