Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Sun, 9 May 2021 15:06:36 +0200 (CEST)
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>,
        =?UTF-8?Q?Beno=C3=AEt_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
Message-ID: <1870803595.135812.1620565596917@mail1.libero.it>
In-Reply-To: <161724167065.2260335.15543151418752525635@swboyd.mtv.corp.google.com>
References: <20210329164222.26794-1-dariobin@libero.it>
 <161707108197.3012082.13148389244272034996@swboyd.mtv.corp.google.com>
 <YGQNyGDkAbUXRYtA@atomide.com>
 <161724167065.2260335.15543151418752525635@swboyd.mtv.corp.google.com>
Subject: Re: [PATCH v3 0/4] clk: ti: add am33xx spread spectrum clock
 support
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Importance: Normal
Precedence: bulk

Hi Stephen, Hi Tony

> Il 01/04/2021 03:47 Stephen Boyd <sboyd@kernel.org> ha scritto:
>=20
> =20
> 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)
> > > >=20
> > > > As reported by the TI spruh73x RM, MPU and LCD modules support spre=
ad
> > > > spectrum clocking (SSC) on their output clocks. SSC is used to spre=
ad
> > > > the spectral peaking of the clock to reduce any electromagnetic
> > > > interference (EMI) that may be caused due to the clock=E2=80=99s fu=
ndamental
> > > > or any of its harmonics.
> > > > The series allows you to enable and adjust the spread spectrum cloc=
king
> > > > for all am33xx PLLs for which it is supported.
> > > >=20
> > >=20
> > > What is your merge strategy? Should all the patches go through clk tr=
ee?
> > > Or you'll send via arm-soc?
> >=20
> > Probably best to just merge all via the clk tree as that's where most o=
f
> > the changes are.
> >=20
>=20
> 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=20
reviewed the most important patch of the series. However, I have not seen a=
ny=20
progress in the state of the series. Furthermore, I don't see the DTS patch=
es=20
in the clk tree. Am I missing something? Or do I have to do something? Sorr=
y=20
for the questions but I don't have much experience with patch merge strateg=
ies.

Thanks and regards,
Dario