From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wilson Subject: Re: RFC: i915 arch changes to better support new chipsets Date: Wed, 21 Mar 2012 11:58:15 +0000 Message-ID: References: <20120320111357.56093868@jbarnes-desktop> <20120320184304.GC27231@phenom.ffwll.local> <20120320131347.10427988@jbarnes-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by gabe.freedesktop.org (Postfix) with ESMTP id 53D429E927 for ; Wed, 21 Mar 2012 04:58:18 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: Eugeni Dodonov , Jesse Barnes Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Wed, 21 Mar 2012 08:42:37 -0300, Eugeni Dodonov wrote: > I was also thinking on adding a intel_workarounds.c for handling all the > W/As we have in one place, and having some support for calling them via > callbacks to run specific WAs during the modeset, after suspend/resume > cycle and so on. Too much midlayer. The recipe for modesetting for a particular chipset goes in e.g. intel_display_pch_ibx.c and that recipe includes the w/a with the calls to common code in intel_display_pch.c and beyond. (It should ideally be a straight lift out of the bspec of the modesetting sequence.) Not the other way around. Otherwise you just have the same tangle of code just split over many different files and the coupling masked through complex assemblages of vtables. -Chris -- Chris Wilson, Intel Open Source Technology Centre