summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorAlexandre Courbot <acourbot@nvidia.com>2017-02-23 07:05:27 +0300
committerBen Skeggs <bskeggs@redhat.com>2017-03-07 10:05:13 +0300
commitc93cfe35c4da46502ffb0b8a9ded3a1f1a819b9d (patch)
tree109194ed46432d0e05da6f071df129188f4682e8 /tools/perf/scripts/python
parent7defd1daacef6bfae5387e95bcd7b57c9183aaf7 (diff)
downloadlinux-c93cfe35c4da46502ffb0b8a9ded3a1f1a819b9d.tar.xz
drm/nouveau/secboot: let callers interpret return value of blobs
Since the HS blobs are provided and signed by NVIDIA, we cannot expect always-consistent behavior. In this case, on GP10x the unload blob may return 0x1d even though things have run perfectly well. This behavior has been confirmed by NVIDIA. So let the callers of the run_blob() hook receive the blob return's value (a positive integer) and decide what it means. This allows us to workaround the 0x1d code instead of issuing an error. Signed-off-by: Alexandre Courbot <acourbot@nvidia.com> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions