Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp803194ybe; Fri, 13 Sep 2019 06:37:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqzD9Ldn3YP6aMP5M/5GzFCVq4GtZzoO7Jh2lGkRUBj0eBqq3HOJ3xPOc/2vW1p9fUaRERK2 X-Received: by 2002:a17:906:e92:: with SMTP id p18mr3759370ejf.308.1568381864714; Fri, 13 Sep 2019 06:37:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568381864; cv=none; d=google.com; s=arc-20160816; b=lRVNlP6U6A4FIbpd7194NbW5cxSwpqm21ZzoI0u7sJfzIWhIlkHFwcmnnQzlbtzPij xob3/voP58v4evx3klrI+JU08Y5BQtU0/1hAS5EVS5ywj1T/yw8hf8NGf7KkLoyismjW SEUo4oqKQ2Tp849sxtZGAzG4+84ihCbgUWQWzK73Bw2kYYLbSscXwCqIr3Ch5fb+5LZo CnUOQvOFefk4ek3P/41B3FtK5CecQ8BgUIAj1gkHAOyWGPmcHMdmNXXcxZ8fhqYI0R8C esdOtFcQK4WxarSdHC8vnjQ61jmvMPZtzNDnfK1rjFFoWYP9bqiEWpq5mDGz1FdT+RA0 p2dg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version; bh=Hnl7OpEfza4YbA2qYO4VUD1uuEgWDd+IAdiDL6hY/pM=; b=MgoqME3MS/a8hLPbTxlZjaI35fXZPaC+Iqo5r4ysz8UnbzqwNtqq7fiRwB2JSQyyp1 35X37VhqcQS1cH64a100i2guKJ4YwGoJxMmJGEHB8kiEHk5m07e6Yp8T5lHzXojllAuq CAjrrOcSo6R6nwzyVf+O7DkVheO5a+dvwYolEdH5kxEZfljmRq8/Uiy0fJu24n4pTLsB XJGt+lldrcpNSMCRFTSid8NlZlZij225glO+Z1UWWQzx5uErYKxc0CVtHwO2SDHG/NMt N4DcR0tA6NzTtfH8dXnBCT7ENRo82XS3CGKTtfLBdxfavmTxeiJeZ+PXjVElbfrDnLGf IsEQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c23si10873818edt.376.2019.09.13.06.37.21; Fri, 13 Sep 2019 06:37:44 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391763AbfIMNdu (ORCPT + 99 others); Fri, 13 Sep 2019 09:33:50 -0400 Received: from mail-vs1-f66.google.com ([209.85.217.66]:42511 "EHLO mail-vs1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388524AbfIMNdt (ORCPT ); Fri, 13 Sep 2019 09:33:49 -0400 Received: by mail-vs1-f66.google.com with SMTP id m22so18586781vsl.9; Fri, 13 Sep 2019 06:33:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Hnl7OpEfza4YbA2qYO4VUD1uuEgWDd+IAdiDL6hY/pM=; b=IofTxCS7lwNQAocatR0C7ZiQ6XGfKbtmTucn1ZRXz9tNVv1mdEnNImBFrovzT4sv0g JIk9w4c6owtM08W0VQUgumkJPpb25IKrmez2gU77KTE1E0UKwLJTbThIMq12FqyEeL67 CPFtFtDQ7Rs55U8hE5dHgidXx1cfABRcAcExlMpmo6csXZ/gsCENd77uYMeoeGJJYWiC UVh48cDhoNTxWrMncsXjNcPjlP0rB/dfFjHsc4xqQI9RcMe6c7VSpLvtQSJUtPw+UDvh qgu7+CHxT/nHUWKlY095X7lIXyDvJ9xK1wp2icCIXIkcSzyBAm1GlX5B4G8sb0I7jWM2 CGfQ== X-Gm-Message-State: APjAAAXvvBtcso/Sz2hoQ9QxRACtG9Z3mKkZsM0daBHX+sqM+6zWffw8 pNH1nN+HGbBxHR+1XhTNcgZeiMYdJ9MJuFCe+DQ= X-Received: by 2002:a67:fd97:: with SMTP id k23mr20291160vsq.220.1568381627687; Fri, 13 Sep 2019 06:33:47 -0700 (PDT) MIME-Version: 1.0 References: <20190913130559.669563815@linuxfoundation.org> <20190913130606.981926197@linuxfoundation.org> In-Reply-To: <20190913130606.981926197@linuxfoundation.org> From: Ilia Mirkin Date: Fri, 13 Sep 2019 09:33:36 -0400 Message-ID: Subject: Re: [PATCH 4.19 092/190] drm/nouveau: Dont WARN_ON VCPI allocation failures To: Greg Kroah-Hartman Cc: LKML , Sasha Levin , dri-devel , Ben Skeggs , nouveau , "# 3.9+" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Greg, This feels like it's missing a From: line. commit b513a18cf1d705bd04efd91c417e79e4938be093 Author: Lyude Paul Date: Mon Jan 28 16:03:50 2019 -0500 drm/nouveau: Don't WARN_ON VCPI allocation failures Is this an artifact of your notification-of-patches process and I never noticed before, or was the patch ingested incorrectly? Cheers, -ilia On Fri, Sep 13, 2019 at 9:16 AM Greg Kroah-Hartman wrote: > > [ Upstream commit b513a18cf1d705bd04efd91c417e79e4938be093 ] > > This is much louder then we want. VCPI allocation failures are quite > normal, since they will happen if any part of the modesetting process is > interrupted by removing the DP MST topology in question. So just print a > debugging message on VCPI failures instead. > > Signed-off-by: Lyude Paul > Fixes: f479c0ba4a17 ("drm/nouveau/kms/nv50: initial support for DP 1.2 multi-stream") > Cc: Ben Skeggs > Cc: dri-devel@lists.freedesktop.org > Cc: nouveau@lists.freedesktop.org > Cc: # v4.10+ > Signed-off-by: Ben Skeggs > Signed-off-by: Sasha Levin > --- > drivers/gpu/drm/nouveau/dispnv50/disp.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/nouveau/dispnv50/disp.c b/drivers/gpu/drm/nouveau/dispnv50/disp.c > index f889d41a281fa..5e01bfb69d7a3 100644 > --- a/drivers/gpu/drm/nouveau/dispnv50/disp.c > +++ b/drivers/gpu/drm/nouveau/dispnv50/disp.c > @@ -759,7 +759,8 @@ nv50_msto_enable(struct drm_encoder *encoder) > > slots = drm_dp_find_vcpi_slots(&mstm->mgr, mstc->pbn); > r = drm_dp_mst_allocate_vcpi(&mstm->mgr, mstc->port, mstc->pbn, slots); > - WARN_ON(!r); > + if (!r) > + DRM_DEBUG_KMS("Failed to allocate VCPI\n"); > > if (!mstm->links++) > nv50_outp_acquire(mstm->outp); > -- > 2.20.1 > > > > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel