diff options
author | Lyude Paul <lyude@redhat.com> | 2020-11-13 19:14:13 -0500 |
---|---|---|
committer | Ben Skeggs <bskeggs@redhat.com> | 2021-01-29 16:49:14 +1000 |
commit | f60f8705fc7b82964339c44aa3a8afd5cf216143 (patch) | |
tree | d35779be9e71693293a0f74040886d43e969053b /tools/perf/scripts/python/export-to-postgresql.py | |
parent | fa9f9489d9f9d787455e827c46a3b1b45d6b37ee (diff) |
drm/nouveau/kms/nv50-: s/armh/asyh/ in nv50_msto_atomic_enable()
I have a strange dejavu feeling that I tried to submit a patch for this in
the past, but that it was rejected. I can't remember though, but I'm
further convinced this patch is the right thing to do anyway.
We label the to-be-committed head state in nv50_msto_atomic_enable() as
armh. Normally armh implies a state which is currently armed in hardware.
nv50_msto_atomic_enable() is called _after_ drm_atomic_swap_state()
however, but before the commit tail ends, which means that said state is
not actually armed on hardware.
As well - take note that this is the same convention followed in all of the
other atomic_enable() callbacks.
So, let's correct this to asyh.
Signed-off-by: Lyude Paul <lyude@redhat.com>
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions