diff options
author | Peter Maydell <peter.maydell@linaro.org> | 2024-09-13 15:31:45 +0100 |
---|---|---|
committer | Peter Maydell <peter.maydell@linaro.org> | 2024-09-13 15:31:45 +0100 |
commit | b5fe9bf296ea5604a16f6dfb4777bfce56cd48c0 (patch) | |
tree | e778ef304116d69835e18aa3caac846109a152f4 /python/scripts/vendor.py | |
parent | 1000872dde2fc089823df7394ca2c9690734091a (diff) | |
download | qemu-b5fe9bf296ea5604a16f6dfb4777bfce56cd48c0.zip qemu-b5fe9bf296ea5604a16f6dfb4777bfce56cd48c0.tar.gz qemu-b5fe9bf296ea5604a16f6dfb4777bfce56cd48c0.tar.bz2 |
hw: Remove device_phases_reset()
Currently we have transitional machinery between legacy reset
and three phase reset that works in two directions:
* if you invoke three phase reset on a device which has set
the DeviceClass::legacy_reset method, we detect this in
device_get_transitional_reset() and arrange that we call
the legacy_reset method during the hold phase of reset
* if you invoke legacy reset on a device which implements
three phase reset, the default legacy_reset method is
device_phases_reset(), which does a three-phase reset
of the device
However, we have now eliminated all the places which could invoke
legacy reset on a device, which means that the function
device_phases_reset() is never called -- it serves only as the value
of DeviceClass::legacy_reset that indicates that the subclass never
overrode the legacy reset method. So we can delete it, and instead
check for legacy_reset != NULL.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Message-id: 20240830145812.1967042-10-peter.maydell@linaro.org
Diffstat (limited to 'python/scripts/vendor.py')
0 files changed, 0 insertions, 0 deletions