linux-kernel - Re: [PATCH] usb: gadget: lpc32xx_udc: Port to new start/stop interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5030E0A1.8040401@antcom.de>
Date:	Sun, 19 Aug 2012 14:48:33 +0200
From:	Roland Stigge <stigge@...com.de>
To:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
CC:	balbi@...com, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org,
	arnd@...db.de, aletes.xgr@...il.com, kevin.wells@....com,
	srinivas.bakki@....com
Subject: Re: [PATCH] usb: gadget: lpc32xx_udc: Port to new start/stop interface

On 17/08/12 13:39, Sebastian Andrzej Siewior wrote:
>>                  .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?

It's assigned dynamically at runtime, depending on RX or TX.

>>                  .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?

The latter, see LPC32xx user manual, 14.1.2.

Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/