From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/6] drm/i915/bios: Use i915->vbt.ports[] on CHV
Date: Wed, 22 Dec 2021 14:49:16 +0200 [thread overview]
Message-ID: <YcMezDqj7XrwZ2k1@intel.com> (raw)
In-Reply-To: <87fsqlypox.fsf@intel.com>
On Wed, Dec 22, 2021 at 11:05:50AM +0200, Jani Nikula wrote:
> On Fri, 17 Dec 2021, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > CHV is currently straddling the divide by using parse_ddi_ports() stuff
> > for aux_ch/ddc_pin but going through all old codepaths for the rest
> > (intel_bios_is_port_present(), intel_bios_is_port_edp(),
> > intel_bios_is_port_dp_dual_mode()). Let's switch over full and use
> > i915->vbt.ports[] for the rest of the stuff.
>
> Whoa, this is far more subtle than what the code looks!
>
> We stop checking for port A for CHV in intel_bios_is_port_present(), but
> it's a warn and I don't recall any bug reports, so probably fine. We
> could add a check in parse_ddi_port(), but meh.
>
> Ditto for intel_bios_is_port_dp_dual_mode(), except it doesn't have a
> warn.
>
> The eDP check in intel_bios_is_port_edp() becomes slightly more
> relaxed. Both the old and new check require these to be set:
>
> - DEVICE_TYPE_DISPLAYPORT_OUTPUT
> - DEVICE_TYPE_INTERNAL_CONNECTOR.
>
> The old code also required these to be unset:
>
> - DEVICE_TYPE_MIPI_OUTPUT
> - DEVICE_TYPE_COMPOSITE_OUTPUT
> - DEVICE_TYPE_DUAL_CHANNEL
> - DEVICE_TYPE_LVDS_SIGNALING
> - DEVICE_TYPE_TMDS_DVI_SIGNALING
> - DEVICE_TYPE_VIDEO_SIGNALING
> - DEVICE_TYPE_ANALOG_OUTPUT
>
> It's possible we've added these just as a sanity check for broken VBTs
> more than anything. I guess I'd see if actual problems arise.
>
> Bottom line, I think the functional changes matter only for VBTs with
> bogus data.
Yeah, I should probably include a bit more of thse details in this
commit message as well to make it easier to figure out what actually
changed if we get a regressoion.
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Thanks.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2021-12-22 12:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 15:53 [Intel-gfx] [PATCH 0/6] drm/i915: Extend parse_ddi_port() to all g4x+ platforms Ville Syrjala
2021-12-17 15:53 ` [Intel-gfx] [PATCH 1/6] drm/i915/bios: Introduce has_ddi_port_info() Ville Syrjala
2021-12-22 8:48 ` Jani Nikula
2021-12-17 15:53 ` [Intel-gfx] [PATCH 2/6] drm/i915/bios: Use i915->vbt.ports[] on CHV Ville Syrjala
2021-12-22 9:05 ` Jani Nikula
2021-12-22 12:49 ` Ville Syrjälä [this message]
2021-12-22 9:13 ` Jani Nikula
2021-12-17 15:54 ` [Intel-gfx] [PATCH 3/6] drm/i915/bios: Use i915->vbt.ports[] for all g4x+ Ville Syrjala
2021-12-22 9:19 ` Jani Nikula
2021-12-17 15:54 ` [Intel-gfx] [PATCH 4/6] drm/i915/bios: Throw out the !has_ddi_port_info() codepaths Ville Syrjala
2021-12-22 9:25 ` Jani Nikula
2021-12-17 15:54 ` [Intel-gfx] [PATCH 5/6] drm/i915/bios: Nuke DEVICE_TYPE_DP_DUAL_MODE_BITS Ville Syrjala
2021-12-22 9:34 ` Jani Nikula
2021-12-22 12:53 ` Ville Syrjälä
2021-12-17 15:54 ` [Intel-gfx] [PATCH 6/6] drm/i915/hdmi: Ignore DP++ TMDS clock limit for native HDMI ports Ville Syrjala
2021-12-22 9:47 ` Jani Nikula
2021-12-22 12:46 ` Ville Syrjälä
2021-12-22 15:38 ` Ville Syrjälä
2021-12-22 16:17 ` [Intel-gfx] [PATCH v2 " Ville Syrjala
2021-12-17 17:17 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Extend parse_ddi_port() to all g4x+ platforms Patchwork
2021-12-17 19:56 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-12-22 17:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Extend parse_ddi_port() to all g4x+ platforms (rev2) Patchwork
2021-12-22 20:28 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-01-19 22:21 ` [Intel-gfx] [PATCH 0/6] drm/i915: Extend parse_ddi_port() to all g4x+ platforms Ville Syrjälä
2022-01-20 10:14 ` 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=YcMezDqj7XrwZ2k1@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox