All of lore.kernel.org
 help / color / mirror / Atom feed
From: shaveta at freescale.com <shaveta@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/mpc85xx: Enabling CPC conditionally based on hwconfig options
Date: Thu, 7 Aug 2014 07:39:23 +0000	[thread overview]
Message-ID: <09ed522a92c1449eafca905a1101050f@BY2PR03MB299.namprd03.prod.outlook.com> (raw)
In-Reply-To: <53E266FF.40807@freescale.com>

Hi York,

This change was required to provide the flexibility of enabling DDRC1/CPC1 by
SC3900/DSP core as DDRC1 is used by Starcore. SC enables CPC1 as per their requirement.
PPC core use DDRC2, so it enables DDRC2/CPC2.

Do you suggest mentioning it in the commit message also?

Thanks and Regards,
Shaveta

-----Original Message-----
From: Sun York-R58495 
Sent: Wednesday, August 06, 2014 11:04 PM
To: Leekha Shaveta-B20052; u-boot at lists.denx.de
Cc: Wood Scott-B07421; Singh Sandeep-B37400
Subject: Re: [PATCH] powerpc/mpc85xx: Enabling CPC conditionally based on hwconfig options

On 07/01/2014 11:14 PM, Shaveta Leekha wrote:
> If hwconfig does not contains "en_cpc" then by default all cpcs are 
> enabled If this config is defined then only those individual cpcs 
> which are defined in the subargument of "en_cpc" will be enabled e.g 
> en_cpc:cpc1,cpc2; (this will enable cpc1 and cpc2) or en_cpc:cpc2; 
> (this enables just cpc2)
> 

What's the user's case for enabling selected CPC?

York

  reply	other threads:[~2014-08-07  7:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02  6:14 [U-Boot] [PATCH] powerpc/mpc85xx: Enabling CPC conditionally based on hwconfig options Shaveta Leekha
2014-08-06 17:33 ` York Sun
2014-08-07  7:39   ` shaveta at freescale.com [this message]
2014-08-20 19:37 ` York Sun
  -- strict thread matches above, loose matches on Subject: below --
2013-06-13  6:59 Sandeep Singh
2013-06-13 16:39 ` Scott Wood
2013-06-14  5:26   ` Singh Sandeep-B37400
2013-06-14 19:39     ` Scott Wood
2013-07-02 10:01       ` Singh Sandeep-B37400

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=09ed522a92c1449eafca905a1101050f@BY2PR03MB299.namprd03.prod.outlook.com \
    --to=shaveta@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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.