From: Arnaud Minier <arnaud.minier@telecom-paris.fr>
To: qemu-devel@nongnu.org
Subject: Questions about clocks emulation
Date: Tue, 12 Dec 2023 14:05:00 +0100 (CET) [thread overview]
Message-ID: <1001572703.6422667.1702386300513.JavaMail.zimbra@enst.fr> (raw)
Hi all,
I tried to implement the RCC (Reset and Clock Control) for the STM32L4x5_SoC but ran into some problems regarding clock emulation in Qemu.
In this SoC, it is possible to change the source of several clocks used for devices like the CPU, the USART, and approximately every other device on the SoC.
This change can be made at runtime by writing into a specific register.
I tried to model this by using the clocks in hw/core/clock.c by I noticed that it is not possible to change a clock's source once it has been assigned (see clock_set_source()).
It prevents me from implementing a clock tree similar to the one on the hardware.
Is this limitation there for some reason or has it simply not been implemented?
Thanks,
Arnaud Minier
next reply other threads:[~2023-12-12 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 13:05 Arnaud Minier [this message]
2023-12-13 19:13 ` Questions about clocks emulation Philippe Mathieu-Daudé
2023-12-14 7:45 ` Luc Michel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1001572703.6422667.1702386300513.JavaMail.zimbra@enst.fr \
--to=arnaud.minier@telecom-paris.fr \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).