All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>,
	Clint Taylor <clinton.a.taylor@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/cnl: Don't trust VBT's alternate pin for port D for now.
Date: Mon, 10 Jul 2017 10:37:13 +0300	[thread overview]
Message-ID: <87y3rwpwt2.fsf@nikula.org> (raw)
In-Reply-To: <CABVU7+sLQytsfQ5Jf8f3a7R0g5hBaQb5=1z9jULwfnLcX1MnVg@mail.gmail.com>

On Fri, 07 Jul 2017, Rodrigo Vivi <rodrigo.vivi@gmail.com> wrote:
> patch merged to dinq. thanks for reviewing.

Did you report the VBT issue? Whenever we paper over bugs in other
components, we're sending a message it's fine. It's not.

BR,
Jani.


>
> On Thu, Jul 6, 2017 at 2:52 PM, Clint Taylor <clinton.a.taylor@intel.com> wrote:
>>
>>
>> On 07/06/2017 02:08 PM, Rodrigo Vivi wrote:
>>>
>>> Cannon Lake's VBT that is currently available for B0 stepping
>>> states that port D uses alternate pin 3 messing up with the
>>> default pin-port mapping table. Using that information we cannot
>>> get HDMI working properly. So for now we don't relly on VBT for
>>> this information.
>>>
>>> Cc: Clint Taylor <clinton.a.taylor@intel.com>
>>> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>>> ---
>>>   drivers/gpu/drm/i915/intel_bios.c | 9 +++++++++
>>>   1 file changed, 9 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/i915/intel_bios.c
>>> b/drivers/gpu/drm/i915/intel_bios.c
>>> index 639d45c..82b144c 100644
>>> --- a/drivers/gpu/drm/i915/intel_bios.c
>>> +++ b/drivers/gpu/drm/i915/intel_bios.c
>>> @@ -1187,6 +1187,15 @@ static void parse_ddi_port(struct drm_i915_private
>>> *dev_priv, enum port port,
>>>         if (is_dvi) {
>>>                 info->alternate_ddc_pin = ddc_pin;
>>>   +             /*
>>> +                * All VBTs that we got so far for B Stepping has this
>>> +                * information wrong for Port D. So, let's just ignore for
>>> now.
>>> +                */
>>> +               if (IS_CNL_REVID(dev_priv, CNL_REVID_B0, CNL_REVID_B0) &&
>>> +                   port == PORT_D) {
>>> +                       info->alternate_ddc_pin = 0;
>>> +               }
>>> +
>>
>>
>> Reviewed-by: Clinton Taylor <clinton.a.taylor@intel.com>
>>
>> -Clint
>>
>>>                 sanitize_ddc_pin(dev_priv, port);
>>>         }
>>>
>>
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-07-10  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 21:08 [PATCH] drm/i915/cnl: Don't trust VBT's alternate pin for port D for now Rodrigo Vivi
2017-07-06 21:52 ` Clint Taylor
2017-07-07 16:38   ` Rodrigo Vivi
2017-07-10  7:37     ` Jani Nikula [this message]
2017-07-07  8:45 ` ✓ Fi.CI.BAT: success for " 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=87y3rwpwt2.fsf@nikula.org \
    --to=jani.nikula@linux.intel.com \
    --cc=clinton.a.taylor@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@gmail.com \
    --cc=rodrigo.vivi@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.