[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1766999502.215268.1617209316614@mail1.libero.it>
Date: Wed, 31 Mar 2021 18:48:36 +0200 (CEST)
From: Dario Binacchi <dariobin@...ero.it>
To: Tony Lindgren <tony@...mide.com>, Stephen Boyd <sboyd@...nel.org>
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
> Il 31/03/2021 07:51 Tony Lindgren <tony@...mide.com> ha scritto:
>
>
> * 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.
>
This means that I no longer have to send patches to TI / OMAP maintainers, commiters
and fixers, as well as at linux-omap@...r.kernel.org ?
Even if the a1e980789b06 ("am335x-spread-spectrum) clk: ti: add am33xx spread spectrum clock support")
patch is basically related to the AM33xx/AM43xx SOCs?
Thanks and regards,
Dario
> Regards,
>
> Tony
Powered by blists - more mailing lists