From: Paul Bolle <pebolle@tiscali.nl>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
linux-sh@vger.kernel.org, gregkh@linuxfoundation.org,
horms@verge.net.au, geert@linux-m68k.org,
laurent.pinchart@ideasonboard.com, olof@lixom.net,
dan.carpenter@oracle.com
Subject: Re: [PATCH v3 01/05] staging: emxx_udc: Add Emma Mobile USB Gadget driver
Date: Fri, 20 Jun 2014 08:22:20 +0000 [thread overview]
Message-ID: <1403252540.22857.20.camel@x220> (raw)
In-Reply-To: <20140606104417.4423.38999.sendpatchset@w520>
Magnus,
On Fri, 2014-06-06 at 19:44 +0900, Magnus Damm wrote:
> From: Magnus Damm <damm+renesas@opensource.se>
>
> Add the emxx_udc driver to staging based on an old linux-2.6.35.7
> android tree. The driver has been brushed up slightly to complile
> but it is still in great need of cleanup.
>
> At this point DT bindings are clearly lacking and I doubt that the
> driver even can run with multiple instances (global variables, hurray!).
>
> Signed-off-by: Magnus Damm <damm+renesas@opensource.se>
> ---
This patch appeared in linux-next (ie, next-20140620).
>[...]
> --- /dev/null
> +++ work/drivers/staging/emxx_udc/emxx_udc.h 2014-05-22 12:21:03.000000000 +0900
> @@ -0,0 +1,662 @@
>[...]
> +/*------- (0x1010) EPCTR Register */
> +#define DIRPD BIT12 /* RW */
> +
> +#define VBUS_LEVEL BIT08 /* R */
> +
> +#define PLL_RESUME BIT05 /* RW */
> +#define PLL_LOCK BIT04 /* R */
> +
> +#ifdef CONFIG_MACH_EMGR
> +#define PLL_RST BIT02 /* RW */
> +#endif
There's no Kconfig symbol MACH_EMGR. There's also no preprocessor define
of CONFIG_MACH_EMGR. Even web searches didn't tell me what MACH_EMGR
could be. Anyhow, this check always evaluates to false. Should I draft a
trivial patch to remove it?
But PLL_RST is unused too. Would you like to keep it?
(I didn't catch this when I first received this patch. One needs to
parse the entire tree to find stuff like this, and there are way too
many patchsets flying by to do treewide searches for all of them. So I
just try to keep up with linux-next, to at least catch things before
they enter mainline.)
Paul Bolle
prev parent reply other threads:[~2014-06-20 8:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 10:44 [PATCH v3 00/05] staging: Emma Mobile USB driver and KZM9D board code V3 Magnus Damm
2014-06-06 10:44 ` [PATCH v3 02/05] staging: emxx_udc: I/O memory and IRQ resource support Magnus Damm
2014-06-06 10:44 ` [PATCH v3 03/05] staging: emxx_udc: Add TODO file Magnus Damm
2014-06-06 10:44 ` [PATCH v3 04/05] staging: board: Initial board staging support Magnus Damm
2014-06-06 10:44 ` [PATCH v3 05/05] staging: board: kzm9d: Board staging support for emxx_udc Magnus Damm
2014-06-06 15:39 ` [PATCH v3 00/05] staging: Emma Mobile USB driver and KZM9D board code V3 Greg KH
2014-06-09 5:14 ` Magnus Damm
2014-06-10 1:57 ` Simon Horman
[not found] ` <20140606104417.4423.38999.sendpatchset@w520>
2014-06-20 8:22 ` Paul Bolle [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=1403252540.22857.20.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
/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).