drm/nouveau/secboot: lazy-load firmware and be more resilient

Browse source

Defer the loading of firmware files to the chip-specific part of secure
boot. This allows implementations to retry loading firmware if the first
attempt failed ; for the GM200 implementation, this happens when trying
to reset a falcon, typically in reaction to GR init.

Firmware loading may fail for a variety of reasons, such as the
filesystem where they reside not being ready at init time. This new
behavior allows GR to be initialized the next time we try to use it if
the firmware has become available.

Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>

...

This commit is contained in:

Alexandre Courbot 2016-06-08 17:32:41 +09:00 • committed by Ben Skeggs

parent 4f3c15569e

commit 20560a9a3c

4 changed files with 59 additions and 39 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

9

drivers/gpu/drm/nouveau/nvkm/subdev/secboot/base.c

View file

30

drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gm200.c

View file

54

drivers/gpu/drm/nouveau/nvkm/subdev/secboot/gm20b.c

View file

5

drivers/gpu/drm/nouveau/nvkm/subdev/secboot/priv.h

View file