From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/dsi: debug log send packet sequence contents
Date: Tue, 28 Oct 2025 20:03:15 +0200 [thread overview]
Message-ID: <aQEFY6_JA9oE66vF@intel.com> (raw)
In-Reply-To: <20251028155712.1824565-2-jani.nikula@intel.com>
On Tue, Oct 28, 2025 at 05:57:12PM +0200, Jani Nikula wrote:
> This might help debug issues better than just debug logging the function
> name.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dsi_vbt.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dsi_vbt.c b/drivers/gpu/drm/i915/display/intel_dsi_vbt.c
> index 748e5462bd95..2528c0996c25 100644
> --- a/drivers/gpu/drm/i915/display/intel_dsi_vbt.c
> +++ b/drivers/gpu/drm/i915/display/intel_dsi_vbt.c
> @@ -107,8 +107,7 @@ static const u8 *mipi_exec_send_packet(struct intel_dsi *intel_dsi,
> u16 len;
> enum port port;
> ssize_t ret;
> -
> - drm_dbg_kms(display->drm, "\n");
> + bool hs_mode;
>
> flags = *data++;
> type = *data++;
> @@ -130,13 +129,18 @@ static const u8 *mipi_exec_send_packet(struct intel_dsi *intel_dsi,
> goto out;
> }
>
> - if ((flags >> MIPI_TRANSFER_MODE_SHIFT) & 1)
> + hs_mode = (flags >> MIPI_TRANSFER_MODE_SHIFT) & 1;
> + if (hs_mode)
> dsi_device->mode_flags &= ~MIPI_DSI_MODE_LPM;
> else
> dsi_device->mode_flags |= MIPI_DSI_MODE_LPM;
>
> dsi_device->channel = (flags >> MIPI_VIRTUAL_CHANNEL_SHIFT) & 3;
>
> + drm_dbg_kms(display->drm, "DSI packet: Port %c (seq %u), Flags 0x%02x, VC %u, %s, Type %u, Length %u, Data %*ph\n",
> + port_name(port), seq_port, flags, dsi_device->channel,
> + hs_mode ? "HS" : "LP", type, len, (int)len, data);
We're printing the type as hex in igt, and looks like the enum uses
hex as well, and the DSI spec has both hex and binary. So seems to
me that hex would be the best way to go here too.
Otherwise lgtm
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> +
> switch (type) {
> case MIPI_DSI_GENERIC_SHORT_WRITE_0_PARAM:
> ret = mipi_dsi_generic_write(dsi_device, NULL, 0);
> --
> 2.47.3
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-10-28 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 15:57 [PATCH 1/2] drm/i915/dsi: log send packet sequence errors Jani Nikula
2025-10-28 15:57 ` [PATCH 2/2] drm/i915/dsi: debug log send packet sequence contents Jani Nikula
2025-10-28 18:03 ` Ville Syrjälä [this message]
2025-10-28 16:38 ` [PATCH 1/2] drm/i915/dsi: log send packet sequence errors Ville Syrjälä
2025-10-28 16:46 ` ✓ i915.CI.BAT: success for series starting with [1/2] " Patchwork
2025-10-29 0:46 ` ✗ 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=aQEFY6_JA9oE66vF@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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