From: Scott Wood <scottwood@freescale.com>
To: Zhao Qiang <B45475@freescale.com>
Cc: B07421@freescale.com, R63061@freescale.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: qe: move qe from arch/powerpc to drivers
Date: Tue, 29 Jul 2014 19:19:23 -0500 [thread overview]
Message-ID: <20140730001923.GA4151@home.buserror.net> (raw)
In-Reply-To: <1403580712-30153-1-git-send-email-B45475@freescale.com>
On Tue, Jun 24, 2014 at 11:31:52AM +0800, Zhao Qiang wrote:
> ls1 has qe and ls1 has arm cpu.
> move qe from arch/powerpc to drivers.
>
> Signed-off-by: Zhao Qiang <B45475@freescale.com>
This is a very terse changelog. Explain more about what QE is, and what
this patch accomplishes (it doesn't seem to get rid of the PPC
dependency, just moving code at this stage)
I don't see a MAINTAINERS update for the new path. Who is going to
maintain it?
I don't think drivers/qe is the right place for it. Directories directly
under drivers/ tend to be for classes of devices, not instances. In any
case, LKML should be CCed when creating a new directory directly under
drivers/ or under a subdirectory of drivers/ that doesn't have its own
mailing list.
This came up before, without a resolution. See:
http://www.spinics.net/lists/kernel/msg1621335.html
> diff --git a/arch/powerpc/platforms/83xx/km83xx.c b/arch/powerpc/platforms/83xx/km83xx.c
> index bf4c447..22c0d6d 100644
> --- a/arch/powerpc/platforms/83xx/km83xx.c
> +++ b/arch/powerpc/platforms/83xx/km83xx.c
> @@ -37,8 +37,8 @@
> #include <asm/udbg.h>
> #include <sysdev/fsl_soc.h>
> #include <sysdev/fsl_pci.h>
> -#include <asm/qe.h>
> -#include <asm/qe_ic.h>
> +#include <linux/qe.h>
> +#include <linux/qe_ic.h>
If you're moving it out of asm/ please give it an fsl prefix.
> diff --git a/drivers/qe/Kconfig b/drivers/qe/Kconfig
> new file mode 100644
> index 0000000..dc16e9a
> --- /dev/null
> +++ b/drivers/qe/Kconfig
> @@ -0,0 +1,35 @@
> +#
> +# QE Communication options
> +#
> +menuconfig 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.
> +
> +if QUICC_ENGINE
> +
> +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
> +
> +endif
These config options could use better namespacing.
-Scott
next prev parent reply other threads:[~2014-07-30 0:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 3:31 [PATCH] qe: move qe from arch/powerpc to drivers Zhao Qiang
2014-07-30 0:19 ` Scott Wood [this message]
2014-08-06 8:53 ` qiang.zhao
2014-08-06 20:15 ` Scott Wood
2014-08-07 9:15 ` qiang.zhao
2014-08-07 17:15 ` Scott Wood
2014-08-07 18:57 ` Timur Tabi
2014-08-07 20:08 ` Scott Wood
2014-08-07 20:09 ` Timur Tabi
2014-08-07 20:11 ` Scott Wood
2014-08-07 20:13 ` Timur Tabi
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=20140730001923.GA4151@home.buserror.net \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B45475@freescale.com \
--cc=R63061@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).