diff options
author | Peter Maydell <peter.maydell@linaro.org> | 2024-04-12 17:08:04 +0100 |
---|---|---|
committer | Peter Maydell <peter.maydell@linaro.org> | 2024-04-25 10:21:06 +0100 |
commit | 1e0f2b38ac104ec3606750cce847cc9d8e4f66ac (patch) | |
tree | a71e4bc64668da22cfe27c4c629124f368d7c578 /hw/misc/macio/cuda.c | |
parent | a6819c1bd0b76d7fa0c8f4ae19e4e80dd61a1502 (diff) | |
download | qemu-1e0f2b38ac104ec3606750cce847cc9d8e4f66ac.zip qemu-1e0f2b38ac104ec3606750cce847cc9d8e4f66ac.tar.gz qemu-1e0f2b38ac104ec3606750cce847cc9d8e4f66ac.tar.bz2 |
hw/misc: Don't special case RESET_TYPE_COLD in npcm7xx_clk, gcr
The npcm7xx_clk and npcm7xx_gcr device reset methods look at
the ResetType argument and only handle RESET_TYPE_COLD,
producing a warning if another reset type is passed. This
is different from how every other three-phase-reset method
we have works, and makes it difficult to add new reset types.
A better pattern is "assume that any reset type you don't know
about should be handled like RESET_TYPE_COLD"; switch these
devices to do that. Then adding a new reset type will only
need to touch those devices where its behaviour really needs
to be different from the standard cold reset.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Luc Michel <luc.michel@amd.com>
Message-id: 20240412160809.1260625-2-peter.maydell@linaro.org
Diffstat (limited to 'hw/misc/macio/cuda.c')
0 files changed, 0 insertions, 0 deletions