From: Luc Michel <luc@lmichel.fr>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, "Luc Michel" <luc.michel@amd.com>,
"Damien Hedde" <damien.hedde@dahe.fr>,
"Inès Varhol" <ines.varhol@telecom-paris.fr>,
"Arnaud Minier" <arnaud.minier@telecom-paris.fr>,
qemu-arm@nongnu.org
Subject: Re: [PATCH-for-9.0 1/2] hw/clock: Let clock_set_mul_div() return boolean value
Date: Mon, 25 Mar 2024 10:05:47 +0100 [thread overview]
Message-ID: <ZgE-a5z-zCVnxXTy@michell-laptop.localdomain> (raw)
In-Reply-To: <ZgE3fZx7qNkYATms@michell-laptop.localdomain>
On 09:40 Mon 25 Mar , Luc Michel wrote:
> On 16:58 Fri 22 Mar , Philippe Mathieu-Daudé wrote:
> > Let clock_set_mul_div() return a boolean value whether the
> > clock has been updated or not, similarly to clock_set().
> >
> > Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>
> Acked-by: Luc Michel <luc@lmichel.fr>
Sorry, I forgot, as Peter suggested, can you add a word in the doc
about this?
Something in the vein of:
+ Similary to ``clock_set()``, ``clock_set_mul_div()`` returns ``true`` if
+ the clock state was modified, that it, if the multiplier or the diviser
+ or both were changed by the call.
+
Note that ``clock_set_mul_div()`` does not automatically
call ``clock_propagate()``. If you make a runtime change to the
multiplier or divider you must call clock_propagate() yourself.
Thanks!
--
Luc
>
> > ---
> > include/hw/clock.h | 4 +++-
> > hw/core/clock.c | 8 +++++++-
> > 2 files changed, 10 insertions(+), 2 deletions(-)
> >
> > diff --git a/include/hw/clock.h b/include/hw/clock.h
> > index bb12117f67..eb58599131 100644
> > --- a/include/hw/clock.h
> > +++ b/include/hw/clock.h
> > @@ -357,6 +357,8 @@ char *clock_display_freq(Clock *clk);
> > * @multiplier: multiplier value
> > * @divider: divider value
> > *
> > + * @return: true if the clock is changed.
> > + *
> > * By default, a Clock's children will all run with the same period
> > * as their parent. This function allows you to adjust the multiplier
> > * and divider used to derive the child clock frequency.
> > @@ -374,6 +376,6 @@ char *clock_display_freq(Clock *clk);
> > * Note that this function does not call clock_propagate(); the
> > * caller should do that if necessary.
> > */
> > -void clock_set_mul_div(Clock *clk, uint32_t multiplier, uint32_t divider);
> > +bool clock_set_mul_div(Clock *clk, uint32_t multiplier, uint32_t divider);
> >
> > #endif /* QEMU_HW_CLOCK_H */
> > diff --git a/hw/core/clock.c b/hw/core/clock.c
> > index d82e44cd1a..a19c7db7df 100644
> > --- a/hw/core/clock.c
> > +++ b/hw/core/clock.c
> > @@ -143,14 +143,20 @@ char *clock_display_freq(Clock *clk)
> > return freq_to_str(clock_get_hz(clk));
> > }
> >
> > -void clock_set_mul_div(Clock *clk, uint32_t multiplier, uint32_t divider)
> > +bool clock_set_mul_div(Clock *clk, uint32_t multiplier, uint32_t divider)
> > {
> > assert(divider != 0);
> >
> > + if (clk->multiplier == multiplier && clk->divider == divider) {
> > + return false;
> > + }
> > +
> > trace_clock_set_mul_div(CLOCK_PATH(clk), clk->multiplier, multiplier,
> > clk->divider, divider);
> > clk->multiplier = multiplier;
> > clk->divider = divider;
> > +
> > + return true;
> > }
> >
> > static void clock_initfn(Object *obj)
> > --
> > 2.41.0
> >
>
--
next prev parent reply other threads:[~2024-03-25 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 15:58 [PATCH-for-9.0 0/2] hw/clock: Propagate clock changes when STM32L4X5 MUX is updated Philippe Mathieu-Daudé
2024-03-22 15:58 ` [PATCH-for-9.0 1/2] hw/clock: Let clock_set_mul_div() return boolean value Philippe Mathieu-Daudé
2024-03-22 16:40 ` Peter Maydell
2024-03-25 8:40 ` Luc Michel
2024-03-25 9:05 ` Luc Michel [this message]
2024-03-22 15:58 ` [PATCH-for-9.0 2/2] hw/misc/stm32l4x5_rcc: Propagate period when enabling a clock Philippe Mathieu-Daudé
2024-03-22 16:39 ` Peter Maydell
2024-03-25 8:56 ` 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=ZgE-a5z-zCVnxXTy@michell-laptop.localdomain \
--to=luc@lmichel.fr \
--cc=arnaud.minier@telecom-paris.fr \
--cc=damien.hedde@dahe.fr \
--cc=ines.varhol@telecom-paris.fr \
--cc=luc.michel@amd.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).