From: <cristian.birsan@microchip.com>
To: <nicolas.ferre@atmel.com>, <balbi@kernel.org>,
<gregkh@linuxfoundation.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <ludovic.desroches@atmel.com>,
<alexandre.belloni@free-electrons.com>,
<boris.brezillon@free-electrons.com>,
Cristian Birsan <cristian.birsan@microchip.com>
Subject: [PATCH linux-next v2 0/1] usb: gadget: udc: atmel: Update endpoint allocation scheme
Date: Mon, 23 Jan 2017 16:45:58 +0200 [thread overview]
Message-ID: <1485182759-17165-1-git-send-email-cristian.birsan@microchip.com> (raw)
From: Cristian Birsan <cristian.birsan@microchip.com>
Hi,
This patch updates the usb endpoint allocation scheme for atmel usba
driver to make sure all endpoints are allocated in order. This requirement
comes from the datasheet of the controller.
The allocation scheme is decided by fifo_mode parameter. For fifo_mode = 0
the driver tries to autoconfigure the endpoints fifo size. All other modes
contain fixed configurations optimized for different purposes. The idea is
somehow similar with the approach used on musb driver.
Please let me know if you have any comments or suggestions.
Changes since v1:
- Minor reworks based on received fedback
Kind regards,
Cristian
Cristian Birsan (1):
usb: gadget: udc: atmel: Update endpoint allocation scheme
drivers/usb/gadget/udc/Kconfig | 14 ++
drivers/usb/gadget/udc/atmel_usba_udc.c | 236 +++++++++++++++++++++++++++-----
drivers/usb/gadget/udc/atmel_usba_udc.h | 10 +-
3 files changed, 227 insertions(+), 33 deletions(-)
--
2.7.4
next reply other threads:[~2017-01-23 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 14:45 cristian.birsan [this message]
2017-01-23 14:45 ` [PATCH linux-next v2 1/1] " cristian.birsan
2017-01-26 15:02 ` Nicolas Ferre
2017-01-27 9:07 ` Felipe Balbi
2017-01-27 13:47 ` Cristian Birsan
2017-01-27 14:56 ` Nicolas Ferre
2017-01-27 15:01 ` Felipe Balbi
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=1485182759-17165-1-git-send-email-cristian.birsan@microchip.com \
--to=cristian.birsan@microchip.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=balbi@kernel.org \
--cc=boris.brezillon@free-electrons.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.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®