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 3/5] drm/i915/dsi: Make 'clock_stop' boolean
Date: Thu, 26 Mar 2026 15:40:56 +0200 [thread overview]
Message-ID: <1558669af43583b072c8c58eff1e01960c2d9f8c@intel.com> (raw)
In-Reply-To: <20260326111814.9800-4-ville.syrjala@linux.intel.com>
On Thu, 26 Mar 2026, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> The DSI 'clock_stop' parameter is a boolean, so use a real
> 'bool' for it. And pimp the debug print while at it.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dsi.h | 2 +-
> drivers/gpu/drm/i915/display/intel_dsi_vbt.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dsi.h b/drivers/gpu/drm/i915/display/intel_dsi.h
> index 8e39d2b52c54..0023ac341aa0 100644
> --- a/drivers/gpu/drm/i915/display/intel_dsi.h
> +++ b/drivers/gpu/drm/i915/display/intel_dsi.h
> @@ -81,7 +81,7 @@ struct intel_dsi {
> int video_mode;
>
> bool eot_pkt;
> - u8 clock_stop;
> + bool clock_stop;
>
> u8 escape_clk_div;
> u8 dual_link;
> diff --git a/drivers/gpu/drm/i915/display/intel_dsi_vbt.c b/drivers/gpu/drm/i915/display/intel_dsi_vbt.c
> index 51f6a5b82cb2..23da7f5f9578 100644
> --- a/drivers/gpu/drm/i915/display/intel_dsi_vbt.c
> +++ b/drivers/gpu/drm/i915/display/intel_dsi_vbt.c
> @@ -719,7 +719,7 @@ void intel_dsi_log_params(struct intel_dsi *intel_dsi)
> drm_printf(&p, "Burst mode ratio %d\n", intel_dsi->burst_mode_ratio);
> drm_printf(&p, "Reset timer %d\n", intel_dsi->rst_timer_val);
> drm_printf(&p, "EoT packet %s\n", str_enabled_disabled(intel_dsi->eot_pkt));
> - drm_printf(&p, "Clockstop %s\n", str_enabled_disabled(!intel_dsi->clock_stop));
> + drm_printf(&p, "Clock stop during BLLP %s\n", str_enabled_disabled(intel_dsi->clock_stop));
What's with the reversed !intel_dsi->clock_stop in the existing log and
the change here?
> drm_printf(&p, "Mode %s\n", intel_dsi->operation_mode ? "command" : "video");
> if (intel_dsi->dual_link == DSI_DUAL_LINK_FRONT_BACK)
> drm_printf(&p, "Dual link: DSI_DUAL_LINK_FRONT_BACK\n");
> @@ -771,7 +771,7 @@ bool intel_dsi_vbt_init(struct intel_dsi *intel_dsi, u16 panel_id)
> drm_dbg_kms(display->drm, "\n");
>
> intel_dsi->eot_pkt = !mipi_config->eot_pkt_disabled;
> - intel_dsi->clock_stop = mipi_config->enable_clk_stop ? 1 : 0;
> + intel_dsi->clock_stop = mipi_config->enable_clk_stop;
> intel_dsi->lane_count = mipi_config->lane_cnt + 1;
> intel_dsi->pixel_format =
> vbt_to_dsi_pixel_format(mipi_config->videomode_color_format);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-03-26 13:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 11:18 [PATCH 0/5] drm/i915/dsi: Some DSI fixes and improvements Ville Syrjala
2026-03-26 11:18 ` [PATCH 1/5] drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode Ville Syrjala
2026-03-26 15:20 ` Jani Nikula
2026-03-26 11:18 ` [PATCH 2/5] drm/i915/dsi: s/eotp_pkt/eot_pkt/ Ville Syrjala
2026-03-26 15:22 ` Jani Nikula
2026-03-26 11:18 ` [PATCH 3/5] drm/i915/dsi: Make 'clock_stop' boolean Ville Syrjala
2026-03-26 13:40 ` Jani Nikula [this message]
2026-03-26 14:02 ` Ville Syrjälä
2026-03-26 15:01 ` Jani Nikula
2026-03-26 15:16 ` Ville Syrjälä
2026-03-26 15:22 ` Jani Nikula
2026-03-26 11:18 ` [PATCH 4/5] drm/i915/dsi: Fill BLLPs with blanking packets if requested Ville Syrjala
2026-03-26 15:23 ` Jani Nikula
2026-03-26 11:18 ` [PATCH 5/5] drm/i915/dsi: Place clock into LP during LPM " Ville Syrjala
2026-03-26 15:24 ` Jani Nikula
2026-03-26 11:24 ` ✗ CI.checkpatch: warning for drm/i915/dsi: Some DSI fixes and improvements Patchwork
2026-03-26 11:26 ` ✓ CI.KUnit: success " Patchwork
2026-03-26 12:00 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-27 0:36 ` ✓ Xe.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=1558669af43583b072c8c58eff1e01960c2d9f8c@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