From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
intel-xe@lists.freedesktop.org
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 1/3] drm/xe: Read out rawclk_freq for display
Date: Tue, 20 Aug 2024 12:12:36 +0300 [thread overview]
Message-ID: <87bk1n5zi3.fsf@intel.com> (raw)
In-Reply-To: <87msl763mb.fsf@intel.com>
On Tue, 20 Aug 2024, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Mon, 19 Aug 2024, Maarten Lankhorst <maarten.lankhorst@linux.intel.com> wrote:
>> Failing to read out rawclk makes it impossible to read out backlight,
>> which results in backlight not working when the backlight is off during
>> boot, or when reloading the module.
>>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> Fixes: 44e694958b95 ("drm/xe/display: Implement display support")
>> Cc: <stable@vger.kernel.org> # v6.8+
>
> Please find another way. See [1]. I'm trying to clean up the whole
> RUNTIME_INFO() and rawclk_freq thing, and this makes it harder.
Had another look, and brushed up my old patches, new version at [1].
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1724144570.git.jani.nikula@intel.com
>
> BR,
> Jani.
>
>
> [1] https://lore.kernel.org/r/ddd05f84ca4a6597133bee55ddf4ab593a16e99d.1717672515.git.jani.nikula@intel.com
>
>> ---
>> drivers/gpu/drm/xe/display/xe_display.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/display/xe_display.c b/drivers/gpu/drm/xe/display/xe_display.c
>> index 30dfdac9f6fa9..79add15c6c4c7 100644
>> --- a/drivers/gpu/drm/xe/display/xe_display.c
>> +++ b/drivers/gpu/drm/xe/display/xe_display.c
>> @@ -159,6 +159,9 @@ int xe_display_init_noirq(struct xe_device *xe)
>>
>> intel_display_device_info_runtime_init(xe);
>>
>> + RUNTIME_INFO(xe)->rawclk_freq = intel_read_rawclk(xe);
>> + drm_dbg(&xe->drm, "rawclk rate: %d kHz\n", RUNTIME_INFO(xe)->rawclk_freq);
>> +
>> err = intel_display_driver_probe_noirq(xe);
>> if (err) {
>> intel_opregion_cleanup(display);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-08-20 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 13:31 [PATCH v2 0/3] drm/xe/display: Fixes to make kexec work Maarten Lankhorst
2024-08-19 13:31 ` [PATCH v2 1/3] drm/xe: Read out rawclk_freq for display Maarten Lankhorst
2024-08-20 7:43 ` Jani Nikula
2024-08-20 9:12 ` Jani Nikula [this message]
2024-08-19 13:31 ` [PATCH v2 2/3] drm/xe: Wire up device shutdown handler Maarten Lankhorst
2024-08-19 13:38 ` Lucas De Marchi
2024-08-19 13:31 ` [PATCH v2 3/3] CI-only: Test if FLR is disabled? Maarten Lankhorst
2024-08-19 13:37 ` ✓ CI.Patch_applied: success for drm/xe/display: Fixes to make kexec work. (rev2) Patchwork
2024-08-19 13:37 ` ✗ CI.checkpatch: warning " Patchwork
2024-08-19 13:37 ` ✗ CI.KUnit: 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=87bk1n5zi3.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.