linux-kernel - Re: [PATCH v3 0/4] clk: ti: add am33xx spread spectrum clock support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1870803595.135812.1620565596917@mail1.libero.it>
Date:   Sun, 9 May 2021 15:06:36 +0200 (CEST)
From:   Dario Binacchi <dariobin@...ero.it>
To:     Stephen Boyd <sboyd@...nel.org>, Tony Lindgren <tony@...mide.com>
Cc:     linux-kernel@...r.kernel.org,
        Grygorii Strashko <grygorii.strashko@...com>,
        Benoît Cousson <bcousson@...libre.com>,
        Lee Jones <lee.jones@...aro.org>,
        Michael Turquette <mturquette@...libre.com>,
        Rob Herring <robh+dt@...nel.org>,
        Tero Kristo <kristo@...nel.org>, devicetree@...r.kernel.org,
        linux-clk@...r.kernel.org, linux-omap@...r.kernel.org
Subject: Re: [PATCH v3 0/4] clk: ti: add am33xx spread spectrum clock
 support

Hi Stephen, Hi Tony

> Il 01/04/2021 03:47 Stephen Boyd <sboyd@...nel.org> ha scritto:
> 
>  
> Quoting Tony Lindgren (2021-03-30 22:51:04)
> > * Stephen Boyd <sboyd@...nel.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