From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Siluvery, Arun" <arun.siluvery@linux.intel.com>
Subject: Re: WAs in init_clock_gating?
Date: Thu, 24 Jul 2014 11:43:11 +0100
Message-ID: <53D0E33F.4090705@linux.intel.com>
References: <92648605EABDA246B775AAB04C95A7A3137EB57C@IRSMSX103.ger.corp.intel.com>
 <20140707205008.GD17271@phenom.ffwll.local>
 <20140707141641.44e7c407@jbarnes-desktop>
 <CAKMK7uGW3hOfe+KMtN7WCPUyRPqTZi3VYBBgB0x3vOFxmD7tZw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93])
 by gabe.freedesktop.org (Postfix) with ESMTP id 9CAD26E0F2
 for <Intel-gfx@lists.freedesktop.org>; Thu, 24 Jul 2014 03:43:24 -0700 (PDT)
In-Reply-To: <CAKMK7uGW3hOfe+KMtN7WCPUyRPqTZi3VYBBgB0x3vOFxmD7tZw@mail.gmail.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Errors-To: intel-gfx-bounces@lists.freedesktop.org
Sender: "Intel-gfx" <intel-gfx-bounces@lists.freedesktop.org>
To: Daniel Vetter <daniel@ffwll.ch>, Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Intel-gfx@lists.freedesktop.org" <Intel-gfx@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org

On 07/07/2014 22:24, Daniel Vetter wrote:
> On Mon, Jul 7, 2014 at 11:16 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>> I don't think it's unreasonable to use a macro that checks a global
>> list for whether to apply a given WA.  They'll be scattered all over,
>> but at least it'll be easy to see:
>>    1) whether we implement a given workaround
>> and
>>    2) which platforms & steppings it applies to based on the table.
>
> Oh, I agree it's not unreasonable. But I'm kinda begging for the
> simple solution since months (years?) and haven't gotten it, while
> still getting a steady stream of bug reports and issues. So I've
> readjusted my expectations ;-)
>
> If someone delivers the real deal I'll certainly won't reject it.
> -Daniel
>

I am moving bdw workarounds from clock_gating fn to render ring init fn 
and testing this before and after gpu reset.
One of the workaround is to disable STC optimization, reg CACHE_MODE_1 
bit6 set to 1. I observed that some times after boot this gets reset to 
0 (default value) even after applying workarounds; other than 
workarounds no one else seems to write to this function.
Any ideas about this behaviour?

regards
Arun