All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Preston <thomas.preston@codethink.co.uk>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
	airlied@linux.ie, intel-gfx@lists.freedesktop.org,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915/ddi: Fix default eDP detection on port A
Date: Thu, 7 Mar 2019 10:02:20 +0000	[thread overview]
Message-ID: <a1434319-daba-756f-34c7-3ea653a9d2eb@codethink.co.uk> (raw)
In-Reply-To: <874l8fm72f.fsf@intel.com>

Hi,
Thanks for looking at this.

On 07/03/2019 08:18, Jani Nikula wrote:
> 
> The subject should probably have "drm/i915/bios" or "drm/i915/vbt".
> 

Noted

> On Wed, 06 Mar 2019, Thomas Preston <thomas.preston@codethink.co.uk> wrote:
>> We rely on VBT DDI port info for eDP detection on GEN9 platforms and
>> above. This breaks GEN9 platforms which don't have VBT because port A
>> eDP now defaults to false. Fix this by defaulting to true when VBT is
>> missing.
> 
> Please include more details about the machine that doesn't have VBT. Why
> don't you have VBT?
> 

We have upgraded from an earlier kernel version (an Intel BSP on v4.1)
which did not require VBT and so our BIOS isn't set up correctly. The
BIOS doesn't set ASLS and fails to find ACPI OpRegion:

[    9.368433] [drm:intel_opregion_setup [i915]] graphic opregion physical addr: 0x0
[    9.368490] [drm:intel_opregion_setup [i915]] ACPI OpRegion not supported!

So now our port A is DP instead of eDP. I was hoping a return to "default"
values would remedy this, but I think it's pretty clear now that we should
focus on fixing VBT.

I've found a default VBT in the BSP but not sure how to get it into BIOS.
If you could point me in the right direction here that would be really
useful!

> Personally I think it was a mistake originally to make guesses about the
> outputs in absence of VBT on DDI platforms, because we can never get the
> generic guesses right across all ports and all products. And for the
> record, that was the result of an easy choice to enable developers way
> back when, and forgotten.
> 
> Certainly eDP is more likely than something else on port A. But this
> will break any outlier products without VBT that have a non-eDP output
> on port A. I guess it's a risk we have to take, and handle the fallout
> later.
> 
> Acked-by: Jani Nikula <jani.nikula@intel.com>
> 
>> Fixes: commit a98d9c1d7e9b ("drm/i915/ddi: Rely on VBT DDI port info for eDP detection")
> 
> The Fixes: format does *not* include "commit" text.
> 

I got that from scripts/checkpatch.pl but noted, thanks.

Kind regards,
Tom

  reply	other threads:[~2019-03-07 10:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 20:06 [PATCH] drm/i915/ddi: Fix default eDP detection on port A Thomas Preston
2019-03-06 21:44 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-03-07  8:18 ` [PATCH] " Jani Nikula
2019-03-07  8:18   ` Jani Nikula
2019-03-07 10:02   ` Thomas Preston [this message]
2019-03-07 10:34     ` Jani Nikula
2019-03-07 10:49       ` Thomas Preston
2019-03-07 10:49         ` Thomas Preston
2019-03-07 11:32         ` Jani Nikula
2019-03-07 11:32           ` Jani Nikula
2019-03-13 16:13           ` Jani Nikula
2019-03-07 16:03       ` Thomas Preston
2019-03-07 16:03         ` Thomas Preston
2019-03-07 14:43 ` ✓ Fi.CI.BAT: success for drm/i915/ddi: Fix default eDP detection on port A (rev2) Patchwork
2019-03-07 16:06 ` ✗ Fi.CI.BAT: failure for drm/i915/ddi: Fix default eDP detection on port A (rev3) Patchwork
2019-03-07 17:20 ` ✓ Fi.CI.IGT: success for drm/i915/ddi: Fix default eDP detection on port A (rev2) 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=a1434319-daba-756f-34c7-3ea653a9d2eb@codethink.co.uk \
    --to=thomas.preston@codethink.co.uk \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.