From: Jani Nikula <jani.nikula@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/dmc_wl: store register ranges in rodata
Date: Fri, 20 Dec 2024 10:57:59 +0200 [thread overview]
Message-ID: <87ikrepw88.fsf@intel.com> (raw)
In-Reply-To: <173453211835.3475.8229112069297893910@intel.com>
On Wed, 18 Dec 2024, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> Quoting Jani Nikula (2024-12-18 11:17:34-03:00)
>>Add const to register range arrays to store them in rodata. They don't
>>need to be modified.
>>
>>Cc: Gustavo Sousa <gustavo.sousa@intel.com>
>>Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Good idea.
>
> Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
Thanks for the review, pushed to drm-intel-next.
BR,
Jani.
>
>>---
>> drivers/gpu/drm/i915/display/intel_dmc_wl.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>>diff --git a/drivers/gpu/drm/i915/display/intel_dmc_wl.c b/drivers/gpu/drm/i915/display/intel_dmc_wl.c
>>index 3ac44151aab5..02de3ae15074 100644
>>--- a/drivers/gpu/drm/i915/display/intel_dmc_wl.c
>>+++ b/drivers/gpu/drm/i915/display/intel_dmc_wl.c
>>@@ -55,12 +55,12 @@ struct intel_dmc_wl_range {
>> u32 end;
>> };
>>
>>-static struct intel_dmc_wl_range powered_off_ranges[] = {
>>+static const struct intel_dmc_wl_range powered_off_ranges[] = {
>> { .start = 0x60000, .end = 0x7ffff },
>> {},
>> };
>>
>>-static struct intel_dmc_wl_range xe3lpd_dc5_dc6_dmc_ranges[] = {
>>+static const struct intel_dmc_wl_range xe3lpd_dc5_dc6_dmc_ranges[] = {
>> { .start = 0x45500 }, /* DC_STATE_SEL */
>> { .start = 0x457a0, .end = 0x457b0 }, /* DC*_RESIDENCY_COUNTER */
>> { .start = 0x45504 }, /* DC_STATE_EN */
>>@@ -94,7 +94,7 @@ static struct intel_dmc_wl_range xe3lpd_dc5_dc6_dmc_ranges[] = {
>> {},
>> };
>>
>>-static struct intel_dmc_wl_range xe3lpd_dc3co_dmc_ranges[] = {
>>+static const struct intel_dmc_wl_range xe3lpd_dc3co_dmc_ranges[] = {
>> { .start = 0x454a0 }, /* CHICKEN_DCPR_4 */
>>
>> { .start = 0x45504 }, /* DC_STATE_EN */
>>--
>>2.39.5
>>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-12-20 8:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 14:17 [PATCH] drm/i915/dmc_wl: store register ranges in rodata Jani Nikula
2024-12-18 14:28 ` Gustavo Sousa
2024-12-20 8:57 ` Jani Nikula [this message]
2024-12-18 18:48 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-18 18:48 ` ✓ CI.checkpatch: " Patchwork
2024-12-18 18:49 ` ✓ CI.KUnit: " Patchwork
2024-12-18 19:08 ` ✓ CI.Build: " Patchwork
2024-12-18 19:10 ` ✓ CI.Hooks: " Patchwork
2024-12-18 19:12 ` ✓ CI.checksparse: " Patchwork
2024-12-18 19:51 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-19 9:38 ` ✗ Xe.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=87ikrepw88.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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