[U-Boot] [PATCH] powerpc/mpc85xx: Enabling CPC conditionally based on hwconfig options - Singh Sandeep-B37400

From: Singh Sandeep-B37400 <B37400@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/mpc85xx: Enabling CPC conditionally based on hwconfig options
Date: Tue, 2 Jul 2013 10:01:46 +0000	[thread overview]
Message-ID: <3F1D9DCAAB49B94D88DBE05911FA4E6E070D5878@039-SN1MPN1-001.039d.mgd.msft.net> (raw)
In-Reply-To: <1371238766.2996.6@snotra>

Sorry somehow I missed this earlier. Please find my reply inline.

Regards,
Sandeep

> -----Original Message-----
> From: Wood Scott-B07421
> Sent: 15 June 2013 01:09
> To: Singh Sandeep-B37400
> Cc: Wood Scott-B07421; u-boot at lists.denx.de; afleming at gmail.com
> Subject: Re: [U-Boot] [PATCH] powerpc/mpc85xx: Enabling CPC conditionally
> based on hwconfig options
> 
> On 06/14/2013 12:26:18 AM, Singh Sandeep-B37400 wrote:
> > This was done with the intension of providing greater
> > configurability. When
> > en_cpc is defined then it's entirely up to user to decide which cpcs
> > are to
> > be enabled. Hence we do following:
> >
> > if_defined("en_cpc"){
> > 	only_then
> > 		check_for_cpc_options;
> > } else {
> > 	enable_all_cpc;
> > }
> 
> OK, I see.
> 
> What is the use case for enabling one cpc but not another?  What is the
> use case for disabling cpc at all?  The answer should go in the commit
> message.

In B4860, Starcore owns one CPC and second CPC is owned by PowerPC. So we need to enable only one CPC at u-boot.

> 
> -Scott