LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Poonam Aggrwal <poonam.aggrwal@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH][v2] powerpc/85xx: Create dts for each core in CAMP mode for P2020RDB
Date: Thu, 24 Sep 2009 11:20:43 -0700	[thread overview]
Message-ID: <85051629-88AD-4AF4-A2D8-93E3A2EB7343@kernel.crashing.org> (raw)
In-Reply-To: <1253380436-1590-1-git-send-email-poonam.aggrwal@freescale.com>


On Sep 19, 2009, at 10:13 AM, Poonam Aggrwal wrote:

> This patch creates the dts files for each core and splits the  
> devices between
> the two cores for P2020RDB.
>
> core0 has memory, L2, i2c, spi, dma1, usb, eth0, eth1, crypto,  
> global-util, pci0
> core1 has L2, dma2, eth0, pci1, msi.
>
> MPIC is shared between two cores but each core will protect its
> interrupts from other core by using "protected-sources" of mpic.
>
> Signed-off-by: Poonam Aggrwal <poonam.aggrwal@freescale.com>
> ---
> - based on http://www.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git
> - branch->next
> - Removed interrupt properties for serial ports to make them work in  
> polling mode.
> arch/powerpc/boot/dts/p2020rdb_camp_core0.dts |  363 ++++++++++++++++ 
> +++++++++
> arch/powerpc/boot/dts/p2020rdb_camp_core1.dts |  184 +++++++++++++
> arch/powerpc/platforms/85xx/mpc85xx_rdb.c     |   10 +-
> 3 files changed, 556 insertions(+), 1 deletions(-)
> create mode 100644 arch/powerpc/boot/dts/p2020rdb_camp_core0.dts
> create mode 100644 arch/powerpc/boot/dts/p2020rdb_camp_core1.dts

applied to merge

- k

  parent reply	other threads:[~2009-09-24 18:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-19 17:13 [PATCH][v2] powerpc/85xx: Create dts for each core in CAMP mode for P2020RDB Poonam Aggrwal
2009-09-22 10:21 ` Aggrwal Poonam-B10812
2009-09-24 18:20 ` Kumar Gala [this message]
2009-11-05 13:15 ` Kumar Gala

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=85051629-88AD-4AF4-A2D8-93E3A2EB7343@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=poonam.aggrwal@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