From: Dario Binacchi <dariobin@libero.it>
To: Stephen Boyd <sboyd@kernel.org>, Tony Lindgren <tony@atomide.com>
Cc: linux-kernel@vger.kernel.org,
"Grygorii Strashko" <grygorii.strashko@ti.com>,
"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>,
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: Sun, 9 May 2021 15:06:36 +0200 (CEST) [thread overview]
Message-ID: <1870803595.135812.1620565596917@mail1.libero.it> (raw)
In-Reply-To: <161724167065.2260335.15543151418752525635@swboyd.mtv.corp.google.com>
Hi Stephen, Hi Tony
> Il 01/04/2021 03:47 Stephen Boyd <sboyd@kernel.org> ha scritto:
>
>
> Quoting Tony Lindgren (2021-03-30 22:51:04)
> > * Stephen Boyd <sboyd@kernel.org> [210330 02:25]:
> > > 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?
> >
> > Probably best to just merge all via the clk tree as that's where most of
> > the changes are.
> >
>
> Ok. If nobody reviews/acks the last patch in a few days I'll merge the
> pile through clk tree.
It's been over a month since I submitted the patches. Meanwhile Tero Kristo has
reviewed the most important patch of the series. However, I have not seen any
progress in the state of the series. Furthermore, I don't see the DTS patches
in the clk tree. Am I missing something? Or do I have to do something? Sorry
for the questions but I don't have much experience with patch merge strategies.
Thanks and regards,
Dario
prev parent reply other threads:[~2021-05-09 13:06 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 ` [PATCH v3 0/4] " Stephen Boyd
2021-03-31 5:51 ` Tony Lindgren
2021-03-31 16:48 ` Dario Binacchi
2021-04-01 1:47 ` Stephen Boyd
2021-05-09 13:06 ` Dario Binacchi [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=1870803595.135812.1620565596917@mail1.libero.it \
--to=dariobin@libero.it \
--cc=bcousson@baylibre.com \
--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=sboyd@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).