All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: "Khoronzhuk, Ivan" <ivan.khoronzhuk@ti.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Mike Turquette <mturquette@linaro.org>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Karicheri, Muralidharan" <m-karicheri2@ti.com>,
	"Strashko, Grygorii" <grygorii.strashko@ti.com>
Subject: Re: linux-next: manual merge of the clk tree with the keystone tree
Date: Wed, 26 Feb 2014 09:26:26 -0500	[thread overview]
Message-ID: <530DF992.1090106@ti.com> (raw)
In-Reply-To: <530DD2CD.7000302@ti.com>

On Wednesday 26 February 2014 06:41 AM, Khoronzhuk, Ivan wrote:
> 
> On 02/26/2014 09:15 AM, Stephen Rothwell wrote:
>> Hi Mike,
>>
>> Today's linux-next merge of the clk tree got a conflict in
>> arch/arm/boot/dts/keystone-clocks.dtsi between commit 0cfc9ccec2a8 ("ARM:
>> dts: keystone: preparatory patch to support K2L and K2E SOCs") from the
>> keystone tree and commit 565bbdcd3b91 ("ARM: keystone: dts: fix clkvcp3
>> control register address") from the clk tree.
>>
>> I fixed it up (by adding the following merge fix patch) and can carry the
>> fix as necessary (no action is required).
>>
>> From: Stephen Rothwell <sfr@canb.auug.org.au>
>> Date: Wed, 26 Feb 2014 18:12:55 +1100
>> Subject: [PATCH] ARM: keystone: dts: fix for code movement
>>
>> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> ---
>>   arch/arm/boot/dts/k2hk-clocks.dtsi | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/boot/dts/k2hk-clocks.dtsi b/arch/arm/boot/dts/k2hk-clocks.dtsi
>> index 4eed84feb761..a71aa2996321 100644
>> --- a/arch/arm/boot/dts/k2hk-clocks.dtsi
>> +++ b/arch/arm/boot/dts/k2hk-clocks.dtsi
>> @@ -339,7 +339,7 @@ clocks {
>>   		compatible = "ti,keystone,psc-clock";
>>   		clocks = <&chipclk13>;
>>   		clock-output-names = "vcp-3";
>> -		reg = <0x0235000a8 0xb00>, <0x02350060 0x400>;
>> +		reg = <0x023500a8 0xb00>, <0x02350060 0x400>;
>>   		reg-names = "control", "domain";
>>   		domain-id = <24>;
>>   	};
> 
> The patch "ARM: dts: keystone: preparatory patch to support K2L and K2E 
> SOCs"
> is from "[PATCH 0/4] ARM: dts: keystone: Add support for K2H and K2E 
> SOCs/EVMs"
> series (http://www.spinics.net/lists/arm-kernel/msg310946.html).
> 
> As I understand, this series splits keystone clock tree into tree boards.
Not boards but SOCs.

> As result clock "clkvcp3" (for wich reg is corrected) is moved to the 
> following two dts:
> 
> k2hk-clocks.dtsi
> k2l-clocks.dtsi
> 
> So probably you should apply this change to k2l-clocks.dtsi too.
> 
I will fix my tree. Thanks for spotting it Ivan !!

Regards,
Santosh

  reply	other threads:[~2014-02-26 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26  7:15 linux-next: manual merge of the clk tree with the keystone tree Stephen Rothwell
2014-02-26  7:28 ` Mike Turquette
2014-02-26 11:41 ` Ivan Khoronzhuk
2014-02-26 11:41   ` Ivan Khoronzhuk
2014-02-26 14:26   ` Santosh Shilimkar [this message]
2014-02-26 15:00   ` Karicheri, Muralidharan

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=530DF992.1090106@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=grygorii.strashko@ti.com \
    --cc=ivan.khoronzhuk@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=m-karicheri2@ti.com \
    --cc=mturquette@linaro.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.