From: Scott Wood <scottwood@freescale.com>
To: Wang Dongsheng-B40534 <Dongsheng.Wang@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"haokexin@gmail.com" <haokexin@gmail.com>,
Kushwaha Prabhakar-B32579 <prabhakar@freescale.com>,
Jin Zhengxiong-R64188 <Jason.Jin@freescale.com>
Subject: Re: [PATCH v2 1/2] fsl/corenet_generic: add a particular initialization for platform
Date: Wed, 16 Apr 2014 14:36:26 -0500 [thread overview]
Message-ID: <1397676986.28539.10.camel@snotra.buserror.net> (raw)
In-Reply-To: <77e2c53b2f154faba68c8b7ac760accc@BN1PR03MB188.namprd03.prod.outlook.com>
On Tue, 2014-04-15 at 21:58 -0500, Wang Dongsheng-B40534 wrote:
>
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Wednesday, April 16, 2014 3:39 AM
> > To: Wang Dongsheng-B40534
> > Cc: Jin Zhengxiong-R64188; haokexin@gmail.com; Kushwaha Prabhakar-B32579;
> > linuxppc-dev@lists.ozlabs.org
> > Subject: Re: [PATCH v2 1/2] fsl/corenet_generic: add a particular initialization
> > for platform
> >
> > On Tue, 2014-04-15 at 13:53 +0800, Dongsheng Wang wrote:
> > > From: Wang Dongsheng <dongsheng.wang@freescale.com>
> > >
> > > Corenet_generic is a generic platform initialization. Those based on
> > > the corenet_generic board maybe need a particular initialize to
> > > enable/set some IP-Blocks. So add "Fix Generic Initialization" to solve
> > > this kind of special cases.
> >
> > I still don't understand what you mean by "fix". What are you fixing,
> > or what is fixed?
> >
> > There is no need for adding an infrastructure layer here. Just add a
> > new piece of code for t104x diu, and have it be called by an appropriate
> > initfunc.
> >
>
> "fix" is means to handle some boards those based on corenet_generic config file,
> But those boards may need some special handle. Perhaps these used to handle
> special feature codes not have an appropriate initfunc we cannot *just find*
> an appropriate place,
I'm not asking you to "just find" anything. I'm asking you to add an
initfunc in a standalone file.
> if more and more boards need to do this, at that time maybe *initfunc*
> looks very complicated.
They would each have their own initfunc. There is no reason to tie this
in with anything else.
> > > --- a/arch/powerpc/platforms/85xx/Kconfig
> > > +++ b/arch/powerpc/platforms/85xx/Kconfig
> > > @@ -269,6 +269,17 @@ config CORENET_GENERIC
> > > The following boards are supported for both 32bit and 64bit kernel:
> > > P5020 DS and P5040 DS
> > >
> > > +config FIX_GENERIC_PLATFORM_INIT
> > > + bool "Fix Generic Initialization"
> > > + depends on CORENET_GENERIC
> >
> > Why does this depend on CORENET_GENERIC?
> >
>
> Because CORENET_GENERIC is a multiboards file, This is designed to handle this situation.
This DIU code is going to be just as applicable to a custom T104x board
which may or may not use CORENET_GENERIC.
> > > + default y
> >
> > No.
> >
>
> Why not? This will not increase any redundant operations if there is not any boards need fix.
> You can see my fix.c code.
default y should not be used for hardware specific code.
-Scott
next prev parent reply other threads:[~2014-04-16 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 5:53 [PATCH v2 1/2] fsl/corenet_generic: add a particular initialization for platform Dongsheng Wang
2014-04-15 5:53 ` [PATCH v2 2/2] fsl/corenet_generic: add t104x platform diu special initialization Dongsheng Wang
2014-04-15 19:39 ` [PATCH v2 1/2] fsl/corenet_generic: add a particular initialization for platform Scott Wood
2014-04-16 2:58 ` Dongsheng.Wang
2014-04-16 19:36 ` Scott Wood [this message]
2014-04-24 6:43 ` Dongsheng.Wang
2014-04-24 18:46 ` Scott Wood
2014-04-24 18:47 ` Scott Wood
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=1397676986.28539.10.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=Dongsheng.Wang@freescale.com \
--cc=Jason.Jin@freescale.com \
--cc=haokexin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=prabhakar@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).