From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915/dsi: improve dphy param limits logging
Date: Thu, 19 Apr 2018 12:28:50 +0300 [thread overview]
Message-ID: <20180419092850.GZ17795@intel.com> (raw)
In-Reply-To: <20180419085940.21505-1-jani.nikula@intel.com>
On Thu, Apr 19, 2018 at 11:59:39AM +0300, Jani Nikula wrote:
> Move the limit checks near the calculations for each field, and actually
> log the values that exceed limits.
>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_dsi_vbt.c | 34 ++++++++++++++++++----------------
> 1 file changed, 18 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dsi_vbt.c b/drivers/gpu/drm/i915/intel_dsi_vbt.c
> index 91c07b0c8db9..4d6ffa7b3e7b 100644
> --- a/drivers/gpu/drm/i915/intel_dsi_vbt.c
> +++ b/drivers/gpu/drm/i915/intel_dsi_vbt.c
> @@ -647,6 +647,11 @@ bool intel_dsi_vbt_init(struct intel_dsi *intel_dsi, u16 panel_id)
> /* prepare count */
> prepare_cnt = DIV_ROUND_UP(ths_prepare_ns * ui_den, ui_num * mul);
>
> + if (prepare_cnt > PREPARE_CNT_MAX) {
> + DRM_DEBUG_KMS("prepare count too high %u\n", prepare_cnt);
> + prepare_cnt = PREPARE_CNT_MAX;
> + }
> +
> /* exit zero count */
> exit_zero_cnt = DIV_ROUND_UP(
> (ths_prepare_hszero - ths_prepare_ns) * ui_den,
> @@ -662,32 +667,29 @@ bool intel_dsi_vbt_init(struct intel_dsi *intel_dsi, u16 panel_id)
> if (exit_zero_cnt < (55 * ui_den / ui_num) && (55 * ui_den) % ui_num)
> exit_zero_cnt += 1;
>
> + if (exit_zero_cnt > EXIT_ZERO_CNT_MAX) {
> + DRM_DEBUG_KMS("exit zero count too high %u\n", exit_zero_cnt);
> + exit_zero_cnt = EXIT_ZERO_CNT_MAX;
> + }
> +
> /* clk zero count */
> clk_zero_cnt = DIV_ROUND_UP(
> (tclk_prepare_clkzero - ths_prepare_ns)
> * ui_den, ui_num * mul);
>
> + if (clk_zero_cnt > CLK_ZERO_CNT_MAX) {
> + DRM_DEBUG_KMS("clock zero count too high %u\n", clk_zero_cnt);
> + clk_zero_cnt = CLK_ZERO_CNT_MAX;
> + }
> +
> /* trail count */
> tclk_trail_ns = max(mipi_config->tclk_trail, mipi_config->ths_trail);
> trail_cnt = DIV_ROUND_UP(tclk_trail_ns * ui_den, ui_num * mul);
>
> - if (prepare_cnt > PREPARE_CNT_MAX ||
> - exit_zero_cnt > EXIT_ZERO_CNT_MAX ||
> - clk_zero_cnt > CLK_ZERO_CNT_MAX ||
> - trail_cnt > TRAIL_CNT_MAX)
> - DRM_DEBUG_DRIVER("Values crossing maximum limits, restricting to max values\n");
> -
> - if (prepare_cnt > PREPARE_CNT_MAX)
> - prepare_cnt = PREPARE_CNT_MAX;
> -
> - if (exit_zero_cnt > EXIT_ZERO_CNT_MAX)
> - exit_zero_cnt = EXIT_ZERO_CNT_MAX;
> -
> - if (clk_zero_cnt > CLK_ZERO_CNT_MAX)
> - clk_zero_cnt = CLK_ZERO_CNT_MAX;
> -
> - if (trail_cnt > TRAIL_CNT_MAX)
> + if (trail_cnt > TRAIL_CNT_MAX) {
> + DRM_DEBUG_KMS("trail count too high %u\n", trail_cnt);
> trail_cnt = TRAIL_CNT_MAX;
> + }
>
> /* B080 */
> intel_dsi->dphy_reg = exit_zero_cnt << 24 | trail_cnt << 16 |
> --
> 2.11.0
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-04-19 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 8:59 [PATCH 1/2] drm/i915/dsi: improve dphy param limits logging Jani Nikula
2018-04-19 8:59 ` [PATCH 2/2] drm/i915/dsi: fix dphy param field widths and range checks for chv+ Jani Nikula
2018-04-19 11:09 ` Ville Syrjälä
2018-04-19 11:09 ` Ville Syrjälä
2018-04-19 12:25 ` Jani Nikula
2018-04-19 13:55 ` Jani Nikula
2018-04-19 13:55 ` Jani Nikula
2018-04-19 9:02 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/dsi: improve dphy param limits logging Patchwork
2018-04-19 9:03 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-04-19 9:19 ` ✓ Fi.CI.BAT: success " Patchwork
2018-04-19 9:28 ` Ville Syrjälä [this message]
2018-04-19 11:07 ` ✓ Fi.CI.IGT: " 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=20180419092850.GZ17795@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@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 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.