Received: by 10.213.65.68 with SMTP id h4csp3008479imn; Mon, 2 Apr 2018 19:17:40 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+ejfrOI97xa2Ej6eBxbCej3PshCa5lUx2VG5ZECWtPxWtOAQ0l83wUtZ/ieD6URESES6wQ X-Received: by 10.167.128.24 with SMTP id j24mr8962531pfi.91.1522721860615; Mon, 02 Apr 2018 19:17:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522721860; cv=none; d=google.com; s=arc-20160816; b=0tv0mRDF/iKW//W9T+rN82Rzw1SC21h9BPrOvPBevLcg06n+L+jrLysAVkUMjziK1W B4DrKbYVkdCme5Vncud6JkA42TH7S7mrF+6K3kgRhxddaP7/OOqaf9KFrvBURVzDbJds xqveR/3amfFOsqUKO/m8ZmBSRd3/pRP8yGsBVTo1q8XimjU5gu+oJ6C6ArsCnEg7HDSD 1tfwsgs7dAzjs++rJXtu07NMnO85epVeFrIkQhkZfVZsISEK5HZyjwJQOIKaCeoMvUJU HP829vUxNZ9CExMHLwNJ/AtNlOCm9bVXh1OZ5fIKQJ1WXydpBO0dFJJf1uVrKphNZoqG LA+Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=ix/sI/P5C9a9b85In63xD34z8y3xvr8w5b4yPRg97Og=; b=Z2URP+2QZnc/gjl6CRebSDSsvXvImectC6FjaWlqJf/RrtHPSsYPkZhXNif3dsJTVL 1sjIfoZhIjlp38ChkTa9x2DgBiiLpTAUl6VA7OaIHyfT+FxVLRlw5E7CdDaXNqXmGLnh mkCrr8rtFcFSQ0SoCUnwKmZE8w0VFCJ9lhy1+fESLDZfoWG0EY11XSYlL8renPC9AVCk b6tQKrEx/ZkM9mYyiE5k/MWgyRbexRDEabrlHms62/rsKoV7+hgp6D2FZUXm9a5vbmXS 9KHX2i8cRk9GLNWXYxQP/UKEO7xTAqCsx5YtE62aoTIfAPyr3mNnpKbnpHpHt5YyDVzP KuAw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d21-v6si1610486pll.557.2018.04.02.19.17.11; Mon, 02 Apr 2018 19:17:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754743AbeDCCPJ (ORCPT + 99 others); Mon, 2 Apr 2018 22:15:09 -0400 Received: from mail-pl0-f65.google.com ([209.85.160.65]:39649 "EHLO mail-pl0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754722AbeDCCPH (ORCPT ); Mon, 2 Apr 2018 22:15:07 -0400 Received: by mail-pl0-f65.google.com with SMTP id s24-v6so6768418plq.6 for ; Mon, 02 Apr 2018 19:15:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ix/sI/P5C9a9b85In63xD34z8y3xvr8w5b4yPRg97Og=; b=JCbje0e2jy4vaIQTRSZvKVD++tGXOgfNGV/XyPsNS2Ymm0U0Rey6qMcJKNP9jgdi0n pH7CZ6HVJlwrIr9Kcll5qGHVkuu5oVlv5Cv/39VM0uKNR55e2sQOCDRHv4zjsal8Qayf V+6QR99TFTEkrOADY9NvewMMmOIpflzg/F8ZVn0YmNolz3GeHvaI5K1TjmSW/Oyeunx0 d1kDlT06F+8fCM1H+y2SqtoFftS3DBTEbRCehBWpyVJkq4mPDdOPYjRhhMvvhwNNYi3t IdWzDTHjrYFJLPdWBmToc6oBPZyvUERrQYVNGzh3vHU4pfLmA1txkt5YAk8lMu6Dbpcw n4tw== X-Gm-Message-State: AElRT7EiWVNiAjuMTXtAWViOae3MvNZkl9LRS6bGz2JmhjZZ9bnxxoga YrvC3dbwKNKvtTwphPQ7gcB5Axt79hs= X-Received: by 10.167.128.81 with SMTP id y17mr2250974pfm.194.1522721706520; Mon, 02 Apr 2018 19:15:06 -0700 (PDT) Received: from localhost.localdomain ([2601:602:9802:a8dc::19fb]) by smtp.gmail.com with ESMTPSA id m1sm2867100pfi.80.2018.04.02.19.15.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Apr 2018 19:15:05 -0700 (PDT) Subject: Re: [PATCH v2] drm/i915: Keep AUX block running when disabling DPMS for MST To: Lyude Paul , intel-gfx@lists.freedesktop.org Cc: Dhinakaran Pandiyan , =?UTF-8?B?VmlsbGUgU3lyasOkbMOk?= , stable@vger.kernel.org, Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , David Airlie , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org References: <20180402212142.19841-1-lyude@redhat.com> <20180402212617.21247-1-lyude@redhat.com> From: Laura Abbott Message-ID: <89a025ea-b7a2-81f0-7277-341d3c96ebe1@redhat.com> Date: Mon, 2 Apr 2018 19:15:04 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180402212617.21247-1-lyude@redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/02/2018 02:26 PM, Lyude Paul wrote: > While enabling/disabling DPMS before link training with MST hubs is > perfectly valid; unfortunately disabling DPMS results in some devices > disabling their AUX CH block as well. For SST this isn't as much of a > problem, but for MST we need to be able to continue handling aux > transactions even when none of the sinks are turned on since it's > possible for us to have a single atomic commit which results in > disabling each downstream sink, followed by subsequently re-enabling > each sink. > > If we don't do this, we'll end up stalling any pending ESI interrupts > from the sink for up to 1ms. Unfortunately, dropping ESIs during this > timespan makes it so that link fallback retraining for MST (which I will > be submitting to the ML shortly) fails due to the channel EQ failure > interrupts potentially getting dropped. Additionally, when performing a > modeset that brings the hub status's link status from bad -> good having > ESIs disabled for that long causes us to miss the hub's response to us > trying to start link training as well. > > Since any sink with MST is going to support DisplayPort 1.2 anyway, save > us the hassle of trying to wait until the sink comes back up and just > never shut the aux block down. > > Changes since v2: > - Fix patch name, no functional changes > > Signed-off-by: Lyude Paul > Cc: Laura Abbott > Cc: Dhinakaran Pandiyan > Cc: Ville Syrjälä > Cc: stable@vger.kernel.org > Fixes: ad260ab32a4d9 ("drm/i915/dp: Write to SET_POWER dpcd to enable MST hub.") Still able to boot docked and lid closed so Tested-by: Laura Abbott > --- > drivers/gpu/drm/i915/intel_dp.c | 6 ++++-- > 1 file changed, 4 insertions(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c > index 62f82c4298ac..0479c377981b 100644 > --- a/drivers/gpu/drm/i915/intel_dp.c > +++ b/drivers/gpu/drm/i915/intel_dp.c > @@ -2589,11 +2589,13 @@ void intel_dp_sink_dpms(struct intel_dp *intel_dp, int mode) > return; > > if (mode != DRM_MODE_DPMS_ON) { > + unsigned char data = intel_dp->is_mst ? > + DP_SET_POWER_D3_AUX_ON : DP_SET_POWER_D3; > + > if (downstream_hpd_needs_d0(intel_dp)) > return; > > - ret = drm_dp_dpcd_writeb(&intel_dp->aux, DP_SET_POWER, > - DP_SET_POWER_D3); > + ret = drm_dp_dpcd_writeb(&intel_dp->aux, DP_SET_POWER, data); > } else { > struct intel_lspcon *lspcon = dp_to_lspcon(intel_dp); > >