From: Wesley Cheng <wcheng@codeaurora.org>
To: Jack Pham <jackp@codeaurora.org>
Cc: balbi@kernel.org, gregkh@linuxfoundation.org, robh+dt@kernel.org,
agross@kernel.org, bjorn.andersson@linaro.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
peter.chen@nxp.com
Subject: Re: [PATCH v6 1/4] usb: gadget: udc: core: Introduce check_config to verify USB configuration
Date: Mon, 25 Jan 2021 17:01:46 -0800 [thread overview]
Message-ID: <f5d04121-fd8c-9644-59c0-0ee8aa132de0@codeaurora.org> (raw)
In-Reply-To: <20210122051743.GE31406@jackp-linux.qualcomm.com>
On 1/21/2021 9:17 PM, Jack Pham wrote:
> Hi Wesley,
>
> On Thu, Jan 21, 2021 at 08:01:37PM -0800, Wesley Cheng wrote:
>> Some UDCs may have constraints on how many high bandwidth endpoints it can
>> support in a certain configuration. This API allows for the composite
>> driver to pass down the total number of endpoints to the UDC so it can verify
>> it has the required resources to support the configuration.
>>
>> Signed-off-by: Wesley Cheng <wcheng@codeaurora.org>
>> ---
>> drivers/usb/gadget/udc/core.c | 9 +++++++++
>> include/linux/usb/gadget.h | 2 ++
>> 2 files changed, 11 insertions(+)
>>
>> diff --git a/drivers/usb/gadget/udc/core.c b/drivers/usb/gadget/udc/core.c
>> index 4173acd..469962f 100644
>> --- a/drivers/usb/gadget/udc/core.c
>> +++ b/drivers/usb/gadget/udc/core.c
>> @@ -1003,6 +1003,15 @@ int usb_gadget_ep_match_desc(struct usb_gadget *gadget,
>> }
>> EXPORT_SYMBOL_GPL(usb_gadget_ep_match_desc);
>>
>> +int usb_gadget_check_config(struct usb_gadget *gadget, unsigned long ep_map)
>
> You should probably add a kernel-doc for this function.
>
> Jack
>
Hi Jack,
Sure, I'll update a bit more about how this API can be used.
Thanks
Wesley Cheng
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2021-01-26 10:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 4:01 [PATCH v6 0/4] Re-introduce TX FIFO resize for larger EP bursting Wesley Cheng
2021-01-22 4:01 ` [PATCH v6 1/4] usb: gadget: udc: core: Introduce check_config to verify USB configuration Wesley Cheng
2021-01-22 5:17 ` Jack Pham
2021-01-26 1:01 ` Wesley Cheng [this message]
2021-01-22 16:24 ` Alan Stern
2021-01-26 1:02 ` Wesley Cheng
2021-01-22 4:01 ` [PATCH v6 2/4] usb: gadget: configfs: Check USB configuration before adding Wesley Cheng
2021-01-22 4:01 ` [PATCH v6 3/4] usb: dwc3: Resize TX FIFOs to meet EP bursting requirements Wesley Cheng
2021-01-22 17:12 ` Bjorn Andersson
2021-01-26 1:14 ` Wesley Cheng
2021-01-26 1:55 ` Bjorn Andersson
2021-01-26 4:32 ` Wesley Cheng
2021-01-26 5:15 ` Bjorn Andersson
2021-01-28 23:08 ` Wesley Cheng
2021-01-23 0:15 ` Thinh Nguyen
2021-01-26 9:51 ` Wesley Cheng
2021-01-26 20:43 ` Thinh Nguyen
2021-01-26 23:26 ` Wesley Cheng
2021-01-27 1:47 ` Thinh Nguyen
2021-01-22 4:01 ` [PATCH v6 4/4] arm64: boot: dts: qcom: sm8150: Enable dynamic TX FIFO resize logic Wesley Cheng
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=f5d04121-fd8c-9644-59c0-0ee8aa132de0@codeaurora.org \
--to=wcheng@codeaurora.org \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jackp@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.com \
--cc=robh+dt@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).