hw/intc: don't use target_ulong for LoongArch ipi
authorAlex Bennée <alex.bennee@linaro.org>
Tue, 4 Apr 2023 13:27:11 +0000 (14:27 +0100)
committerSong Gao <gaosong@loongson.cn>
Sat, 6 May 2023 03:19:50 +0000 (11:19 +0800)
The calling function is already working with hwaddr and uint64_t so
lets avoid bringing target_ulong in if we don't need to.

Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Song Gao <gaosong@loongson.cn>
Message-Id: <20230404132711.2563638-1-alex.bennee@linaro.org>
Signed-off-by: Song Gao <gaosong@loongson.cn>
hw/intc/loongarch_ipi.c

index aa4bf9eb747bc4bc937d0ec72e1775f70963fd70..bdba0f81072b4189ebdad80bc849c6eb7cf6218e 100644 (file)
@@ -50,7 +50,7 @@ static uint64_t loongarch_ipi_readl(void *opaque, hwaddr addr, unsigned size)
     return ret;
 }
 
-static void send_ipi_data(CPULoongArchState *env, target_ulong val, target_ulong addr)
+static void send_ipi_data(CPULoongArchState *env, uint64_t val, hwaddr addr)
 {
     int i, mask = 0, data = 0;