linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Leekha Shaveta-B20052 <B20052@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	Mehresh Ramneek-B31383 <B31383@freescale.com>,
	Zhao Chenhui-B35336 <B35336@freescale.com>,
	Garg Vakul-B16394 <B16394@freescale.com>,
	Lian Minghuan-B31939 <B31939@freescale.com>,
	Tang Yuantian-B29983 <B29983@freescale.com>,
	Fleming Andy-AFLEMING <afleming@freescale.com>,
	Sethi Varun-B16395 <B16395@freescale.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: RE: [PATCH 2/5] powerpc/fsl-booke: Add initial silicon device tree files for B4860 and B4420
Date: Fri, 5 Apr 2013 05:23:43 +0000	[thread overview]
Message-ID: <E12D2F89F87F4A49B0320A4C2DE7E749151E18@039-SN2MPN1-011.039d.mgd.msft.net> (raw)
In-Reply-To: <BF757FF6-067E-4A23-9A12-E510B5CE59A7@kernel.crashing.org>



-----Original Message-----
From: Kumar Gala [mailto:galak@kernel.crashing.org]=20
Sent: Friday, April 05, 2013 12:44 AM
To: Leekha Shaveta-B20052
Cc: Wood Scott-B07421; Zhao Chenhui-B35336; Mehresh Ramneek-B31383; Garg Va=
kul-B16394; Lian Minghuan-B31939; Tang Yuantian-B29983; Fleming Andy-AFLEMI=
NG; Sethi Varun-B16395; linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/5] powerpc/fsl-booke: Add initial silicon device tree=
 files for B4860 and B4420


On Apr 4, 2013, at 2:03 AM, Leekha Shaveta-B20052 wrote:

>=20
>=20
> -----Original Message-----
> From: Wood Scott-B07421
> Sent: Wednesday, April 03, 2013 10:10 PM
> To: Leekha Shaveta-B20052
> Cc: Wood Scott-B07421; linuxppc-dev@lists.ozlabs.org; Zhao=20
> Chenhui-B35336; Lian Minghuan-B31939; Garg Vakul-B16394; Tang=20
> Yuantian-B29983; Fleming Andy-AFLEMING; Mehresh Ramneek-B31383; Sethi=20
> Varun-B16395
> Subject: Re: [PATCH 2/5] powerpc/fsl-booke: Add initial silicon device=20
> tree files for B4860 and B4420
>=20
> On 04/03/2013 01:42:14 AM, Leekha Shaveta-B20052 wrote:
>>=20
>>=20
>> -----Original Message-----
>> From: Wood Scott-B07421
>> Sent: Wednesday, April 03, 2013 12:49 AM
>> To: Leekha Shaveta-B20052
>> Cc: linuxppc-dev@lists.ozlabs.org; Zhao Chenhui-B35336; Lian=20
>> Minghuan-B31939; Leekha Shaveta-B20052; Garg Vakul-B16394; Tang=20
>> Yuantian-B29983; Fleming Andy-AFLEMING; Mehresh Ramneek-B31383; Sethi
>> Varun-B16395
>> Subject: Re: [PATCH 2/5] powerpc/fsl-booke: Add initial silicon=20
>> device tree files for B4860 and B4420
>>=20
>> On 04/02/2013 02:16:05 AM, Shaveta Leekha wrote:
>>> +/ {
>>> +	compatible =3D "fsl,B4860";
>>> +
>>> +	cpus {
>>> +		cpu1: PowerPC,e6500@1 {
>>> +			device_type =3D "cpu";
>>> +			reg =3D <2 3>;
>>> +			next-level-cache =3D <&L2>;
>>> +		};
>>> +		cpu2: PowerPC,e6500@2 {
>>> +			device_type =3D "cpu";
>>> +			reg =3D <4 5>;
>>> +			next-level-cache =3D <&L2>;
>>> +		};
>>> +		cpu3: PowerPC,e6500@3 {
>>> +			device_type =3D "cpu";
>>> +			reg =3D <6 7>;
>>> +			next-level-cache =3D <&L2>;
>>> +		};
>>=20
>> The unit addresses need to match "reg".
>> [SL] You mean  "@1" should match to "reg =3D <2 3>" ?
>=20
> Yes, it should be "@2" for that node.
>=20
>> As each e6500 core in B4860 is dual- threaded, reg property here=20
>> represents the thread's identifier in that PA core.
>>=20
>> So convention used in T4 and B4 is: core 0 having threads 0 and 1,
>> 						Core 1 having <2 3> and
>> so on....
>=20
> The convention used in device trees is that the unit address matches the =
reg.
>=20
> -Scott
> [SL] Ok, I can change that. Will make unit address as @2 for <2 3>, @4 fo=
r <4 5> and so on....
>=20
> Kumar, please respond here, as I have followed the convention used in=20
> T4 device tree files for Dual-threaded cores.

Scott is correct, we probably need to fix the T4 dts.

- k
[SL] ok, will do it for B4
Regards,
Shaveta=20

  reply	other threads:[~2013-04-05  5:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02  7:16 [PATCH 2/5] powerpc/fsl-booke: Add initial silicon device tree files for B4860 and B4420 Shaveta Leekha
2013-04-02  7:16 ` [PATCH 3/5] powerpc/fsl-booke: Add initial B4860QDS and B4420QDS board device tree Shaveta Leekha
2013-04-02  7:16 ` [PATCH 4/5] powerpc/fsl-booke: Add B4_QDS board support Shaveta Leekha
2013-04-03 16:42   ` Kumar Gala
2013-04-04  7:10     ` Leekha Shaveta-B20052
2013-04-02  7:16 ` [PATCH 5/5] powerpc/85xx: Update corenet64_smp_defconfig for B4_QDS Shaveta Leekha
2013-04-02 19:19 ` [PATCH 2/5] powerpc/fsl-booke: Add initial silicon device tree files for B4860 and B4420 Scott Wood
2013-04-03  6:42   ` Leekha Shaveta-B20052
2013-04-03 16:39     ` Scott Wood
2013-04-04  7:03       ` Leekha Shaveta-B20052
2013-04-04 19:13         ` Kumar Gala
2013-04-05  5:23           ` Leekha Shaveta-B20052 [this message]
2013-04-03 16:39 ` Kumar Gala
2013-04-04  7:10   ` Leekha Shaveta-B20052
2013-04-04 19:13     ` Kumar Gala
2013-04-05  5:26       ` Leekha Shaveta-B20052

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=E12D2F89F87F4A49B0320A4C2DE7E749151E18@039-SN2MPN1-011.039d.mgd.msft.net \
    --to=b20052@freescale.com \
    --cc=B07421@freescale.com \
    --cc=B16394@freescale.com \
    --cc=B16395@freescale.com \
    --cc=B29983@freescale.com \
    --cc=B31383@freescale.com \
    --cc=B31939@freescale.com \
    --cc=B35336@freescale.com \
    --cc=afleming@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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;
as well as URLs for NNTP newsgroup(s).