From: Scott Wood <scottwood@freescale.com>
To: <ying.zhang@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org, Ying Zhang <b40530@freescale.com>
Subject: Re: [PATCH 2/3] powerpc/85xx: Create dts of each core in CAMP mode for P1021RDB-PC
Date: Thu, 26 Mar 2015 17:15:50 -0500 [thread overview]
Message-ID: <1427408150.22867.135.camel@freescale.com> (raw)
In-Reply-To: <1427361317-4733-1-git-send-email-ying.zhang@freescale.com>
On Thu, 2015-03-26 at 17:15 +0800, ying.zhang@freescale.com wrote:
> From: Ying Zhang <b40530@freescale.com>
>
> 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.
Are we going to have this split for every board (I hope not)? We
already have a couple examples of CAMP; why do we need p1021
specifically?
> Signed-off-by: Ying Zhang <b40530@freescale.com>
> Change-Id: I92614abdca3db3ab6083c4443ad563fd687050ec
> Reviewed-on: http://git.am.freescale.net:8181/1179
> Reviewed-by: Fleming Andrew-AFLEMING <AFLEMING@freescale.com>
> Tested-by: Fleming Andrew-AFLEMING <AFLEMING@freescale.com>
Get rid of the gerrit stuff.
> + mpic: pic@40000 {
> + protected-sources = <
> + 42 /* serial1 */
> + 31 32 33 /* enet2-queue-group0 */
> + 25 26 27 /* enet2-queue-group1 */
> + >;
> + pic-no-reset;
> + };
If you have pic-no-reset you don't strictly need protected-sources.
Having it can protect against some relatively unlikely software errors,
at the expense of allowing more likely device tree errors. Or at least,
it makes it harder to modify the device tree to assign devices
differently.
-Scott
prev parent reply other threads:[~2015-03-26 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 9:15 [PATCH 2/3] powerpc/85xx: Create dts of each core in CAMP mode for P1021RDB-PC ying.zhang
2015-03-26 22:15 ` Scott Wood [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=1427408150.22867.135.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=b40530@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ying.zhang@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).