Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp658440pxu; Thu, 7 Jan 2021 14:58:24 -0800 (PST) X-Google-Smtp-Source: ABdhPJyM+pyyXOQcaT12XzVTGyT8n2QXTtkVPFA1sbvFl/48m49dTZF0mTjuGAM1edsNAhHFGcP0 X-Received: by 2002:a50:875b:: with SMTP id 27mr3300276edv.24.1610060304633; Thu, 07 Jan 2021 14:58:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610060304; cv=none; d=google.com; s=arc-20160816; b=DI8DXlGy59DL8P5umJN4gQud34TqpZJvLtuxmphCnrONBf6Wtu/55BxXP+rjlC3Th7 OvJU2OLFRvBADKGRhvtb/BeYVuwChPtnEWT2KHYBKGhhLKEvubrqf2mdd/PzCLa3nU8P vqSoreZxVM3qPmIEW700tXQ33gBF84tk8l7ixy0yGOwTxrV8IQkoDLeLCu0S08BYmPFA 3W0uV9dWWKhgmrX5EaXv5qNdr6ylN3FTeWZ3ewOb+aW9tZP+x8jEnV445HRZ0A9ceXAd M8qUf58cxRHpWA66HqfVGGYphwZkxsA5gfP3A5zxRY5tHHnk7EhAcFuPtv2XsmNu7f7U OW4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=FefrCvtgHc4zx+jKJhsVluNmZv/u7VtNXp1c2c2tpc4=; b=DLbVQo/gieLWeT0tLHrery7y7givcgvDonPR5m9OrGttQjvtOCZHq3xW0WggeDfAbK lUvwe6t5aixGNsvaTdAn7+sE9x6PEsilz7xSHd/iRUfTuPG6ZU1uK/VKS2hgWk7WtCn0 tyjrc/ByWNZTjlU+ZONvqCx+MqvO9S5qHcMdJENoGRY8UcftoASoI94PJXa0NjeZYZeP q5OHEtMU4LWQO1Yn5KTSsYxTGojU3hFHfXmgy1tUzBR7V5T2cBq28y+17bxQz1MpajHt rQ+Fyfqf3NSlRVSWxnM2YcQfARj30U4i46P0oa0yb/naZh4vnAhyIP43zcyCQsN/wzHR ZJ4w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=FbYFAkTB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id nq4si2992839ejb.68.2021.01.07.14.58.01; Thu, 07 Jan 2021 14:58:24 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=FbYFAkTB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728417AbhAGWyO (ORCPT + 99 others); Thu, 7 Jan 2021 17:54:14 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:36374 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726326AbhAGWyO (ORCPT ); Thu, 7 Jan 2021 17:54:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1610059967; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FefrCvtgHc4zx+jKJhsVluNmZv/u7VtNXp1c2c2tpc4=; b=FbYFAkTBTIZRhHwHtwlDNwddQFOgIqcC/lTqBZJgEgU1UnAkHCEKfPabZptZasR4AsuMYN CGMDGmtg0dPv3xZukBQOw9QS26sksdNxFCsjCWOhbDnjB9lUXXd31qu87AuAZbeO/ojICt hwEiinqRsgB9jytMDQfvjY8HshAxo9U= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-285-MtT76RcbMyuca4BFfM9JkQ-1; Thu, 07 Jan 2021 17:52:43 -0500 X-MC-Unique: MtT76RcbMyuca4BFfM9JkQ-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 7550C80362F; Thu, 7 Jan 2021 22:52:39 +0000 (UTC) Received: from Ruby.redhat.com (ovpn-118-135.rdu2.redhat.com [10.10.118.135]) by smtp.corp.redhat.com (Postfix) with ESMTP id 22D115B4BD; Thu, 7 Jan 2021 22:52:38 +0000 (UTC) From: Lyude Paul To: intel-gfx@lists.freedesktop.org Cc: Jani Nikula , thaytan@noraisin.net, Vasily Khoruzhick , Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , David Airlie , Daniel Vetter , Juha-Pekka Heikkila , =?UTF-8?q?Ville=20Syrj=C3=A4l=C3=A4?= , Sean Paul , dri-devel@lists.freedesktop.org (open list:DRM DRIVERS), linux-kernel@vger.kernel.org (open list) Subject: [PATCH v5 3/4] drm/i915/dp: Allow forcing specific interfaces through enable_dpcd_backlight Date: Thu, 7 Jan 2021 17:52:06 -0500 Message-Id: <20210107225207.28091-4-lyude@redhat.com> In-Reply-To: <20210107225207.28091-1-lyude@redhat.com> References: <20210107225207.28091-1-lyude@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Since we now support controlling panel backlights through DPCD using both the standard VESA interface, and Intel's proprietary HDR backlight interface, we should allow the user to be able to explicitly choose between one or the other in the event that we're wrong about panels reliably reporting support for the Intel HDR interface. So, this commit adds support for this by introducing two new enable_dpcd_backlight options: 2 which forces i915 to only probe for the VESA interface, and 3 which forces i915 to only probe for the Intel backlight interface (might be useful if we find panels in the wild that report the VESA interface in their VBT, but actually only support the Intel backlight interface). v3: * Rebase Signed-off-by: Lyude Paul Reviewed-by: Jani Nikula Cc: thaytan@noraisin.net Cc: Vasily Khoruzhick --- .../drm/i915/display/intel_dp_aux_backlight.c | 45 +++++++++++++++++-- drivers/gpu/drm/i915/i915_params.c | 2 +- 2 files changed, 43 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c index 5e761fb49a14..4b2cb20b1f94 100644 --- a/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c +++ b/drivers/gpu/drm/i915/display/intel_dp_aux_backlight.c @@ -613,15 +613,54 @@ static const struct intel_panel_bl_funcs intel_dp_vesa_bl_funcs = { .get = intel_dp_aux_vesa_get_backlight, }; +enum intel_dp_aux_backlight_modparam { + INTEL_DP_AUX_BACKLIGHT_AUTO = -1, + INTEL_DP_AUX_BACKLIGHT_OFF = 0, + INTEL_DP_AUX_BACKLIGHT_ON = 1, + INTEL_DP_AUX_BACKLIGHT_FORCE_VESA = 2, + INTEL_DP_AUX_BACKLIGHT_FORCE_INTEL = 3, +}; + int intel_dp_aux_init_backlight_funcs(struct intel_connector *connector) { struct drm_device *dev = connector->base.dev; struct intel_panel *panel = &connector->panel; struct intel_dp *intel_dp = enc_to_intel_dp(connector->encoder); struct drm_i915_private *i915 = dp_to_i915(intel_dp); + bool try_intel_interface = false, try_vesa_interface = false; - if (i915->params.enable_dpcd_backlight == 0) + /* Check the VBT and user's module parameters to figure out which + * interfaces to probe + */ + switch (i915->params.enable_dpcd_backlight) { + case INTEL_DP_AUX_BACKLIGHT_OFF: return -ENODEV; + case INTEL_DP_AUX_BACKLIGHT_AUTO: + switch (i915->vbt.backlight.type) { + case INTEL_BACKLIGHT_VESA_EDP_AUX_INTERFACE: + try_vesa_interface = true; + break; + case INTEL_BACKLIGHT_DISPLAY_DDI: + try_intel_interface = true; + try_vesa_interface = true; + break; + default: + return -ENODEV; + } + break; + case INTEL_DP_AUX_BACKLIGHT_ON: + if (i915->vbt.backlight.type != INTEL_BACKLIGHT_VESA_EDP_AUX_INTERFACE) + try_intel_interface = true; + + try_vesa_interface = true; + break; + case INTEL_DP_AUX_BACKLIGHT_FORCE_VESA: + try_vesa_interface = true; + break; + case INTEL_DP_AUX_BACKLIGHT_FORCE_INTEL: + try_intel_interface = true; + break; + } /* * A lot of eDP panels in the wild will report supporting both the @@ -630,13 +669,13 @@ int intel_dp_aux_init_backlight_funcs(struct intel_connector *connector) * and will only work with the Intel interface. So, always probe for * that first. */ - if (intel_dp_aux_supports_hdr_backlight(connector)) { + if (try_intel_interface && intel_dp_aux_supports_hdr_backlight(connector)) { drm_dbg_kms(dev, "Using Intel proprietary eDP backlight controls\n"); panel->backlight.funcs = &intel_dp_hdr_bl_funcs; return 0; } - if (intel_dp_aux_supports_vesa_backlight(connector)) { + if (try_vesa_interface && intel_dp_aux_supports_vesa_backlight(connector)) { drm_dbg_kms(dev, "Using VESA eDP backlight controls\n"); panel->backlight.funcs = &intel_dp_vesa_bl_funcs; return 0; diff --git a/drivers/gpu/drm/i915/i915_params.c b/drivers/gpu/drm/i915/i915_params.c index 7f139ea4a90b..6939634e56ed 100644 --- a/drivers/gpu/drm/i915/i915_params.c +++ b/drivers/gpu/drm/i915/i915_params.c @@ -185,7 +185,7 @@ i915_param_named_unsafe(inject_probe_failure, uint, 0400, i915_param_named(enable_dpcd_backlight, int, 0400, "Enable support for DPCD backlight control" - "(-1=use per-VBT LFP backlight type setting [default], 0=disabled, 1=enabled)"); + "(-1=use per-VBT LFP backlight type setting [default], 0=disabled, 1=enable, 2=force VESA interface, 3=force Intel interface)"); #if IS_ENABLED(CONFIG_DRM_I915_GVT) i915_param_named(enable_gvt, bool, 0400, -- 2.29.2