[0/3] Drop TI compatibility clocks

Message

Tony Lindgren Feb. 3, 2022, 8:56 a.m. UTC

Hi all,

In order to prepare the TI clocks for fixing lots of devicetree warnings,
let's first drop the now unused compatibility clocks.

The dra7 changes depend on my still pending omap-for-v5.17/fixes-not-urgent
pull request that did not make it for v5.17-rc series so far.

Regards,

Tony


Tony Lindgren (3):
  clk: ti: Drop legacy compatibility clocks for am3
  clk: ti: Drop legacy compatibility clocks for am4
  clk: ti: Drop legacy compatibility clocks for dra7

 drivers/clk/ti/Makefile          |   9 +-
 drivers/clk/ti/clk-33xx-compat.c | 218 --------
 drivers/clk/ti/clk-33xx.c        |   5 +-
 drivers/clk/ti/clk-43xx-compat.c | 225 ---------
 drivers/clk/ti/clk-43xx.c        |   5 +-
 drivers/clk/ti/clk-7xx-compat.c  | 820 -------------------------------
 drivers/clk/ti/clk-7xx.c         |   5 +-
 drivers/clk/ti/clkctrl.c         |  33 +-
 drivers/clk/ti/clock.h           |   3 -
 include/dt-bindings/clock/am3.h  |  93 ----
 include/dt-bindings/clock/am4.h  |  98 ----
 include/dt-bindings/clock/dra7.h | 168 -------
 12 files changed, 15 insertions(+), 1667 deletions(-)
 delete mode 100644 drivers/clk/ti/clk-33xx-compat.c
 delete mode 100644 drivers/clk/ti/clk-43xx-compat.c
 delete mode 100644 drivers/clk/ti/clk-7xx-compat.c

Comments

Stephen Boyd March 11, 2022, 3:36 a.m. UTC | #1

Quoting Tony Lindgren (2022-02-03 00:56:15)
> Hi all,
> 
> In order to prepare the TI clocks for fixing lots of devicetree warnings,
> let's first drop the now unused compatibility clocks.
> 
> The dra7 changes depend on my still pending omap-for-v5.17/fixes-not-urgent
> pull request that did not make it for v5.17-rc series so far.
> 

What should I do with this one though?

Tony Lindgren March 12, 2022, 7:52 a.m. UTC | #2

* Stephen Boyd <[e-mail]> [220311 03:34]:
> Quoting Tony Lindgren (2022-02-03 00:56:15)
> > Hi all,
> > 
> > In order to prepare the TI clocks for fixing lots of devicetree warnings,
> > let's first drop the now unused compatibility clocks.
> > 
> > The dra7 changes depend on my still pending omap-for-v5.17/fixes-not-urgent
> > pull request that did not make it for v5.17-rc series so far.
> > 
> 
> What should I do with this one though?

Well the dependencies are now merged to the mainline kernel, so you could
merge in commit 31aa7056bbec, then apply this series if otherwise OK.

Commit 31aa7056bbec is based on the old v5.16-rc1. It would bring few other
fixes from mainline too if pulled on a v5.17-rc1 based branch:

31aa7056bbec ("ARM: dts: Don't use legacy clock defines for dra7 clkctrl")
9206a3af4fc0 ("clk: ti: Move dra7 clock devices out of the legacy section")
23885389dbbb ("ARM: dts: Fix timer regression for beagleboard revision c")
29a5e8496b3a ("ARM: dts: am335x-wega: Fix typo in mcasp property rx-num-evt")
34596ba380b0 ("ARM: OMAP2+: adjust the location of put_device() call in omapdss_init_of")
80c469a0a037 ("ARM: OMAP2+: hwmod: Add of_node_put() before break")

Regards,

Tony

Stephen Boyd March 15, 2022, 9:06 p.m. UTC | #3

Quoting Tony Lindgren (2022-03-11 23:52:36)
> * Stephen Boyd <[e-mail]> [220311 03:34]:
> > Quoting Tony Lindgren (2022-02-03 00:56:15)
> > > Hi all,
> > > 
> > > In order to prepare the TI clocks for fixing lots of devicetree warnings,
> > > let's first drop the now unused compatibility clocks.
> > > 
> > > The dra7 changes depend on my still pending omap-for-v5.17/fixes-not-urgent
> > > pull request that did not make it for v5.17-rc series so far.
> > > 
> > 
> > What should I do with this one though?
> 
> Well the dependencies are now merged to the mainline kernel, so you could
> merge in commit 31aa7056bbec, then apply this series if otherwise OK.
> 
> Commit 31aa7056bbec is based on the old v5.16-rc1. It would bring few other

Ok. Looks like I can merge v5.17-rc4 and then apply these patches. I'll
do that now. Thanks!