From: Stephen Boyd <sboyd@kernel.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
linux-kernel@vger.kernel.org
Cc: linux-amarula@amarulasolutions.com,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v4 4/4] clk: stm32f4: support spread spectrum clock generation
Date: Wed, 15 Jan 2025 15:23:09 -0800 [thread overview]
Message-ID: <4af9d643e1f0d3b291d7cbe7445bfd2b.sboyd@kernel.org> (raw)
In-Reply-To: <20250114182021.670435-5-dario.binacchi@amarulasolutions.com>
Quoting Dario Binacchi (2025-01-14 10:19:49)
> Support spread spectrum clock generation for the main PLL, the only one
> for which this functionality is available.
>
> Tested on the STM32F469I-DISCO board.
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
>
> ---
Applied to clk-next
prev parent reply other threads:[~2025-01-15 23:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 18:19 [PATCH v4 0/4] Support spread spectrum clocking for stm32f{4,7} platforms Dario Binacchi
2025-01-14 18:19 ` [PATCH v4 1/4] dt-bindings: clock: convert stm32 rcc bindings to json-schema Dario Binacchi
2025-01-15 23:22 ` Stephen Boyd
2025-01-14 18:19 ` [PATCH v4 2/4] dt-bindings: clock: st,stm32-rcc: support spread spectrum clocking Dario Binacchi
2025-01-15 23:22 ` Stephen Boyd
2025-01-24 13:45 ` Krzysztof Kozlowski
2025-01-25 13:21 ` Dario Binacchi
2025-01-14 18:19 ` [PATCH v4 3/4] clk: stm32f4: use FIELD helpers to access the PLLCFGR fields Dario Binacchi
2025-01-15 23:23 ` Stephen Boyd
2025-01-14 18:19 ` [PATCH v4 4/4] clk: stm32f4: support spread spectrum clock generation Dario Binacchi
2025-01-15 23:23 ` Stephen Boyd [this message]
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=4af9d643e1f0d3b291d7cbe7445bfd2b.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.