[Intel-gfx] [PATCH] drm/i915/csr: Allow matching unknown HW steppings with generic firmware

Imre Deak imre.deak at intel.com
Mon Mar 7 15:56:15 UTC 2016


On ma, 2016-03-07 at 13:39 +0000, Chris Wilson wrote:
> On Mon, Mar 07, 2016 at 03:12:40PM +0200, Imre Deak wrote:
> > On ma, 2016-03-07 at 12:05 +0000, Chris Wilson wrote:
> > > If the firmware is generic and has a run-anywhere mode, enable it
> > > rather
> > > than completely failing on unknown HW revisions.
> > > Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
> > > Cc: Damien Lespiau <damien.lespiau at intel.com>
> > > Cc: Imre Deak <imre.deak at intel.com>
> > > Cc: Sunil Kamath <sunil.kamath at intel.com>
> > > Cc: Daniel Vetter <daniel.vetter at intel.com>
> > > Cc: Animesh Manna <animesh.manna at intel.com>
> > > Cc: Jani Nikula <jani.nikula at intel.com>
> > 
> > Looks ok:
> > Reviewed-by: Imre Deak <imre.deak at intel.com>
> > 
> > > ---
> > > This is probably stable@ material since it could allow future hw
> > > to
> > > just work.
> > 
> > Existing platforms will select the generic firmware version already if
> > one is provided in the image, this change will just allow us not to
> > provide a stepping info table for new platforms. So not sure why it's
> > @stable material.
> 
> Because we are already hitting the scenario where there are new
> platforms that do not match the hardcoded set of steppings and error out
> i.e. we have failed to futureproof the code.

Ok, I missed the part that this also fixes the fw version selection for
existing platforms with a new stepping. So yes, agreed we need this for
@stable.

--Imre


More information about the Intel-gfx mailing list