From: "qiang.zhao@freescale.com" <qiang.zhao@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: "LeoLi@freescale.com" <LeoLi@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Xiaobo Xie <X.Xie@freescale.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2] QE: move qe code from arch/powerpc to drivers/soc
Date: Wed, 10 Sep 2014 03:38:18 +0000 [thread overview]
Message-ID: <fcf0691e6fe7410bb72ddb459da9a315@BLUPR03MB341.namprd03.prod.outlook.com> (raw)
In-Reply-To: <1410305198.24184.336.camel@snotra.buserror.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 3617 bytes --]
On Wed, 2014-09-10 at 07:27 -0500, Wood Scott-B07421 wrote:
> -----Original Message-----
> From: Wood Scott-B07421
> Sent: Wednesday, September 10, 2014 7:27 AM
> To: Zhao Qiang-B45475
> Cc: Li Yang-Leo-R58472; linuxppc-dev@lists.ozlabs.org; Xie Xiaobo-R63061;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2] QE: move qe code from arch/powerpc to drivers/soc
>
> On Tue, 2014-09-09 at 04:27 -0500, Zhao Qiang-B45475 wrote:
> > On Fri, 2014-09-05 at 06:47 AM, Wood Scott wrote:
> >
> >
> >
> > > Subject: Re: [PATCH v2] QE: move qe code from arch/powerpc to
> > > drivers/soc
> > >
> > > On Thu, 2014-09-04 at 13:06 +0800, Zhao Qiang wrote:
> > > > LS1 is arm cpu and it has qe ip block.
> > > > move qe code from platform directory to public directory.
> > > >
> > > > QE is an IP block integrates several comunications peripheral
> > > > controllers. It can implement a variety of applications, such as
> > > > uart, usb and tdm and so on.
> > > >
> > > > Signed-off-by: Zhao Qiang <B45475@freescale.com>
> > > > ---
> > > > Changes for v2:
> > > > - mv code to drivers/soc
> > >
> > > Who will be the maintainer of this code once it lives in
> > > drivers/soc, especially once it is no longer used only by PPC?
> >
> > I have no idea about that, can you explain why you want to know who
> will be the maintainer.
>
> Currently it falls within "Freescale PPC" which I maintain. This moves
> it out of arch/powerpc and is the first step towards making it not be
> PPC-specific. Whose tree are you expecting patches to drivers/soc/fsl-qe
> to go through?
How about network tree?
>
> > > > diff --git a/drivers/soc/qe/Kconfig b/drivers/soc/qe/Kconfig new
> > > > file mode 100644 index 0000000..8b03ca2
> > > > --- /dev/null
> > > > +++ b/drivers/soc/qe/Kconfig
> > > > @@ -0,0 +1,45 @@
> > > > +#
> > > > +# QE Communication options
> > > > +#
> > > > +config QUICC_ENGINE
> > > > + bool "Freescale QUICC Engine (QE) Support"
> > > > + depends on FSL_SOC && PPC32
> > > > + select PPC_LIB_RHEAP
> > > > + select CRC32
> > > > + help
> > > > + The QUICC Engine (QE) is a new generation of communications
> > > > + coprocessors on Freescale embedded CPUs (akin to CPM in
> older
> > > chips).
> > > > + Selecting this option means that you wish to build a kernel
> > > > + for a machine with a QE coprocessor.
> > > > +
> > > > +config QE_GPIO
> > > > + bool "QE GPIO support"
> > > > + depends on QUICC_ENGINE
> > > > + select ARCH_REQUIRE_GPIOLIB
> > > > + help
> > > > + Say Y here if you're going to use hardware that connects to
> the
> > > > + QE GPIOs.
> > > > +
> > > > +config UCC_SLOW
> > > > + bool
> > > > + default y if SERIAL_QE
> > > > + help
> > > > + This option provides qe_lib support to UCC slow
> > > > + protocols: UART, BISYNC, QMC
> > > > +
> > > > +config UCC_FAST
> > > > + bool
> > > > + default y if UCC_GETH
> > > > + help
> > > > + This option provides qe_lib support to UCC fast
> > > > + protocols: HDLC, Ethernet, ATM, transparent
> > > > +
> > > > +config UCC
> > > > + bool
> > > > + default y if UCC_FAST || UCC_SLOW
> > > > +
> > > > +config QE_USB
> > > > + bool
> > > > + default y if USB_FSL_QE
> > > > + help
> > > > + QE USB Controller support
> > >
> > > First could we give these names better namespacing?
> >
> > Add FSL as prefix?
>
> Yes.
If the names changed, there will be so a lot of changes.
Can I send another patch to change it?
>
> -Scott
>
Regards,
Zhao Qiang
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
prev parent reply other threads:[~2014-09-10 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 5:06 Zhao Qiang
2014-09-04 22:46 ` Scott Wood
2014-09-09 9:27 ` qiang.zhao
2014-09-09 23:26 ` Scott Wood
2014-09-10 3:38 ` qiang.zhao [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=fcf0691e6fe7410bb72ddb459da9a315@BLUPR03MB341.namprd03.prod.outlook.com \
--to=qiang.zhao@freescale.com \
--cc=LeoLi@freescale.com \
--cc=X.Xie@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@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
all inboxes | Powered by JetHome®