From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915/bios: Use the platform's port_mask when there is no VBT
Date: Tue, 19 Mar 2024 12:20:58 +0200 [thread overview]
Message-ID: <87h6h2o73p.fsf@intel.com> (raw)
In-Reply-To: <20240319092443.15769-2-ville.syrjala@linux.intel.com>
On Tue, 19 Mar 2024, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> When we have no VBT we currently assume ports A-F are
> all pontially valid for every platform. That is nonsense.
> Grab the bitmask of valid ports from the runtime info
> instead.
>
> Although the defaults we actually fill here look semi-sensible
> only for hsw-skl era hardware. Dunno if we should try to do
> something more appropriate here for other platforms,
> or just try to nuke the whole thing?
Seems like doing something appropriate is an endless task. We should
never have added the defaults, but here we are. Can we remove them for
newer platforms? There's only one way to find out...
Commit 828ccb31cf41 ("drm/i915/icl: Add TypeC ports only if VBT is
present") fails to mention if this was to address a real issue on ICL
without VBT, or just playing it safe.
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_bios.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_bios.c b/drivers/gpu/drm/i915/display/intel_bios.c
> index c13a98431a7b..2abd2d7ceda2 100644
> --- a/drivers/gpu/drm/i915/display/intel_bios.c
> +++ b/drivers/gpu/drm/i915/display/intel_bios.c
> @@ -2890,9 +2890,8 @@ init_vbt_panel_defaults(struct intel_panel *panel)
> static void
> init_vbt_missing_defaults(struct drm_i915_private *i915)
> {
> + unsigned int ports = DISPLAY_RUNTIME_INFO(i915)->port_mask;
> enum port port;
> - int ports = BIT(PORT_A) | BIT(PORT_B) | BIT(PORT_C) |
> - BIT(PORT_D) | BIT(PORT_E) | BIT(PORT_F);
I was wondering why we don't just
-#define for_each_port(__port) \
- for ((__port) = PORT_A; (__port) < I915_MAX_PORTS; (__port)++)
+#define for_each_port(__i915, __port) \
+ for_each_set_bit(__port, &DISPLAY_RUNTIME_INFO(__i915)->port_mask, sizeof(DISPLAY_RUNTIME_INFO(__i915)->port_mask))
but then we have DSI code that relies on it returning PORT_A for DSI.
Ugh. It's all so brittle.
Anyway, the patch is
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> if (!HAS_DDI(i915) && !IS_CHERRYVIEW(i915))
> return;
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-03-19 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 9:24 [PATCH 1/2] drm/i915/bios: Tolerate devdata==NULL in intel_bios_encoder_supports_dp_dual_mode() Ville Syrjala
2024-03-19 9:24 ` [PATCH 2/2] drm/i915/bios: Use the platform's port_mask when there is no VBT Ville Syrjala
2024-03-19 10:20 ` Jani Nikula [this message]
2024-03-19 9:29 ` [PATCH 1/2] drm/i915/bios: Tolerate devdata==NULL in intel_bios_encoder_supports_dp_dual_mode() Jani Nikula
2024-03-19 18:11 ` Ville Syrjälä
2024-03-25 10:32 ` Jani Nikula
2024-03-19 20:05 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] " Patchwork
2024-03-20 14:16 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915/bios: Tolerate devdata==NULL in intel_bios_encoder_supports_dp_dual_mode() (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=87h6h2o73p.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@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 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.