From: Matt Roper <matthew.d.roper@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/bxt: fix DDI PHY vswing scale value setting
Date: Wed, 10 Jun 2015 09:18:29 -0700 [thread overview]
Message-ID: <20150610161829.GD15024@intel.com> (raw)
In-Reply-To: <1433430095-26801-1-git-send-email-imre.deak@intel.com>
On Thu, Jun 04, 2015 at 06:01:35PM +0300, Imre Deak wrote:
> According to bspec the DDI PHY vswing scale value is "don't care" in
> case the scale enable bit [27] is clear. But this doesn't seem to be
> correct. The scale value seems to also matter if the scale mode bit
> [26] is set. So both bit 26 and 27 depend on the value. Setting the
> scale value to 0 while either bit is set results in a failed modeset on
> HDMI (sink reports no signal).
>
> After reset the scale value is 0x98, but according to the spec we have
> to program it to 0x9a. So for consistency program it always to 0x9a
> regardless of the scale enable bit.
>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
This patch successfully enables HDMI display for my team.
Tested-by: Matt Roper <matthew.d.roper@intel.com>
> ---
> drivers/gpu/drm/i915/intel_ddi.c | 36 ++++++++++++++++++------------------
> 1 file changed, 18 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> index 832e4e1..5246cfa 100644
> --- a/drivers/gpu/drm/i915/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/intel_ddi.c
> @@ -181,15 +181,15 @@ struct bxt_ddi_buf_trans {
> */
> static const struct bxt_ddi_buf_trans bxt_ddi_translations_dp[] = {
> /* Idx NT mV diff db */
> - { 52, 0, 0, 128, true }, /* 0: 400 0 */
> - { 78, 0, 0, 85, false }, /* 1: 400 3.5 */
> - { 104, 0, 0, 64, false }, /* 2: 400 6 */
> - { 154, 0, 0, 43, false }, /* 3: 400 9.5 */
> - { 77, 0, 0, 128, false }, /* 4: 600 0 */
> - { 116, 0, 0, 85, false }, /* 5: 600 3.5 */
> - { 154, 0, 0, 64, false }, /* 6: 600 6 */
> - { 102, 0, 0, 128, false }, /* 7: 800 0 */
> - { 154, 0, 0, 85, false }, /* 8: 800 3.5 */
> + { 52, 0x9A, 0, 128, true }, /* 0: 400 0 */
> + { 78, 0x9A, 0, 85, false }, /* 1: 400 3.5 */
> + { 104, 0x9A, 0, 64, false }, /* 2: 400 6 */
> + { 154, 0x9A, 0, 43, false }, /* 3: 400 9.5 */
> + { 77, 0x9A, 0, 128, false }, /* 4: 600 0 */
> + { 116, 0x9A, 0, 85, false }, /* 5: 600 3.5 */
> + { 154, 0x9A, 0, 64, false }, /* 6: 600 6 */
> + { 102, 0x9A, 0, 128, false }, /* 7: 800 0 */
> + { 154, 0x9A, 0, 85, false }, /* 8: 800 3.5 */
> { 154, 0x9A, 1, 128, false }, /* 9: 1200 0 */
> };
>
> @@ -198,15 +198,15 @@ static const struct bxt_ddi_buf_trans bxt_ddi_translations_dp[] = {
> */
> static const struct bxt_ddi_buf_trans bxt_ddi_translations_hdmi[] = {
> /* Idx NT mV diff db */
> - { 52, 0, 0, 128, false }, /* 0: 400 0 */
> - { 52, 0, 0, 85, false }, /* 1: 400 3.5 */
> - { 52, 0, 0, 64, false }, /* 2: 400 6 */
> - { 42, 0, 0, 43, false }, /* 3: 400 9.5 */
> - { 77, 0, 0, 128, false }, /* 4: 600 0 */
> - { 77, 0, 0, 85, false }, /* 5: 600 3.5 */
> - { 77, 0, 0, 64, false }, /* 6: 600 6 */
> - { 102, 0, 0, 128, false }, /* 7: 800 0 */
> - { 102, 0, 0, 85, false }, /* 8: 800 3.5 */
> + { 52, 0x9A, 0, 128, false }, /* 0: 400 0 */
> + { 52, 0x9A, 0, 85, false }, /* 1: 400 3.5 */
> + { 52, 0x9A, 0, 64, false }, /* 2: 400 6 */
> + { 42, 0x9A, 0, 43, false }, /* 3: 400 9.5 */
> + { 77, 0x9A, 0, 128, false }, /* 4: 600 0 */
> + { 77, 0x9A, 0, 85, false }, /* 5: 600 3.5 */
> + { 77, 0x9A, 0, 64, false }, /* 6: 600 6 */
> + { 102, 0x9A, 0, 128, false }, /* 7: 800 0 */
> + { 102, 0x9A, 0, 85, false }, /* 8: 800 3.5 */
> { 154, 0x9A, 1, 128, true }, /* 9: 1200 0 */
> };
>
> --
> 2.1.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Matt Roper
Graphics Software Engineer
IoTG Platform Enabling & Development
Intel Corporation
(916) 356-2795
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-10 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 15:01 [PATCH] drm/i915/bxt: fix DDI PHY vswing scale value setting Imre Deak
2015-06-05 9:22 ` shuang.he
2015-06-10 16:18 ` Matt Roper [this message]
2015-06-11 10:34 ` Damien Lespiau
2015-06-12 7:48 ` Jani Nikula
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=20150610161829.GD15024@intel.com \
--to=matthew.d.roper@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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