From: Greg KH <greg@kroah.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linux-usb@vger.kernel.org,
Joel Stanley <joel.stanley@au1.ibm.com>,
Andrew Jeffery <andrew@aj.id.au>
Subject: [v3,2/3] usb/gadget: Add an EP dispose() callback for EP lifetime tracking
Date: Mon, 22 Jan 2018 15:33:32 +0100 [thread overview]
Message-ID: <20180122143332.GB13897@kroah.com> (raw)
On Fri, Jan 12, 2018 at 05:50:03PM +1100, Benjamin Herrenschmidt wrote:
> Some UDC may want to allocate endpoints dynamically, either because
> the HW supports an arbitrary large number or because (like the Aspeed
> BMC SoCs), the pool of HW endpoints is shared between multiple gadgets.
>
> The allocation side can be done rather easily using the existing
> match_ep() UDC hook.
>
> However we have no good place to "free" them.
>
> This implements a "simple" variant of this, which calls an EP dispose
> callback on all EPs associated with a gadget when the composite device
> gets unbound.
>
> This is required by my upcoming Aspeed vHub driver.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
> drivers/usb/gadget/composite.c | 8 ++++++++
> include/linux/usb/gadget.h | 1 +
> 2 files changed, 9 insertions(+)
Any reason you aren't sending these to the maintainer of the usb gadget
subsystem? get_maintainer.pl is your friend :)
thanks,
greg k-h
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-01-22 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 14:33 Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-01-22 22:25 [v3,2/3] usb/gadget: Add an EP dispose() callback for EP lifetime tracking Benjamin Herrenschmidt
2018-01-12 6:50 Benjamin Herrenschmidt
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=20180122143332.GB13897@kroah.com \
--to=greg@kroah.com \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=joel.stanley@au1.ibm.com \
--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).