From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 05/14] drm/i915: Use drm_dbg_kms() for initial FB debugs
Date: Tue, 12 May 2026 13:40:11 +0300 [thread overview]
Message-ID: <09373911927701c841c50d91716bc2371c6f5283@intel.com> (raw)
In-Reply-To: <20260511214122.8468-6-ville.syrjala@linux.intel.com>
On Tue, 12 May 2026, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> The initial FB stuff is ultimately about display stuff, so
> use the proper display specific debug level for it.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/i915_initial_plane.c | 4 ++--
> drivers/gpu/drm/xe/display/xe_initial_plane.c | 12 ++++++------
> 2 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_initial_plane.c b/drivers/gpu/drm/i915/i915_initial_plane.c
> index 56d31f83707b..62365ba1ff97 100644
> --- a/drivers/gpu/drm/i915/i915_initial_plane.c
> +++ b/drivers/gpu/drm/i915/i915_initial_plane.c
> @@ -68,8 +68,8 @@ initial_plane_phys(struct drm_i915_private *i915,
> return false;
> }
>
> - drm_dbg(&i915->drm, "Using dma_addr=%pa, based on initial plane programming\n",
> - &dma_addr);
> + drm_dbg_kms(&i915->drm, "Using dma_addr=%pa, based on initial plane programming\n",
> + &dma_addr);
>
> *out_phys_base = dma_addr - mem->region.start;
> *out_mem = mem;
> diff --git a/drivers/gpu/drm/xe/display/xe_initial_plane.c b/drivers/gpu/drm/xe/display/xe_initial_plane.c
> index 1f2919797f6f..37cfc8a55031 100644
> --- a/drivers/gpu/drm/xe/display/xe_initial_plane.c
> +++ b/drivers/gpu/drm/xe/display/xe_initial_plane.c
> @@ -59,9 +59,9 @@ initial_plane_bo(struct xe_device *xe,
> return NULL;
> }
>
> - drm_dbg(&xe->drm,
> - "Using phys_base=%pa, based on initial plane programming\n",
> - &phys_base);
> + drm_dbg_kms(&xe->drm,
> + "Using phys_base=%pa, based on initial plane programming\n",
> + &phys_base);
> } else {
> struct ttm_resource_manager *stolen = ttm_manager_type(&xe->ttm, XE_PL_STOLEN);
>
> @@ -78,9 +78,9 @@ initial_plane_bo(struct xe_device *xe,
> bo = xe_bo_create_pin_map_at_novm(xe, tile0, size, phys_base,
> ttm_bo_type_kernel, flags, 0, false);
> if (IS_ERR(bo)) {
> - drm_dbg(&xe->drm,
> - "Failed to create bo phys_base=%pa size %u with flags %x: %li\n",
> - &phys_base, size, flags, PTR_ERR(bo));
> + drm_dbg_kms(&xe->drm,
> + "Failed to create bo phys_base=%pa size %u with flags %x: %li\n",
> + &phys_base, size, flags, PTR_ERR(bo));
> return NULL;
> }
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-05-12 10:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 21:41 [PATCH 00/14] drm/{i915,xe}: BIOS FB takeover fixes Ville Syrjala
2026-05-11 21:41 ` [PATCH 01/14] drm/i915: Disable the plane if initial plane config readout failed Ville Syrjala
2026-05-12 10:25 ` Jani Nikula
2026-05-11 21:41 ` [PATCH 02/14] drm/i915/fbdev: Extract bios_fb_ok() Ville Syrjala
2026-05-12 10:29 ` Jani Nikula
2026-05-11 21:41 ` [PATCH 03/14] drm/i915: Throw away the BIOS fb if has the wrong depth/bpp Ville Syrjala
2026-05-12 10:33 ` Jani Nikula
2026-05-11 21:41 ` [PATCH 04/14] drm/i915: Introduce intel_bo_fbdev_bios_fb_ok() Ville Syrjala
2026-05-11 21:41 ` [PATCH 05/14] drm/i915: Use drm_dbg_kms() for initial FB debugs Ville Syrjala
2026-05-12 10:40 ` Jani Nikula [this message]
2026-05-11 21:41 ` [PATCH 06/14] drm/xe: Do the initial FB size alignment earlier Ville Syrjala
2026-05-11 21:41 ` [PATCH 07/14] drm/xe/ggtt: Decouple lmem/stolen physcial offset from GGTT offset Ville Syrjala
2026-05-11 21:41 ` [PATCH 08/14] drm/xe: Print a debug message if we have no stolen for the initial FB Ville Syrjala
2026-05-12 10:45 ` Jani Nikula
2026-05-11 21:41 ` [PATCH 09/14] drm/xe: Abstract the initial FB PTE checks a bit Ville Syrjala
2026-05-12 10:48 ` Jani Nikula
2026-05-11 21:41 ` [PATCH 10/14] drm/xe: Check the PTE local memory bit for initial FB in stolen Ville Syrjala
2026-05-11 21:41 ` [PATCH 11/14] drm/xe: s/bar2/lmembar/ Ville Syrjala
2026-05-12 10:49 ` Jani Nikula
2026-05-11 21:41 ` [PATCH 12/14] drm/xe: Use the correct stolen offset in initial FB readout Ville Syrjala
2026-05-11 21:41 ` [PATCH 13/14] drm/i915: Fix BIOS FB memory region name debug prints Ville Syrjala
2026-05-11 21:41 ` [PATCH 14/14] drm/i915: Print the phys_base in addition to the dma_addr for the BIOS FB Ville Syrjala
2026-05-11 22:27 ` ✓ i915.CI.BAT: success for drm/{i915,xe}: BIOS FB takeover fixes Patchwork
2026-05-12 7:02 ` ✓ i915.CI.Full: " 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=09373911927701c841c50d91716bc2371c6f5283@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=ville.syrjala@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