From: Luca Coelho <luca@coelho.fi>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Luca Coelho <luciano.coelho@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 08/13] drm/i915/dmc_wl: Allow simpler syntax for single reg in range tables
Date: Fri, 01 Nov 2024 14:58:33 +0200 [thread overview]
Message-ID: <39ca0bca034ed369700b2ecc1b1a411c824bd3b0.camel@coelho.fi> (raw)
In-Reply-To: <20241021222744.294371-9-gustavo.sousa@intel.com>
On Mon, 2024-10-21 at 19:27 -0300, Gustavo Sousa wrote:
> Allow simpler syntax for defining entries for single registers in range
> tables. That makes them easier to type as well as to read, allowing one
> to quickly tell whether a range actually refers to a single register or
> a "true range".
>
> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dmc_wl.c | 118 ++++++++++----------
> 1 file changed, 60 insertions(+), 58 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dmc_wl.c b/drivers/gpu/drm/i915/display/intel_dmc_wl.c
> index 8bf2f32be859..6992ce654e75 100644
> --- a/drivers/gpu/drm/i915/display/intel_dmc_wl.c
> +++ b/drivers/gpu/drm/i915/display/intel_dmc_wl.c
> @@ -54,82 +54,82 @@ static struct intel_dmc_wl_range lnl_wl_range[] = {
> };
>
> static struct intel_dmc_wl_range xe3lpd_dc5_dc6_wl_ranges[] = {
> - { .start = 0x45500, .end = 0x45500 }, /* DC_STATE_SEL */
> + { .start = 0x45500 }, /* DC_STATE_SEL */
> { .start = 0x457a0, .end = 0x457b0 }, /* DC*_RESIDENCY_COUNTER */
> - { .start = 0x45504, .end = 0x45504 }, /* DC_STATE_EN */
> + { .start = 0x45504 }, /* DC_STATE_EN */
> { .start = 0x45400, .end = 0x4540c }, /* PWR_WELL_CTL_* */
> - { .start = 0x454f0, .end = 0x454f0 }, /* RETENTION_CTRL */
> + { .start = 0x454f0 }, /* RETENTION_CTRL */
>
> /* DBUF_CTL_* */
> - { .start = 0x44300, .end = 0x44300 },
> - { .start = 0x44304, .end = 0x44304 },
> - { .start = 0x44f00, .end = 0x44f00 },
> - { .start = 0x44f04, .end = 0x44f04 },
> - { .start = 0x44fe8, .end = 0x44fe8 },
> - { .start = 0x45008, .end = 0x45008 },
> + { .start = 0x44300 },
> + { .start = 0x44304 },
> + { .start = 0x44f00 },
> + { .start = 0x44f04 },
> + { .start = 0x44fe8 },
> + { .start = 0x45008 },
>
> - { .start = 0x46070, .end = 0x46070 }, /* CDCLK_PLL_ENABLE */
> - { .start = 0x46000, .end = 0x46000 }, /* CDCLK_CTL */
> - { .start = 0x46008, .end = 0x46008 }, /* CDCLK_SQUASH_CTL */
> + { .start = 0x46070 }, /* CDCLK_PLL_ENABLE */
> + { .start = 0x46000 }, /* CDCLK_CTL */
> + { .start = 0x46008 }, /* CDCLK_SQUASH_CTL */
Many of these are probably actually ranges. I'm not a HW guy, but
these are probably blocks that need the wakelock and it just happens
that many of those addresses are actually not used, but would need a
wakelock if they were used?
IOW, e.g. all these DBUF_CTL registers are probably in the same range
that needs wakelocks (i.e. 0x44300-0x46fff)? Do we really need to
define many of these individually?
This is related to the previous patch as well, but I decided to comment
it here because it becomes clearer.
--
Cheers,
Luca.
next prev parent reply other threads:[~2024-11-01 12:58 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 22:27 [PATCH 00/13] drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD Gustavo Sousa
2024-10-21 22:27 ` [PATCH 01/13] drm/xe: Mimic i915 behavior for non-sleeping MMIO wait Gustavo Sousa
2024-11-01 10:57 ` Luca Coelho
2024-11-05 12:17 ` Gustavo Sousa
2024-10-21 22:27 ` [PATCH 02/13] drm/i915/dmc_wl: Use non-sleeping variant of " Gustavo Sousa
2024-10-22 9:34 ` Jani Nikula
2024-10-22 10:55 ` Gustavo Sousa
2024-11-01 11:04 ` Luca Coelho
2024-11-01 11:18 ` Luca Coelho
2024-10-21 22:27 ` [PATCH 03/13] drm/i915/dmc_wl: Check for non-zero refcount in release work Gustavo Sousa
2024-11-01 11:48 ` Luca Coelho
2024-10-21 22:27 ` [PATCH 04/13] drm/i915/dmc_wl: Get wakelock when disabling dynamic DC states Gustavo Sousa
2024-11-01 12:24 ` Luca Coelho
2024-11-05 12:44 ` Gustavo Sousa
2024-11-06 11:37 ` Luca Coelho
2024-10-21 22:27 ` [PATCH 05/13] drm/i915/dmc_wl: Use sentinel item for range tables Gustavo Sousa
2024-11-01 12:25 ` Luca Coelho
2024-10-21 22:27 ` [PATCH 06/13] drm/i915/dmc_wl: Extract intel_dmc_wl_addr_in_range() Gustavo Sousa
2024-10-21 22:27 ` [PATCH 07/13] drm/i915/dmc_wl: Check ranges specific to DC states Gustavo Sousa
2024-10-22 8:03 ` Jani Nikula
2024-10-22 11:06 ` Gustavo Sousa
2024-11-05 19:54 ` Gustavo Sousa
2024-10-22 8:03 ` Jani Nikula
2024-10-22 11:10 ` Gustavo Sousa
2024-10-22 11:14 ` Gustavo Sousa
2024-11-01 12:51 ` Luca Coelho
2024-11-05 13:00 ` Gustavo Sousa
2024-11-06 11:47 ` Luca Coelho
2024-11-06 13:56 ` Gustavo Sousa
2024-10-21 22:27 ` [PATCH 08/13] drm/i915/dmc_wl: Allow simpler syntax for single reg in range tables Gustavo Sousa
2024-11-01 12:58 ` Luca Coelho [this message]
2024-11-05 13:42 ` Gustavo Sousa
2024-11-06 12:23 ` Luca Coelho
2024-11-06 12:29 ` Gustavo Sousa
2024-11-06 12:35 ` Luca Coelho
2024-10-21 22:27 ` [PATCH 09/13] drm/i915/dmc_wl: Deal with existing references when disabling Gustavo Sousa
2024-11-01 14:17 ` Luca Coelho
2024-10-21 22:27 ` [PATCH 10/13] drm/i915/dmc_wl: Couple enable/disable with dynamic DC states Gustavo Sousa
2024-11-01 14:19 ` Luca Coelho
2024-10-21 22:27 ` [PATCH 11/13] drm/i915/dmc_wl: Add and use HAS_DMC_WAKELOCK() Gustavo Sousa
2024-10-22 9:37 ` Jani Nikula
2024-10-22 11:03 ` Gustavo Sousa
2024-11-05 13:56 ` Gustavo Sousa
2024-11-06 9:25 ` Jani Nikula
2024-11-06 13:24 ` Gustavo Sousa
2024-10-21 22:27 ` [PATCH 12/13] drm/i915/dmc_wl: Sanitize enable_dmc_wl according to hardware support Gustavo Sousa
2024-11-01 14:25 ` Luca Coelho
2024-10-21 22:27 ` [PATCH 13/13] drm/i915/xe3lpd: Use DMC wakelock by default Gustavo Sousa
2024-11-01 14:27 ` Luca Coelho
2024-11-05 13:46 ` Gustavo Sousa
2024-11-05 21:12 ` Gustavo Sousa
2024-11-06 12:27 ` Luca Coelho
2024-10-21 23:47 ` ✓ CI.Patch_applied: success for drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD Patchwork
2024-10-21 23:48 ` ✗ CI.checkpatch: warning " Patchwork
2024-10-21 23:49 ` ✓ CI.KUnit: success " Patchwork
2024-10-22 0:01 ` ✓ CI.Build: " Patchwork
2024-10-22 0:03 ` ✓ CI.Hooks: " Patchwork
2024-10-22 0:04 ` ✗ CI.checksparse: warning " Patchwork
2024-10-22 0:29 ` ✓ CI.BAT: success " Patchwork
2024-10-22 8:23 ` ✗ CI.FULL: failure " 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=39ca0bca034ed369700b2ecc1b1a411c824bd3b0.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=luciano.coelho@intel.com \
--cc=rodrigo.vivi@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