From: Jani Nikula <jani.nikula@intel.com>
To: Madhav Chauhan <madhav.chauhan@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: ander.conselvan.de.oliveira@intel.com, shashidhar.hiremath@intel.com
Subject: Re: [PATCH 1/2] drm/i915/glk: Calculate high/low switch count for GLK
Date: Mon, 15 May 2017 18:48:20 +0300 [thread overview]
Message-ID: <87lgpydsu3.fsf@intel.com> (raw)
In-Reply-To: <1494336565-19185-1-git-send-email-madhav.chauhan@intel.com>
On Tue, 09 May 2017, Madhav Chauhan <madhav.chauhan@intel.com> wrote:
> As per BSPEC, high/low switch count to be programmed in
> terms of byteclock using exit_zero_count and prep_count.
> For Geminilake exit/prep counts are already calculated
> in terms of byteclock. This patch calculates high/low
> switch count using counts value in byteclock, old calculation
> leads to screen flicker/shift issue while resuming from S3/S4.
>
> Signed-off-by: Madhav Chauhan <madhav.chauhan@intel.com>
Pushed this patch to drm-intel-next-queued, thanks for the patch.
BR,
Jani.
> ---
> drivers/gpu/drm/i915/intel_dsi_vbt.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dsi_vbt.c b/drivers/gpu/drm/i915/intel_dsi_vbt.c
> index 0dce779..7158c7c 100644
> --- a/drivers/gpu/drm/i915/intel_dsi_vbt.c
> +++ b/drivers/gpu/drm/i915/intel_dsi_vbt.c
> @@ -694,8 +694,8 @@ bool intel_dsi_vbt_init(struct intel_dsi *intel_dsi, u16 panel_id)
> clk_zero_cnt << 8 | prepare_cnt;
>
> /*
> - * LP to HS switch count = 4TLPX + PREP_COUNT * 2 + EXIT_ZERO_COUNT * 2
> - * + 10UI + Extra Byte Count
> + * LP to HS switch count = 4TLPX + PREP_COUNT * mul + EXIT_ZERO_COUNT *
> + * mul + 10UI + Extra Byte Count
> *
> * HS to LP switch count = THS-TRAIL + 2TLPX + Extra Byte Count
> * Extra Byte Count is calculated according to number of lanes.
> @@ -708,8 +708,8 @@ bool intel_dsi_vbt_init(struct intel_dsi *intel_dsi, u16 panel_id)
> /* B044 */
> /* FIXME:
> * The comment above does not match with the code */
> - lp_to_hs_switch = DIV_ROUND_UP(4 * tlpx_ui + prepare_cnt * 2 +
> - exit_zero_cnt * 2 + 10, 8);
> + lp_to_hs_switch = DIV_ROUND_UP(4 * tlpx_ui + prepare_cnt * mul +
> + exit_zero_cnt * mul + 10, 8);
>
> hs_to_lp_switch = DIV_ROUND_UP(mipi_config->ths_trail + 2 * tlpx_ui, 8);
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-05-15 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 13:29 [PATCH 1/2] drm/i915/glk: Calculate high/low switch count for GLK Madhav Chauhan
2017-05-09 13:29 ` [PATCH 2/2] drm/i915/glk: Enable cold boot for GLK DSI Madhav Chauhan
2017-05-09 13:58 ` Ville Syrjälä
2017-05-15 15:49 ` Jani Nikula
2017-05-15 17:42 ` Chauhan, Madhav
2017-05-24 13:51 ` Jani Nikula
2017-05-24 18:00 ` Chauhan, Madhav
2017-05-30 7:03 ` Jani Nikula
2017-05-30 9:10 ` Chauhan, Madhav
2017-05-09 14:09 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/glk: Calculate high/low switch count for GLK Patchwork
2017-05-15 15:48 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-08 15:29 [PATCH 1/2] " Madhav Chauhan
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=87lgpydsu3.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=madhav.chauhan@intel.com \
--cc=shashidhar.hiremath@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.