From: "Inès Varhol" <ines.varhol@telecom-paris.fr>
To: peter maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Arnaud Minier" <arnaud.minier@telecom-paris.fr>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Luc Michel" <luc@lmichel.fr>, qemu-arm <qemu-arm@nongnu.org>,
"Thomas Huth" <thuth@redhat.com>,
"Samuel Tardieu" <sam@rfc1149.net>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Alistair Francis" <alistair@alistair23.me>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Damien Hedde" <damien.hedde@dahe.fr>,
"Laurent Vivier" <lvivier@redhat.com>
Subject: Re: [PING PATCH v5 3/3] tests/qtest: Check STM32L4x5 clock connections
Date: Tue, 15 Oct 2024 16:34:24 +0200 (CEST) [thread overview]
Message-ID: <698508180.2421226.1729002864954.JavaMail.zimbra@enst.fr> (raw)
In-Reply-To: <CAFEAcA_0eyAa=XjDnobYqkinEnW1wOetKDBqus7k1BTWTyLLpQ@mail.gmail.com>
----- Le 15 Oct 24, à 16:20, peter maydell peter.maydell@linaro.org a écrit :
> On Thu, 3 Oct 2024 at 09:11, Inès Varhol <ines.varhol@telecom-paris.fr> wrote:
>>
>> For USART, GPIO and SYSCFG devices, check that clock frequency before
>> and after enabling the peripheral clock in RCC is correct.
>>
>> Signed-off-by: Inès Varhol <ines.varhol@telecom-paris.fr>
>> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>> Reviewed-by: Luc Michel <luc@lmichel.fr>
>
>
>> +static void test_clock_enable(void)
>> +{
>> + /*
>> + * For each USART device, enable its clock in RCC
>> + * and check that its clock frequency is SYSCLK_PERIOD
>> + */
>> + QTestState *qts = qtest_init("-M b-l475e-iot01a");
>> +
>> + check_clock(qts, "machine/soc/usart[0]/clk", RCC_APB2ENR, 14);
>> + check_clock(qts, "machine/soc/usart[1]/clk", RCC_APB1ENR1, 17);
>> + check_clock(qts, "machine/soc/usart[2]/clk", RCC_APB1ENR1, 18);
>> + check_clock(qts, "machine/soc/uart[0]/clk", RCC_APB1ENR1, 19);
>> + check_clock(qts, "machine/soc/uart[1]/clk", RCC_APB1ENR1, 20);
>> + check_clock(qts, "machine/soc/lpuart1/clk", RCC_APB1ENR2, 0);
>> +}
>
> This new test is missing the qtest_quit(qts) call at the
> end, which makes it hang when run on OpenBSD. (I fixed
> this up in the pullrequest.)
>
> thanks
> -- PMM
Thanks for the fix!
Inès
next prev parent reply other threads:[~2024-10-15 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 8:10 [PING PATCH v5 0/3] Check clock connection between STM32L4x5 RCC and peripherals Inès Varhol
2024-10-03 8:10 ` [PING PATCH v5 1/3] hw/misc: Create STM32L4x5 SYSCFG clock Inès Varhol
2024-10-03 8:10 ` [PING PATCH v5 2/3] hw/clock: Expose 'qtest-clock-period' QOM property for QTests Inès Varhol
2024-10-03 8:10 ` [PING PATCH v5 3/3] tests/qtest: Check STM32L4x5 clock connections Inès Varhol
2024-10-15 14:20 ` Peter Maydell
2024-10-15 14:34 ` Inès Varhol [this message]
2024-10-04 18:23 ` [PING PATCH v5 0/3] Check clock connection between STM32L4x5 RCC and peripherals Peter Maydell
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=698508180.2421226.1729002864954.JavaMail.zimbra@enst.fr \
--to=ines.varhol@telecom-paris.fr \
--cc=alistair@alistair23.me \
--cc=arnaud.minier@telecom-paris.fr \
--cc=damien.hedde@dahe.fr \
--cc=luc@lmichel.fr \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sam@rfc1149.net \
--cc=thuth@redhat.com \
/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).