From: Ruslan Bilovol <ruslan.bilovol@gmail.com>
To: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
balbi@ti.com, gregkh@linuxfoundation.org
Cc: andrzej.p@samsung.com
Subject: [PATCH 0/2] usb/gadget: independent registration of gadgets and gadget
Date: Thu, 29 Jan 2015 03:25:32 +0200 [thread overview]
Message-ID: <1422494734-9499-1-git-send-email-ruslan.bilovol@gmail.com> (raw)
This patchset adds independent registration of gadgets
and gadget drivers to udc-core. This is very useful for
built-in modules into kernel case since it's possible
situation that gadget driver is probing at a time
when no gadgets are registered in udc-core.
In this case instead of silently failing without
of any attempt to recover, with independent registration
of gadgets and gadget drivers there is no matter
in which order gadgets and gadget drivers are
probed/registered.
Also it's possible to add/remove gadgets or gadget
drivers many times since it's now correctly handled
by the udc-core
This patch has side-effect on gadget drivers that had
__init/__exit attributes on some paths like bind/unbind
and (since bind/unbind may happen at any time) should
not use them now. This is covered by second patch
(please let me know if I need to break it into separate
patches for each gadget driver)
Ruslan Bilovol (2):
usb: gadget: udc-core: independent registration of gadgets and gadget
drivers
usb: gadget: legacy: don't use __init/__exit attributes for
bind/unbind path
drivers/usb/gadget/legacy/acm_ms.c | 6 +-
drivers/usb/gadget/legacy/audio.c | 6 +-
drivers/usb/gadget/legacy/cdc2.c | 6 +-
drivers/usb/gadget/legacy/dbgp.c | 2 +-
drivers/usb/gadget/legacy/ether.c | 8 +--
drivers/usb/gadget/legacy/gmidi.c | 6 +-
drivers/usb/gadget/legacy/hid.c | 6 +-
drivers/usb/gadget/legacy/mass_storage.c | 4 +-
drivers/usb/gadget/legacy/multi.c | 16 ++---
drivers/usb/gadget/legacy/ncm.c | 6 +-
drivers/usb/gadget/legacy/nokia.c | 6 +-
drivers/usb/gadget/legacy/printer.c | 6 +-
drivers/usb/gadget/legacy/serial.c | 2 +-
drivers/usb/gadget/legacy/webcam.c | 4 +-
drivers/usb/gadget/legacy/zero.c | 2 +-
drivers/usb/gadget/udc/udc-core.c | 112 ++++++++++++++++++++++++++++---
16 files changed, 147 insertions(+), 51 deletions(-)
--
1.9.1
next reply other threads:[~2015-01-29 3:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 1:25 Ruslan Bilovol [this message]
2015-01-29 1:25 ` [PATCH 1/2] usb: gadget: udc-core: independent registration of gadgets and gadget drivers Ruslan Bilovol
2015-01-29 15:56 ` Alan Stern
2015-02-08 19:04 ` Ruslan Bilovol
2015-02-09 8:46 ` Peter Chen
2015-02-09 16:35 ` Alan Stern
2015-02-09 18:06 ` Krzysztof Opasiak
2015-02-09 18:17 ` Krzysztof Opasiak
2015-02-09 20:00 ` Alan Stern
2015-02-09 23:46 ` Ruslan Bilovol
2015-02-10 8:47 ` Krzysztof Opasiak
2015-02-15 22:43 ` Ruslan Bilovol
2015-02-16 8:07 ` Andrzej Pietrasiewicz
2015-02-17 21:02 ` Ruslan Bilovol
2015-02-18 7:21 ` Andrzej Pietrasiewicz
2015-02-15 22:40 ` Ruslan Bilovol
2015-01-29 1:25 ` [PATCH 2/2] usb: gadget: legacy: don't use __init/__exit attributes for bind/unbind path Ruslan Bilovol
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=1422494734-9499-1-git-send-email-ruslan.bilovol@gmail.com \
--to=ruslan.bilovol@gmail.com \
--cc=andrzej.p@samsung.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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).