public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: <linux-clk@vger.kernel.org>, <sboyd@kernel.org>,
	<mturquette@baylibre.com>, <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 00/11] clk: ti: clkctrl data split based on clkdm boundaries
Date: Wed, 3 Oct 2018 16:17:26 +0300	[thread overview]
Message-ID: <f56fe50b-e5e4-a59d-b0d5-73dcd171dc1e@ti.com> (raw)
In-Reply-To: <20180927144949.GZ5662@atomide.com>

On 27/09/18 17:49, Tony Lindgren wrote:
> * Tero Kristo <t-kristo@ti.com> [180927 06:35]:
>> On 26/09/18 22:13, Tony Lindgren wrote:
>>> Hi,
>>>
>>> * Tony Lindgren <tony@atomide.com> [180904 15:41]:
>>>> * Tero Kristo <t-kristo@ti.com> [180831 15:11]:
>>>>> Hi,
>>>>>
>>>>> This series splits up the clkctrl data for TI SoCs based on clockdomain
>>>>> boundaries, instead of the current CM boundaries. For rest of the SoCs,
>>>>> the CM boundaries are actually the same as clockdomains, only am3/am4/dra7
>>>>> are mutants.
>>>>>
>>>>> This is done in preparation for better supporting Tony's upcoming
>>>>> interconnect driver data introduction for these SoCs.
>>>>>
>>>>> One thing to note is that we maintain backwards compatibility with this
>>>>> series, the compat data is introduced temporarily for this purpose. The
>>>>> compat data can be ditched after couple of release cycles when nobody
>>>>> needs it anymore.
>>>>>
>>>>> The series can be applied independently, as the compat data support
>>>>> makes care that the switch is only done once DT changes are in place.
>>>>
>>>> When this is ready for merging, can you guys please set up an
>>>> immutable branch against v4.19-rc1 with the drivers/clk changes
>>>> for me to merge in too?
>>>>
>>>> I've tested this on am335x and am437x so far and it works fine
>>>> for me, so for the whole series:
>>>>
>>>> Tested-by: Tony Lindgren <tony@atomide.com>
>>>
>>> Any news on getting this into Linux next and merged? The
>>> immutable is still needed too for the dts changes.
>>>
>>
>> This is currently blocked from my side, as the patch [1] from Johan got in
>> clk-next is conflicting with my series. Asked Stephen for either dropping
>> that patch and letting me pick it up but no response so far.
>>
>> [1] https://lkml.org/lkml/2018/8/22/160
> 
> Hmm well the idea is to not redo branches. So how about
> send Stephen a pull request against Johan's patch commit
> 00a461cc32ec ("clk: ti: fix OF child-node lookup")?
> 
> That is assuming 00a461cc32ec is considered immutable and
> OK to use as a base by Stephen? :)
> 
> And assuming that your pull request gets merged, and we
> all consider that branch immutable too, then I can merge it
> in too for the dts changes. It will bring also Rob's
> clean-up patch 00a461cc32ec ("clk: ti: fix OF child-node
> lookup") too but that's just fine.
> 
> Regards,
> 
> Tony
> 

So, finally queued this up towards 4.20, assuming Stephen accepts it.

The immutable branch I have pushed is available here:

https://git.kernel.org/pub/scm/linux/kernel/git/kristo/linux.git/log/?h=clk-ti-clkctrl-sr

It is also tagged in the pull-req I just sent out.

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

      parent reply	other threads:[~2018-10-03 13:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 15:06 [PATCH 00/11] clk: ti: clkctrl data split based on clkdm boundaries Tero Kristo
2018-08-31 15:06 ` [PATCH 01/11] dt-bindings: clock: am33xx: add clkctrl indices for new data layout Tero Kristo
2018-08-31 15:06 ` [PATCH 02/11] dt-bindings: clock: am43xx: " Tero Kristo
2018-08-31 15:06 ` [PATCH 03/11] dt-bindings: clock: dra7xx: " Tero Kristo
2018-08-31 15:07 ` [PATCH 04/11] clk: ti: clkctrl: support multiple clkctrl nodes under a cm node Tero Kristo
2018-10-12 21:25   ` Stephen Boyd
2018-10-12 21:45     ` Rob Herring
2018-10-12 22:03       ` Stephen Boyd
2018-10-15 15:58         ` Tero Kristo
2018-10-15 23:38           ` Stephen Boyd
2018-10-16  7:37             ` Tero Kristo
2018-10-16 15:37               ` Stephen Boyd
2018-08-31 15:07 ` [PATCH 05/11] clk: ti: clkctrl: replace dashes from clkdm name with underscore Tero Kristo
2018-08-31 15:07 ` [PATCH 06/11] clk: ti: am33xx: rename existing clkctrl data as compat data Tero Kristo
2018-08-31 15:07 ` [PATCH 07/11] clk: ti: am33xx: add new clkctrl data for am33xx Tero Kristo
2018-08-31 15:07 ` [PATCH 08/11] clk: ti: am43xx: rename existing clkctrl data as compat data Tero Kristo
2018-08-31 15:07 ` [PATCH 09/11] clk: ti: am43xx: add new clkctrl data for am43xx Tero Kristo
2018-08-31 15:07 ` [PATCH 10/11] clk: ti: dra7xx: rename existing clkctrl data as compat data Tero Kristo
2018-08-31 15:07 ` [PATCH 11/11] clk: ti: dra7: add new clkctrl data Tero Kristo
2018-09-04 15:36 ` [PATCH 00/11] clk: ti: clkctrl data split based on clkdm boundaries Tony Lindgren
2018-09-26 19:13   ` Tony Lindgren
2018-09-26 19:13     ` Tony Lindgren
2018-09-27  6:31     ` Tero Kristo
2018-09-27  6:31       ` Tero Kristo
2018-09-27 14:49       ` Tony Lindgren
2018-09-27 14:49         ` Tony Lindgren
2018-10-03 13:17         ` Tero Kristo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f56fe50b-e5e4-a59d-b0d5-73dcd171dc1e@ti.com \
    --to=t-kristo@ti.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox