Re: [Intel-gfx] [PATCH] drm/i915/icl: Use hw engine class, instance to find irq handler

Hi, On 3/12/2018 7:41 AM, Mika Kuoppala wrote: Interrupt identity register we already read from hardware contains engine class and instance fields. Leverage these fields to find correct engine to handle the interrupt. add/remove: 0/0 grow/shrink: 0/1 up/down: 0/-160 (-160) Function

Re: [Intel-gfx] [PATCH] drm/i915/icl: Use hw engine class, instance to find irq handler

On 12/03/18 08:23, Chris Wilson wrote: Quoting Daniele Ceraolo Spurio (2018-03-12 15:09:31) On 12/03/18 07:52, Chris Wilson wrote: Quoting Mika Kuoppala (2018-03-12 14:41:31) Interrupt identity register we already read from hardware contains engine class and instance fields. Leverage

Re: [Intel-gfx] [PATCH] drm/i915/icl: Use hw engine class, instance to find irq handler

Quoting Daniele Ceraolo Spurio (2018-03-12 15:09:31) > > > On 12/03/18 07:52, Chris Wilson wrote: > > Quoting Mika Kuoppala (2018-03-12 14:41:31) > >> Interrupt identity register we already read from hardware > >> contains engine class and instance fields. Leverage > >> these fields to find

Re: [Intel-gfx] [PATCH] drm/i915/icl: Use hw engine class, instance to find irq handler

On 12/03/18 07:52, Chris Wilson wrote: Quoting Mika Kuoppala (2018-03-12 14:41:31) Interrupt identity register we already read from hardware contains engine class and instance fields. Leverage these fields to find correct engine to handle the interrupt. add/remove: 0/0 grow/shrink: 0/1

Re: [Intel-gfx] [PATCH] drm/i915/icl: Use hw engine class, instance to find irq handler

Quoting Mika Kuoppala (2018-03-12 14:41:31) > Interrupt identity register we already read from hardware > contains engine class and instance fields. Leverage > these fields to find correct engine to handle the interrupt. > > add/remove: 0/0 grow/shrink: 0/1 up/down: 0/-160 (-160) > Function