From: Felipe Balbi <balbi@ti.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Ruslan Bilovol <ruslan.bilovol@gmail.com>, <balbi@ti.com>,
<k.opasiak@samsung.com>, <peter.chen@freescale.com>,
<linux-kernel@vger.kernel.org>, <gregkh@linuxfoundation.org>,
<andrzej.p@samsung.com>
Subject: Re: [PATCH v2 1/2] usb: gadget: udc-core: independent registration of gadgets and gadget drivers
Date: Mon, 16 Feb 2015 07:19:35 -0600 [thread overview]
Message-ID: <20150216131935.GE28983@saruman.tx.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1502151805290.5771-100000@netrider.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
On Sun, Feb 15, 2015 at 06:23:02PM -0500, Alan Stern wrote:
> On Mon, 16 Feb 2015, Ruslan Bilovol wrote:
>
> > Change behavior during registration of gadgets and
> > gadget drivers in udc-core. Instead of previous
> > approach when for successful probe of usb gadget driver
> > at least one usb gadget should be already registered
> > use another one where gadget drivers and gadgets
> > can be registered in udc-core independently.
> >
> > Independent registration of gadgets and gadget drivers
> > is useful for built-in into kernel gadget and gadget
> > driver case - because it's possible that gadget is
> > really probed only on late_init stage (due to deferred
> > probe) whereas gadget driver's probe is silently failed
> > on module_init stage due to no any UDC added.
> >
> > Also it is useful for modules case - now there is no
> > difference what module to insert first: gadget module
> > or gadget driver one.
> >
> > Signed-off-by: Ruslan Bilovol <ruslan.bilovol@gmail.com>
> > ---
> > drivers/usb/gadget/udc/udc-core.c | 77 +++++++++++++++++++++++++++++++++++++--
> > 1 file changed, 74 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/usb/gadget/udc/udc-core.c b/drivers/usb/gadget/udc/udc-core.c
> > index 5a81cb0..71b6942 100644
> > --- a/drivers/usb/gadget/udc/udc-core.c
> > +++ b/drivers/usb/gadget/udc/udc-core.c
> > @@ -46,10 +46,18 @@ struct usb_udc {
> > struct list_head list;
> > };
> >
> > +struct pending_gadget_driver {
> > + struct usb_gadget_driver *driver;
> > + char *udc_name;
> > + struct list_head list;
> > +};
>
> Don't make this a separate structure. It should be embedded in the
> usb_gadget_driver structure. This will make a lot of the changes
> below much simpler.
right, also when resending, make sure to Cc linux-usb as well.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-16 13:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 22:58 [PATCH v2 0/2] usb/gadget: independent registration of gadgets and gadget Ruslan Bilovol
2015-02-15 22:58 ` [PATCH v2 1/2] usb: gadget: udc-core: independent registration of gadgets and gadget drivers Ruslan Bilovol
2015-02-15 23:23 ` Alan Stern
2015-02-16 13:19 ` Felipe Balbi [this message]
2015-02-17 21:00 ` Ruslan Bilovol
2015-02-15 22:58 ` [PATCH v2 2/2] usb: gadget: legacy: don't use __init/__exit attributes for bind/unbind path Ruslan Bilovol
2015-02-15 23:04 ` [PATCH v2 0/2] usb/gadget: independent registration of gadgets and gadget Alan Stern
2015-02-17 20:24 ` 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=20150216131935.GE28983@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=andrzej.p@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=k.opasiak@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.chen@freescale.com \
--cc=ruslan.bilovol@gmail.com \
--cc=stern@rowland.harvard.edu \
/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®