Re: [Intel-gfx] [PATCH 10/19] drm/i915: do not assert DE_PCH_EVENT_IVB enabled

2013-12-10 Thread Daniel Vetter
On Thu, Nov 21, 2013 at 01:47:24PM -0200, Paulo Zanoni wrote: > From: Paulo Zanoni > > The current code was checking if all bits of "val" were enabled and > DE_PCH_EVENT_IVB was disabled. The new code doesn't care about the > state of DE_PCH_EVENT_IVB: it just checks if everything else is 1. > >

Re: [Intel-gfx] [PATCH 10/19] drm/i915: do not assert DE_PCH_EVENT_IVB enabled

2013-11-29 Thread Rodrigo Vivi
Reviewed-by: Rodrigo Vivi On Thu, Nov 21, 2013 at 01:47:24PM -0200, Paulo Zanoni wrote: > From: Paulo Zanoni > > The current code was checking if all bits of "val" were enabled and > DE_PCH_EVENT_IVB was disabled. The new code doesn't care about the > state of DE_PCH_EVENT_IVB: it just checks i

[Intel-gfx] [PATCH 10/19] drm/i915: do not assert DE_PCH_EVENT_IVB enabled

2013-11-21 Thread Paulo Zanoni
From: Paulo Zanoni The current code was checking if all bits of "val" were enabled and DE_PCH_EVENT_IVB was disabled. The new code doesn't care about the state of DE_PCH_EVENT_IVB: it just checks if everything else is 1. The goal is that future patches may completely disable interrupts, and the