RE: [PATCH] drm/i915: rename intel_gsc to intel_heci_gsc

2022-11-18 Thread Winkler, Tomas
> > > On 11/3/2022 3:41 AM, Winkler, Tomas wrote: > >> Starting on MTL, the GSC FW is loaded at runtime and will be managed > >> directly by i915. This means we now have a naming clash around the > >> GSC, as we have 2 different aspects of it that we need to handle: the > >> HECI interfaces we e

Re: [PATCH] drm/i915: rename intel_gsc to intel_heci_gsc

2022-11-17 Thread Ceraolo Spurio, Daniele
On 11/3/2022 3:41 AM, Winkler, Tomas wrote: Starting on MTL, the GSC FW is loaded at runtime and will be managed directly by i915. This means we now have a naming clash around the GSC, as we have 2 different aspects of it that we need to handle: the HECI interfaces we export pre-mtl and the ne

RE: [PATCH] drm/i915: rename intel_gsc to intel_heci_gsc

2022-11-03 Thread Winkler, Tomas
> > Starting on MTL, the GSC FW is loaded at runtime and will be managed > directly by i915. This means we now have a naming clash around the GSC, as > we have 2 different aspects of it that we need to handle: the HECI interfaces > we export pre-mtl and the new full FW loading and support we have

[PATCH] drm/i915: rename intel_gsc to intel_heci_gsc

2022-11-02 Thread Daniele Ceraolo Spurio
Starting on MTL, the GSC FW is loaded at runtime and will be managed directly by i915. This means we now have a naming clash around the GSC, as we have 2 different aspects of it that we need to handle: the HECI interfaces we export pre-mtl and the new full FW loading and support we have to introduc