[0/3] clk: ti: couple of fixes towards 5.8

Message

Tero Kristo April 29, 2020, 1:13 p.m. UTC

Hi,

The issues fixed by these patches have been around for a while, so they
can be picked up for 5.8.

Patch #1 fixes a memory leak within composite clock registration, which
is only visible on platforms actually using composite clocks;
omap4/omap5.

Last two patches fix parenting of the l4-secure clocks for omap4/omap5,
which was apparenly missed when the clkctrl data for these domains was
created.

-Tero


--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki

Comments

Tony Lindgren April 29, 2020, 10:21 p.m. UTC | #1

* Tero Kristo <[e-mail]> [200429 13:14]:
> Hi,
> 
> The issues fixed by these patches have been around for a while, so they
> can be picked up for 5.8.
> 
> Patch #1 fixes a memory leak within composite clock registration, which
> is only visible on platforms actually using composite clocks;
> omap4/omap5.

OK great thanks for chasing that one down.

> Last two patches fix parenting of the l4-secure clocks for omap4/omap5,
> which was apparenly missed when the clkctrl data for these domains was
> created.

Oops sorry about that. Looks like I totally missed adding the source
clocks for those.

For the whole series:

Acked-by: Tony Lindgren <[e-mail]>