From: Kumar Gala <galak@kernel.crashing.org>
To: Prabhakar Kushwaha <prabhakar@freescale.com>
Cc: meet2prabhu@gmail.com, devicetree-discuss@lists.ozlabs.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/85xx:Create dts of each core in CAMP mode for P1020RDB
Date: Thu, 19 May 2011 01:33:06 -0500 [thread overview]
Message-ID: <C0FC0AB9-E31C-4976-991E-80D3DBA40BDF@kernel.crashing.org> (raw)
In-Reply-To: <1303974000-2943-1-git-send-email-prabhakar@freescale.com>
On Apr 28, 2011, at 2:00 AM, Prabhakar Kushwaha wrote:
> Create the dts files for each core and splits the devices between the =
two cores
> for P1020RDB.
>=20
> Core0 has core0 to have memory, l2, i2c, spi, gpio, tdm, dma, usb, =
eth1, eth2,
> sdhc, crypto, global-util, message, pci0, pci1, msi.
> Core1 has l2, eth0, crypto.
>=20
> MPIC is shared between two cores but each core will protect its =
interrupts from
> other core by using "protected-sources" of mpic.
>=20
> Fix compatible property for global-util node of P1020si.dtsi.
>=20
> Signed-off-by: Prabhakar Kushwaha <prabhakar@freescale.com>
> ---
> Based upon =
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git(branc=
h master)
>=20
> This patch depends on following patch
> "powerpc/85xx: P1020 DTS : re-organize dts files"
>=20
> arch/powerpc/boot/dts/p1020rdb_camp_core0.dts | 213 =
+++++++++++++++++++++++++
> arch/powerpc/boot/dts/p1020rdb_camp_core1.dts | 148 +++++++++++++++++
> arch/powerpc/boot/dts/p1020si.dtsi | 2 +-
> 3 files changed, 362 insertions(+), 1 deletions(-)
> create mode 100644 arch/powerpc/boot/dts/p1020rdb_camp_core0.dts
> create mode 100644 arch/powerpc/boot/dts/p1020rdb_camp_core1.dts
applied to next
- k=
prev parent reply other threads:[~2011-05-19 6:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 7:00 [PATCH] powerpc/85xx:Create dts of each core in CAMP mode for P1020RDB Prabhakar Kushwaha
2011-05-19 6:33 ` Kumar Gala [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=C0FC0AB9-E31C-4976-991E-80D3DBA40BDF@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=meet2prabhu@gmail.com \
--cc=prabhakar@freescale.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;
as well as URLs for NNTP newsgroup(s).