Received: by 10.192.165.148 with SMTP id m20csp1613612imm; Thu, 3 May 2018 02:25:30 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpBH2yolEbZHYZ46zux7a5/ZSmuDPnXvUMecEtfv85V4zOd4wJRi2CiWjih8arQ0ecc00Cs X-Received: by 10.98.100.2 with SMTP id y2mr9263519pfb.71.1525339530274; Thu, 03 May 2018 02:25:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525339530; cv=none; d=google.com; s=arc-20160816; b=X/THvzWl6oTOigGnRjNnBGW0zCb6LkArqFYRGZZpfmBUVgqv8xb9k+exW6LzvAU2Eg Yj55bbkNHI9YIs+2/lzUHY1wSA9SWmv42brmXvUpOj9fm1MLzBGRRuQeIdxWLBy2XyXq cdyQjT9zexhDXa/JLidxo7UQW5zrX2fFsA8WZbaffYCQkEFoQspVtqldH54AJ3CaXC/O DFY/AQiCQMukGXq4xkKdcLYcSXzu/3FBMIbauhWAoScxJsQREh0GHtAU8leDvBwRXS6f pcGq13mQSo4EHZjjthh50JbykX/QfhP8ymXIYikt4dPOuApYGy1/D0bN+GfDdhhi9Ak9 zYXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=Ht2nbqfatqmbZQhP+Dc3uANm3nr3vjmxEvKEDIgaeOA=; b=1CIIN0pZ/yPmbV+Pf2NueCu6bwUBRQIwyRbsNKQqbHnNdgNf4KA6DaSe136a8qZDXY MyH8ssNpZJp9U+cqV+OaIkkifWxE/T6XmCI4He+LQL4+xVyR4ffy74DhplsiBE4IVbWU fO8dmhmJUVQEfRyWkKRiUZBHf/hNgqjeRZH2j8TNOYgvgXuG+CXfX8U5acyTFAQMJvfa 4gDzAgUjmtZFVTjWItJlmn5e92T9r2Mos2KTCaDotpyKvzYOM/KWCyec26hNTOw5GED0 D9ci3CoLOA+JbYmOwQp8aFDv3mH2LrDLJPsIo+LM5ZVaWId52Y0OygvnhDq7xMP8rWUu 6oNA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@ffwll.ch header.s=google header.b=VbopN+Jo; 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 f1-v6si10144565pgq.590.2018.05.03.02.25.15; Thu, 03 May 2018 02:25:30 -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; dkim=fail header.i=@ffwll.ch header.s=google header.b=VbopN+Jo; 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 S1751174AbeECJZE (ORCPT + 99 others); Thu, 3 May 2018 05:25:04 -0400 Received: from mail-wm0-f51.google.com ([74.125.82.51]:35827 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750945AbeECJZC (ORCPT ); Thu, 3 May 2018 05:25:02 -0400 Received: by mail-wm0-f51.google.com with SMTP id o78so29131544wmg.0 for ; Thu, 03 May 2018 02:25:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=Ht2nbqfatqmbZQhP+Dc3uANm3nr3vjmxEvKEDIgaeOA=; b=VbopN+Jo2qnGSo33/kp/cgCvGVhj/O8XRGXwdQk9N3DGXXYPtbdUtjWlZet05ASgf4 +vsuN0ar4RgbXe/1pKqS1k/1tv4tMTooGToHhcj719Ua6rnBsGYfNuHlMKiwwTzHaUCq 998nF+q7PxuMW7U1SMq02BV4RuHQnVBVM/qqs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=Ht2nbqfatqmbZQhP+Dc3uANm3nr3vjmxEvKEDIgaeOA=; b=c6FbIRxKrSwGAH16HRyXW9JD6d7blmWimsUj1Y+Rra8m4LEGm7maX4Hq5cim5DjR/o 9P8ThEUmbylcNCwy/aEGfcTah294yCVCT/Y2gH077khPxSYrZRciT2DHD2Ag22iTCCJK 3Z0VoJsrcPgRxJ7BErSelrRwRge97k/zHUB7ubacRsHNnZqBn/WyBLIz2UDptLvkyBjJ MpOPCGIxOL1RDyMURsqLJZr4rxbicJiK+ziEnTyBnBYrC3oGChGKji95fiirRXtVmPjr 0TJ+54wALAuKgfSLWJDqGYo07AqRm4Ugs5ElUTo4S76TcZQF3tCisMX2rBbp+9zvL3nr vBtQ== X-Gm-Message-State: ALQs6tCBzTxICQyOqu9noHbhg067RscXHOwugSUNQRcazJbdmzqahaCy GL3PKUq0quSfqB82ouQHb+h3ag== X-Received: by 2002:a50:a845:: with SMTP id j63-v6mr30184546edc.210.1525339501643; Thu, 03 May 2018 02:25:01 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:5635:0:39d2:f87e:2033:9f6]) by smtp.gmail.com with ESMTPSA id e24-v6sm7812738edc.80.2018.05.03.02.25.00 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 03 May 2018 02:25:00 -0700 (PDT) Date: Thu, 3 May 2018 11:24:59 +0200 From: Daniel Vetter To: Satendra Singh Thakur Cc: Gustavo Padovan , Maarten Lankhorst , Sean Paul , David Airlie , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Hemanshu Srivastava , Madhur Verma Subject: Re: [PATCH] drm/atomic: Handling the case when setting old crtc for plane Message-ID: <20180503092458.GH12521@phenom.ffwll.local> Mail-Followup-To: Satendra Singh Thakur , Gustavo Padovan , Maarten Lankhorst , Sean Paul , David Airlie , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Hemanshu Srivastava , Madhur Verma References: <1525326572-25854-1-git-send-email-satendra.t@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1525326572-25854-1-git-send-email-satendra.t@samsung.com> X-Operating-System: Linux phenom 4.15.0-3-amd64 User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 03, 2018 at 11:19:32AM +0530, Satendra Singh Thakur wrote: > In the func drm_atomic_set_crtc_for_plane, with the current code, > if crtc of the plane_state and crtc passed as argument to the func > are same, entire func will executed in vein. > It will get state of crtc and clear and set the bits in plane_mask. > All these steps are not required for same old crtc. > Ideally, we should do nothing in this case, this patch handles the same, > and causes the program to return without doing anything in such scenario. > > Signed-off-by: Satendra Singh Thakur > Cc: Madhur Verma > Cc: Hemanshu Srivastava > --- > drivers/gpu/drm/drm_atomic.c | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c > index 7d25c42..5bd3365 100644 > --- a/drivers/gpu/drm/drm_atomic.c > +++ b/drivers/gpu/drm/drm_atomic.c > @@ -1421,7 +1421,9 @@ drm_atomic_set_crtc_for_plane(struct drm_plane_state *plane_state, > { > struct drm_plane *plane = plane_state->plane; > struct drm_crtc_state *crtc_state; > - > + /* Nothing to do for same crtc*/ > + if (plane_state->crtc == crtc) > + return 0; I didn't do this (both here and in the set_crtc_for_connector functions) because the overhead is probably way down in the noise compared to the overall atomic commit machinery. Do you really see this as a hotpath? -Daniel > if (plane_state->crtc) { > crtc_state = drm_atomic_get_crtc_state(plane_state->state, > plane_state->crtc); > -- > 2.7.4 > > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch