From: Stephen Boyd <sboyd@kernel.org>
To: Dario Binacchi <dariobin@libero.it>, linux-kernel@vger.kernel.org
Cc: "Grygorii Strashko" <grygorii.strashko@ti.com>,
"Dario Binacchi" <dariobin@libero.it>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Lee Jones" <lee.jones@linaro.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Tero Kristo" <kristo@kernel.org>,
"Tony Lindgren" <tony@atomide.com>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: [PATCH v3 0/4] clk: ti: add am33xx spread spectrum clock support
Date: Mon, 29 Mar 2021 19:24:41 -0700 [thread overview]
Message-ID: <161707108197.3012082.13148389244272034996@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <20210329164222.26794-1-dariobin@libero.it>
Quoting Dario Binacchi (2021-03-29 09:42:17)
>
> As reported by the TI spruh73x RM, MPU and LCD modules support spread
> spectrum clocking (SSC) on their output clocks. SSC is used to spread
> the spectral peaking of the clock to reduce any electromagnetic
> interference (EMI) that may be caused due to the clock’s fundamental
> or any of its harmonics.
> The series allows you to enable and adjust the spread spectrum clocking
> for all am33xx PLLs for which it is supported.
>
What is your merge strategy? Should all the patches go through clk tree?
Or you'll send via arm-soc?
next prev parent reply other threads:[~2021-03-30 2:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 16:42 [PATCH v3 0/4] clk: ti: add am33xx spread spectrum clock support Dario Binacchi
2021-03-29 16:42 ` [PATCH v3 1/4] clk: ti: fix typo in routine description Dario Binacchi
2021-03-30 2:24 ` Stephen Boyd
2021-03-29 16:42 ` [PATCH v3 3/4] ARM: dts: am33xx-clocks: add spread spectrum support Dario Binacchi
2021-03-29 16:42 ` [PATCH v3 4/4] clk: ti: add am33xx spread spectrum clock support Dario Binacchi
2021-03-30 2:24 ` Stephen Boyd [this message]
2021-03-31 5:51 ` [PATCH v3 0/4] " Tony Lindgren
2021-03-31 16:48 ` Dario Binacchi
2021-04-01 1:47 ` Stephen Boyd
2021-05-09 13:06 ` Dario Binacchi
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=161707108197.3012082.13148389244272034996@swboyd.mtv.corp.google.com \
--to=sboyd@kernel.org \
--cc=bcousson@baylibre.com \
--cc=dariobin@libero.it \
--cc=devicetree@vger.kernel.org \
--cc=grygorii.strashko@ti.com \
--cc=kristo@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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).