[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <161707108197.3012082.13148389244272034996@swboyd.mtv.corp.google.com>
Date: Mon, 29 Mar 2021 19:24:41 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Dario Binacchi <dariobin@...ero.it>, linux-kernel@...r.kernel.org
Cc: Grygorii Strashko <grygorii.strashko@...com>,
Dario Binacchi <dariobin@...ero.it>,
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>,
Tony Lindgren <tony@...mide.com>, 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
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?
Powered by blists - more mailing lists