Received: by 2002:a05:6a10:d5a5:0:0:0:0 with SMTP id gn37csp688002pxb; Wed, 6 Oct 2021 13:16:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy1aehzCWPQcgJ3gzNloHK24sq4w6MXsrcAv+v3+eWaMRBaID0mOM+zH4xGr3FhQhCaxAZX X-Received: by 2002:a17:90b:4a92:: with SMTP id lp18mr186970pjb.47.1633551383791; Wed, 06 Oct 2021 13:16:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633551383; cv=none; d=google.com; s=arc-20160816; b=1D1py+k8l9Wcti8WcY6LAwC3RJ7l34GTwdlGFpH5q3vliFNWybam1OmUh3VfvLNGaS VlzfT+Fst7e2+ShjnunCB3/kKS2ke16/+n/wta0OBNSBEDExjW6tN1/AOaWAEQ3i6KBv Z1t0ZpYm5iNEVbIyt9wlhzblUJmx2+InXIiWEiT5oCmBMKDRspRKDP6ts0c+B91bPWkl o+qqkjoa9NUzMuq4FAKMsYZtvntp3/pn5yAeBW0uwFDHCeW2URcTysNjC134GuUDxvxA cq88KHxoIZd6kUiR4301cRXYKPXZyYA18iJmrf5RSYaDAY7kN7spdYfnm4r1R184sSnr 8h+Q== 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 :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id:dkim-signature; bh=cagY2D5F5NT1bAs4th+N+T0RHoiMV1A9dmi9z8s6Y24=; b=t8fJqs0Uc414kGRZ6yaFuK1sUl13+7/A2VXhRicDoxtSKxmIrQF4+tcYY63++Onk5U a1V16eaCmEKBKgfbCkLyMTYcxlPELM2/kHfCHVcODwnzNlCKozNR7QMseJyU3Aixg3b8 95W5ijC/M5U78BWAw7bub/QygkWQNN74m5ewEiIkAVHYfWrgkLS3Zb5y5CRvQ/7uZ6Za KSYbSA+IbBMGKL8C0XPno4ckncDj/f5G9mbP6ps5p2KBqrx8xIeG5LNfD2IZj5goSkpH vD8ToK1C8BaFcyOo4n+SHt4eea2n5E+6oJfuui2S4ErmyEochpY/9hkwTVb8AIl68reY MP7A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Bu57G9g2; 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 n13si28561665pgq.327.2021.10.06.13.16.08; Wed, 06 Oct 2021 13:16:23 -0700 (PDT) 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=Bu57G9g2; 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 S239370AbhJFUQ2 (ORCPT + 99 others); Wed, 6 Oct 2021 16:16:28 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:58914 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232147AbhJFUQ1 (ORCPT ); Wed, 6 Oct 2021 16:16:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1633551274; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cagY2D5F5NT1bAs4th+N+T0RHoiMV1A9dmi9z8s6Y24=; b=Bu57G9g2BoDNCTguojI0BqG5BF0JykGZ7oM7c4anKJ4vt/2XanGU4ZfcqZWC1Y1K5Igeel ItvlRZoa60+PMiOzE5Yz6sx3DCFTC0++wd6i2b29qay01GtCuna1TlnTy6y626DyvzbmUr MUodZhwXTyD/XbG7hQYVqGo55x+cHcM= Received: from mail-qt1-f199.google.com (mail-qt1-f199.google.com [209.85.160.199]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-263-cS_sHWARNyCVPj1emB06tw-1; Wed, 06 Oct 2021 16:14:33 -0400 X-MC-Unique: cS_sHWARNyCVPj1emB06tw-1 Received: by mail-qt1-f199.google.com with SMTP id x6-20020ac81206000000b002a6e46bbd0eso3139213qti.12 for ; Wed, 06 Oct 2021 13:14:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:organization:user-agent:mime-version :content-transfer-encoding; bh=cagY2D5F5NT1bAs4th+N+T0RHoiMV1A9dmi9z8s6Y24=; b=sDGhjJW5YJhGSjrOaJohjf13hAcKvhLfwWFsXnA3oR3PgjR44UmpDtSjBKusefenoI ndRG8GQ/idBitc/iuewxvyVk8NU6qPoUmrnORy23MrEMyH63NmittE4phvienepOpgfZ J+tejK2PLsb5j5ytqoeKO2QqDBd6AjLfPQAcTGfb/h+2RiS2mM1TSEVvjIInIl8Da0kP 5aQKtcAQ30CfhWm/8FgN5Mz5qPrfoOvsrbKNvfZPxHjWmmRfbtBktdlEpARMhsLJoQIT ocbGyaRUMCmmFKKyO7vTdxWudZ8RVkG4jJUhHj4QcmxJVMnxRzQYs/d6DNy4zcZgE7uM kZ7A== X-Gm-Message-State: AOAM5329symS2cG6GUHaOQTG+CGAt37qSOdhYEJnp/QSkrvsm8dYIEL+ yrWSUq//F5bY3aPzrD5XY+QZh4ZhZ7aB2le9O5Ropn9Gvb3C4u2yr7juDK0xRbc5+5cUigZsCeR UzDJuAokXw2hoTm5zt2ATomJD X-Received: by 2002:a37:2e03:: with SMTP id u3mr104144qkh.313.1633551273155; Wed, 06 Oct 2021 13:14:33 -0700 (PDT) X-Received: by 2002:a37:2e03:: with SMTP id u3mr104131qkh.313.1633551272978; Wed, 06 Oct 2021 13:14:32 -0700 (PDT) Received: from [192.168.8.206] (pool-96-230-249-157.bstnma.fios.verizon.net. [96.230.249.157]) by smtp.gmail.com with ESMTPSA id h17sm13302582qtp.13.2021.10.06.13.14.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 06 Oct 2021 13:14:32 -0700 (PDT) Message-ID: Subject: Re: [Nouveau] [PATCH v3 2/5] drm/nouveau/kms/nv50-: Explicitly check DPCD backlights for aux enable/brightness From: Lyude Paul To: Karol Herbst Cc: Intel Graphics Development , dri-devel , nouveau , Ben Skeggs , David Airlie , Daniel Vetter , open list Date: Wed, 06 Oct 2021 16:14:31 -0400 In-Reply-To: References: <20211006024018.320394-1-lyude@redhat.com> <20211006024018.320394-3-lyude@redhat.com> Organization: Red Hat Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-1.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2021-10-06 at 18:30 +0200, Karol Herbst wrote: > On Wed, Oct 6, 2021 at 4:41 AM Lyude Paul wrote: > > > > Since we don't support hybrid AUX/PWM backlights in nouveau right now, > > let's add some explicit checks so that we don't break nouveau once we > > enable support for these backlights in other drivers. > > > > Signed-off-by: Lyude Paul > > --- > >  drivers/gpu/drm/nouveau/nouveau_backlight.c | 5 ++++- > >  1 file changed, 4 insertions(+), 1 deletion(-) > > > > diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c > > b/drivers/gpu/drm/nouveau/nouveau_backlight.c > > index 1cbd71abc80a..ae2f2abc8f5a 100644 > > --- a/drivers/gpu/drm/nouveau/nouveau_backlight.c > > +++ b/drivers/gpu/drm/nouveau/nouveau_backlight.c > > @@ -308,7 +308,10 @@ nv50_backlight_init(struct nouveau_backlight *bl, > >                 if (ret < 0) > >                         return ret; > > > > -               if (drm_edp_backlight_supported(edp_dpcd)) { > > +               /* TODO: Add support for hybrid PWM/DPCD panels */ > > +               if (drm_edp_backlight_supported(edp_dpcd) && > > +                   (edp_dpcd[1] & DP_EDP_BACKLIGHT_AUX_ENABLE_CAP) && > > where does the DP_EDP_BACKLIGHT_AUX_ENABLE_CAP come from? afaik > drm_edp_backlight_supported checks for > DP_EDP_BACKLIGHT_BRIGHTNESS_AUX_SET_CAP and > DP_EDP_TCON_BACKLIGHT_ADJUSTMENT_CAP so wondering if this was > intentional or a typo This is intentional - drm_edp_backlight_supported() does check for these, but in the patch after this we remove the BRIGHTNESS_AUX_SET_CAP from drm_edp_backlight_supported() in order to implement support for panels lacking BRIGHTNESS_AUX_SET_CAP in i915. Since we don't have support for this in nouveau yet but such backlights are likely to mostly work without the use of DPCD if we avoid trying to set it up, this patch is just here to make sure that the changes to drm_edp_backlight_supported() don't result in nouveau suddenly trying (and failing) to enable DPCD backlight controls on those backlights. > > > +                   (edp_dpcd[2] & > > DP_EDP_BACKLIGHT_BRIGHTNESS_AUX_SET_CAP)) { > >                         NV_DEBUG(drm, "DPCD backlight controls supported > > on %s\n", > >                                  nv_conn->base.name); > > > > -- > > 2.31.1 > > > -- Cheers, Lyude Paul (she/her) Software Engineer at Red Hat