next-cube: use named gpio output for next-rtc data
authorMark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Sun, 22 Dec 2024 13:00:07 +0000 (13:00 +0000)
committerThomas Huth <huth@tuxfamily.org>
Sun, 29 Dec 2024 06:13:47 +0000 (07:13 +0100)
commit44df9533686fcc8899b45120b0dc8d676b57c616
tree6e1829ab2509c10c2e62d6437ae1c37fa1f3e7df
parent4387e938f4eb66515ae9a240522d5c77825e51b1
next-cube: use named gpio output for next-rtc data

Add a named gpio output for the next-rtc data and then update
next_rtc_data_in_irq() to drive the IRQ directly. This enables the next-rtc to
next-pc data to be wired up using the standard qdev gpio APIs.

At the same time rename the pc-rtc-data-in gpio to rtc-data-in which is possible
now that the previous rtc-data-in gpio has been moved to the next-rtc device.

Signed-off-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Message-ID: <20241222130012.1013374-29-mark.cave-ayland@ilande.co.uk>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Thomas Huth <huth@tuxfamily.org>
hw/m68k/next-cube.c