From: Tabi Timur-B04825 <B04825@freescale.com>
To: Xu Jiucheng-B37781 <B37781@freescale.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] powerpc/85xx: Create dts of each core in CAMP mode for P1021RDB-PC
Date: Tue, 10 Jul 2012 12:25:48 +0000 [thread overview]
Message-ID: <CAOZdJXX1+=p3GMccLvCwFpei2igidXuo_U1gSVy56cBAkKxoHg@mail.gmail.com> (raw)
In-Reply-To: <1341909561-6591-2-git-send-email-Jiucheng.Xu@freescale.com>
On Tue, Jul 10, 2012 at 3:39 AM, Xu Jiucheng <Jiucheng.Xu@freescale.com> wr=
ote:
> Create the dts files for each core and splits the devices between
> the two cores for P1021RDB-PC.
>
> Core0 has l2, serial0, i2c, spi, gpio, tdm,dma, usb, eth0, eth1,
> sdhc, crypto, global-util, message, pci0, pci1, msi, crypto.
> Core1 has l2, serial1, eth2.
>
> Signed-off-by: Xu Jiucheng <Jiucheng.Xu@freescale.com>
> Signed-off-by: Matthew McClintock <msm@freescale.com>
> ---
Do we really want AMP device trees upstream? They're very
application-specific, and AMP support has always been a hack. If
anything, I think we should be deleting AMP device trees from
upstream, not adding more.
--=20
Timur Tabi
Linux kernel developer at Freescale=
next prev parent reply other threads:[~2012-07-10 12:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 8:39 [PATCH] powerpc/85xx: Add dts files for P1021RDB-PC board Xu Jiucheng
2012-07-10 8:39 ` [PATCH 2/2] powerpc/85xx: Create dts of each core in CAMP mode for P1021RDB-PC Xu Jiucheng
2012-07-10 12:25 ` Tabi Timur-B04825 [this message]
2012-07-11 14:47 ` Kumar Gala
2012-07-11 14:49 ` Timur Tabi
2012-07-11 14:52 ` AW: " Schneider, Kolja
2012-07-11 14:56 ` Timur Tabi
2012-07-11 14:53 ` Kumar Gala
2012-07-11 14:56 ` Timur Tabi
2012-07-12 3:16 ` Kumar Gala
2012-07-12 3:53 ` Tabi Timur-B04825
2012-07-12 4:05 ` Kumar Gala
2012-07-10 15:57 ` Scott Wood
2012-07-10 11:48 ` [PATCH] powerpc/85xx: Add dts files for P1021RDB-PC board Kumar Gala
2012-07-11 9:58 ` Jiucheng Xu
2012-07-11 12:31 ` Kumar Gala
2012-07-11 12:43 ` 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='CAOZdJXX1+=p3GMccLvCwFpei2igidXuo_U1gSVy56cBAkKxoHg@mail.gmail.com' \
--to=b04825@freescale.com \
--cc=B29882@freescale.com \
--cc=B37781@freescale.com \
--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 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.