From: Leekha Shaveta-B20052 <B20052@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Zhao Chenhui-B35336 <B35336@freescale.com>,
Mehresh Ramneek-B31383 <B31383@freescale.com>,
Timur Tabi <timur@tabi.org>,
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 1/6] powerpc/fsl-booke: Add initial silicon device tree files for B4860QDS
Date: Tue, 19 Mar 2013 06:13:10 +0000 [thread overview]
Message-ID: <E12D2F89F87F4A49B0320A4C2DE7E749145374@039-SN2MPN1-011.039d.mgd.msft.net> (raw)
In-Reply-To: <9B5470DD-595E-4234-B462-1232745D8F9F@kernel.crashing.org>
-----Original Message-----
From: Kumar Gala [mailto:galak@kernel.crashing.org]=20
Sent: Monday, March 18, 2013 8:34 PM
To: Leekha Shaveta-B20052
Cc: Timur Tabi; linuxppc-dev@lists.ozlabs.org; Zhao Chenhui-B35336; Lian Mi=
nghuan-B31939; Tang Yuantian-B29983; Fleming Andy-AFLEMING; Mehresh Ramneek=
-B31383; Sethi Varun-B16395
Subject: Re: [PATCH 1/6] powerpc/fsl-booke: Add initial silicon device tree=
files for B4860QDS
On Mar 18, 2013, at 2:41 AM, Leekha Shaveta-B20052 wrote:
>=20
>=20
> -----Original Message-----
> From: Timur Tabi [mailto:timur@tabi.org]
> Sent: Friday, March 15, 2013 6:38 PM
> To: Leekha Shaveta-B20052
> Cc: linuxppc-dev@lists.ozlabs.org; Zhao Chenhui-B35336; Lian=20
> Minghuan-B31939; Tang Yuantian-B29983; Fleming Andy-AFLEMING; Mehresh=20
> Ramneek-B31383; Sethi Varun-B16395
> Subject: Re: [PATCH 1/6] powerpc/fsl-booke: Add initial silicon device=20
> tree files for B4860QDS
>=20
> On Fri, Mar 15, 2013 at 2:55 AM, Shaveta Leekha <shaveta@freescale.com> w=
rote:
>=20
>=20
>> + iommu@20000 {
>> + compatible =3D "fsl,pamu-v1.0", "fsl,pamu";
>> + reg =3D <0x20000 0x4000>;
>> + interrupts =3D <
>> + 24 2 0 0
>> + 16 2 1 1>;
>> + };
>=20
> You need to add the PAMU topology.
> [SL] Thanks for reviewing the patches.
> These patches are on similar lines as T4 initial support In due course=20
> of time, we plan to add pamu topology and pamu related support in various=
devices both for T4 and B4.
> Kumar can you please suggest?
I can help with the B4 topology as its reasonable well described, I've been=
working on trying to get the info to finish T4.
[SL] I have seen your patches to add PAMU topology in B4. Should I include =
them in my set of patches or you would send them above my initial set of pa=
tches?
BR,
Shaveta
- k
next prev parent reply other threads:[~2013-03-19 6:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 7:55 [PATCH 1/6] powerpc/fsl-booke: Add initial silicon device tree files for B4860QDS Shaveta Leekha
2013-03-15 7:55 ` [PATCH 2/6] powerpc/fsl-booke: Add initial B4860QDS board device tree Shaveta Leekha
2013-03-15 20:26 ` Kumar Gala
2013-03-18 6:31 ` Leekha Shaveta-B20052
2013-03-18 15:02 ` Kumar Gala
2013-03-19 6:11 ` Leekha Shaveta-B20052
2013-03-19 6:23 ` Leekha Shaveta-B20052
2013-03-15 7:55 ` [PATCH 3/6] powerpc/fsl-booke: Add initial silicon device tree files for B4420QDS Shaveta Leekha
2013-03-15 20:30 ` Kumar Gala
2013-03-15 7:55 ` [PATCH 4/6] powerpc/fsl-booke: Add initial B4420QDS board device tree Shaveta Leekha
2013-03-15 20:31 ` Kumar Gala
2013-03-18 7:00 ` Leekha Shaveta-B20052
2013-03-15 7:55 ` [PATCH 5/6] powerpc/fsl-booke: Add B4_QDS board support Shaveta Leekha
2013-03-15 15:58 ` Kumar Gala
2013-03-18 6:28 ` Leekha Shaveta-B20052
2013-03-18 14:56 ` Kumar Gala
2013-03-19 6:07 ` Leekha Shaveta-B20052
2013-03-15 7:55 ` [PATCH 6/6] powerpc/85xx: Update corenet64_smp_defconfig for B4_QDS Shaveta Leekha
2013-03-15 13:07 ` [PATCH 1/6] powerpc/fsl-booke: Add initial silicon device tree files for B4860QDS Timur Tabi
2013-03-18 7:41 ` Leekha Shaveta-B20052
2013-03-18 15:03 ` Kumar Gala
2013-03-19 6:13 ` Leekha Shaveta-B20052 [this message]
2013-03-20 10:32 ` Leekha Shaveta-B20052
2013-03-20 11:37 ` Timur Tabi
2013-03-15 15:54 ` Kumar Gala
2013-03-15 20:29 ` Kumar Gala
2013-03-18 6:59 ` 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=E12D2F89F87F4A49B0320A4C2DE7E749145374@039-SN2MPN1-011.039d.mgd.msft.net \
--to=b20052@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 \
--cc=timur@tabi.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).