From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Roland Stigge <stigge@antcom.de>
Cc: balbi@ti.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
arnd@arndb.de, aletes.xgr@gmail.com, kevin.wells@nxp.com,
srinivas.bakki@nxp.com
Subject: Re: [PATCH] usb: gadget: lpc32xx_udc: Port to new start/stop interface
Date: Fri, 17 Aug 2012 13:39:21 +0200 [thread overview]
Message-ID: <502E2D69.3040302@linutronix.de> (raw)
In-Reply-To: <502E2BD4.5090803@antcom.de>
On 08/17/2012 01:32 PM, Roland Stigge wrote:
> How about the following: Below, I show how the initialization of the
> current controller is done (statically). Removing this struct
> initialization completely would make the code much uglier, introducing
> many individual assignments.
I said what I had to say, I leave it up to Felipe.
> static struct lpc32xx_udc controller = {
> .gadget = {
> .ops =&lpc32xx_udc_ops,
> .ep0 =&controller.ep[0].ep,
> .name = driver_name,
> .dev = {
> .init_name = "gadget",
> .release = nop_release,
> }
> },
> .ep[0] = {
> .ep = {
> .name = "ep0",
> .ops =&lpc32xx_ep_ops,
> },
> .udc =&controller,
> .maxpacket = 64,
> .hwep_num_base = 0,
> .hwep_num = 0, /* Can be 0 or 1, has special
> handling */
Can it be 0 or 1 or has it to be 0? Who would change and why?
> .lep = 0,
> .eptype = EP_CTL_TYPE,
> },
> .ep[1] = {
> .ep = {
> .name = "ep1-int",
> .ops =&lpc32xx_ep_ops,
> },
> .udc =&controller,
> .maxpacket = 64,
> .hwep_num_base = 2,
> .hwep_num = 0, /* 2 or 3, will be set later */
Why not now?
> .lep = 1,
> .eptype = EP_INT_TYPE,
Do you have any restrictions on these endpoints? I mean can you pick
any endpoints for BULK/INT/ISO or have they been pre-defined by HW?
Sebastian
next prev parent reply other threads:[~2012-08-17 11:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 15:34 [PATCH] usb: gadget: lpc32xx_udc: Port to new start/stop interface Roland Stigge
2012-08-16 16:05 ` Sebastian Andrzej Siewior
2012-08-16 16:16 ` Roland Stigge
2012-08-17 9:10 ` Roland Stigge
2012-08-17 9:42 ` Sebastian Andrzej Siewior
2012-08-17 10:52 ` Felipe Balbi
2012-08-19 12:33 ` Roland Stigge
2012-08-20 7:07 ` Sebastian Andrzej Siewior
2012-08-20 8:11 ` Roland Stigge
2012-08-17 10:51 ` Felipe Balbi
2012-08-17 11:01 ` Sebastian Andrzej Siewior
2012-08-17 11:02 ` Felipe Balbi
2012-08-17 11:28 ` Sebastian Andrzej Siewior
2012-08-17 11:32 ` Roland Stigge
2012-08-17 11:39 ` Sebastian Andrzej Siewior [this message]
2012-08-19 12:48 ` Roland Stigge
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=502E2D69.3040302@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=aletes.xgr@gmail.com \
--cc=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=kevin.wells@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=srinivas.bakki@nxp.com \
--cc=stigge@antcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox