[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH RFC 4/4] rtc: Have event RTC_CHANGE identify the RTC by QOM p
From: |
Peter Maydell |
Subject: |
Re: [PATCH RFC 4/4] rtc: Have event RTC_CHANGE identify the RTC by QOM path |
Date: |
Tue, 22 Feb 2022 13:06:09 +0000 |
On Tue, 22 Feb 2022 at 12:56, Philippe Mathieu-Daudé
<philippe.mathieu.daude@gmail.com> wrote:
> On 22/2/22 13:02, Markus Armbruster wrote:
> > Event RTC_CHANGE is "emitted when the guest changes the RTC time" (and
> > the RTC supports the event). What if there's more than one RTC?
>
> w.r.t. RTC, a machine having multiple RTC devices is silly...
I don't think we have any examples in the tree currently, but
I bet real hardware like that does exist: the most plausible
thing would be a board where there's an RTC built into the SoC
but the board designers put an external RTC on the board (perhaps
because it was better/more accurate/easier to make battery-backed).
In fact, here's an old bug report from a user trying to get
their Debian system to use the battery-backed RTC as the
"real" one rather than the non-battery-backed RTC device
that's also part of the arm board they're using:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785445
-- PMM
- [PATCH v2 1/3] qapi: Move RTC_CHANGE back out of target schema, (continued)
- [PATCH v2 1/3] qapi: Move RTC_CHANGE back out of target schema, Peter Maydell, 2022/02/21
- [PATCH v2 2/3] qapi: Document some missing details of RTC_CHANGE event, Peter Maydell, 2022/02/21
- [PATCH v2 3/3] hw/rtc: Compile pl031 once-only, Peter Maydell, 2022/02/21
- Re: [PATCH v2 0/3] qapi: Move RTC_CHANGE back out of target schema, Eric Auger, 2022/02/21
- [PATCH RFC 4/4] rtc: Have event RTC_CHANGE identify the RTC by QOM path, Markus Armbruster, 2022/02/22
- Re: [PATCH RFC 4/4] rtc: Have event RTC_CHANGE identify the RTC by QOM path, Markus Armbruster, 2022/02/23
Re: [PATCH v2 0/3] qapi: Move RTC_CHANGE back out of target schema, Markus Armbruster, 2022/02/25