From: Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Cc: <arun.r.murthy@intel.com>
Subject: Re: [PATCH] drm/i915/fbdev: Hold runtime PM ref during fbdev BO creation
Date: Mon, 10 Nov 2025 20:56:37 +0530 [thread overview]
Message-ID: <602bb5d3-fe1f-47c3-8775-3078d0fc7bc3@intel.com> (raw)
In-Reply-To: <c08839f894cefc8f5fa801d4254934b8c4dfbdcb@intel.com>
On 06-11-2025 19:00, Jani Nikula wrote:
> On Thu, 06 Nov 2025, Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com> wrote:
>> During fbdev probe, the driver allocates and pins a framebuffer
>> BO (via xe_bo_create_pin_map_novm() → xe_ggtt_insert_bo()).
> Might emphasize this is with the xe driver, since the subject prefix
> says i915.
I will mention xe .
>> Without a runtime PM reference, xe_pm_runtime_get_noresume() warns about
>> missing outer PM protection as below:
>>
>> xe 0000:03:00.0: [drm] Missing outer runtime PM protection
>>
>> Acquire a runtime PM reference before framebuffer allocation to ensure
>> xe_ggtt_insert_bo() executes under active runtime PM context.
>>
>> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/6350
>>
> Superfluous newline.
>
> Fixes: ?
As this originates from intel_fbdev_fb_alloc()
which was introduced by commit 44e694958b95395bd1c41508c88c8ca141bf9bd7,
Can I add same commit for Fixes:
Regards,
Dibin
>
> BR,
> Jani.
>
>> Signed-off-by: Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_fbdev.c | 11 +++++++----
>> 1 file changed, 7 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_fbdev.c b/drivers/gpu/drm/i915/display/intel_fbdev.c
>> index e5449c41cfa1..7173bd1cbffd 100644
>> --- a/drivers/gpu/drm/i915/display/intel_fbdev.c
>> +++ b/drivers/gpu/drm/i915/display/intel_fbdev.c
>> @@ -288,13 +288,18 @@ int intel_fbdev_driver_fbdev_probe(struct drm_fb_helper *helper,
>> drm_framebuffer_put(&fb->base);
>> fb = NULL;
>> }
>> +
>> + wakeref = intel_display_rpm_get(display);
>> +
>> if (!fb || drm_WARN_ON(display->drm, !intel_fb_bo(&fb->base))) {
>> drm_dbg_kms(display->drm,
>> "no BIOS fb, allocating a new one\n");
>>
>> fb = __intel_fbdev_fb_alloc(display, sizes);
>> - if (IS_ERR(fb))
>> - return PTR_ERR(fb);
>> + if (IS_ERR(fb)) {
>> + ret = PTR_ERR(fb);
>> + goto out_unlock;
>> + }
>> } else {
>> drm_dbg_kms(display->drm, "re-using BIOS fb\n");
>> prealloc = true;
>> @@ -302,8 +307,6 @@ int intel_fbdev_driver_fbdev_probe(struct drm_fb_helper *helper,
>> sizes->fb_height = fb->base.height;
>> }
>>
>> - wakeref = intel_display_rpm_get(display);
>> -
>> /* Pin the GGTT vma for our access via info->screen_base.
>> * This also validates that any existing fb inherited from the
>> * BIOS is suitable for own access.
next prev parent reply other threads:[~2025-11-10 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 12:03 [PATCH] drm/i915/fbdev: Hold runtime PM ref during fbdev BO creation Dibin Moolakadan Subrahmanian
2025-11-06 13:30 ` Jani Nikula
2025-11-06 13:30 ` Jani Nikula
2025-11-10 15:26 ` Dibin Moolakadan Subrahmanian [this message]
2025-11-10 20:28 ` Jani Nikula
2025-11-06 13:34 ` ✓ i915.CI.BAT: success for " Patchwork
2025-11-07 8:33 ` ✗ i915.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=602bb5d3-fe1f-47c3-8775-3078d0fc7bc3@intel.com \
--to=dibin.moolakadan.subrahmanian@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.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