From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesse Barnes Subject: [RFC] async CRTC enable/disable hack Date: Fri, 13 Dec 2013 11:26:51 -0800 Message-ID: <1386962813-2058-1-git-send-email-jbarnes@virtuousgeek.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from alt-proxy6.mail.unifiedlayer.com (alt-proxy6.mail.unifiedlayer.com [66.147.245.65]) by gabe.freedesktop.org (Postfix) with SMTP id 933ACFBB1C for ; Fri, 13 Dec 2013 11:27:01 -0800 (PST) Received: from [67.161.37.189] (port=48333 helo=localhost.localdomain) by box514.bluehost.com with esmtpsa (UNKNOWN:CAMELLIA256-SHA:256) (Exim 4.80) (envelope-from ) id 1VrYO1-000754-Ef for intel-gfx@lists.freedesktop.org; Fri, 13 Dec 2013 12:26:57 -0700 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces@lists.freedesktop.org Errors-To: intel-gfx-bounces@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org Obviously still need a lot of work (and I didn't quite get the patch split correctly, I meant commit the first bits earlier). I think the approach may be sound though, and is actually not too hard to get right with all the cross checking we have in place. Things to fix: - modeset cross check - we don't want to sync after a mode set just to check, maybe we could put this off until the actual enable happens - split flushing of disable and enable to actually make full mode sets fast Anyway this is just a sketch of something we might do, definitely not intended for upstream anytime soon. Thanks, Jesse