From: Prashanth K <prashanth.k@oss.qualcomm.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Simona Vetter <simona.vetter@ffwll.ch>,
Takashi Iwai <tiwai@suse.de>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: Increase the limit of USB_GADGET_VBUS_DRAW to 900mA
Date: Tue, 21 Jan 2025 09:50:08 +0530 [thread overview]
Message-ID: <1b1587e8-5c38-4138-a27a-1de71ff07ce3@oss.qualcomm.com> (raw)
In-Reply-To: <894f42a7-50a5-401e-a705-a06eafd6161d@rowland.harvard.edu>
On 20-01-25 08:17 pm, Alan Stern wrote:
> On Mon, Jan 20, 2025 at 04:47:02PM +0530, Prashanth K wrote:
>> Currently CONFIG_USB_GADGET_VBUS_DRAW limits the maximum current
>> drawn from Vbus to be up to 500mA. However USB gadget operating
>> in SuperSpeed or higher can draw up to 900mA. Also, MaxPower in
>> ConfigFS takes its default value from this config. Hence increase
>> the allowed range of CONFIG_USB_GADGET_VBUS_DRAW to 900mA.
>
> Is this the sort of thing that really needs to be a Kconfig option? Why
> not make the decision at runtime, based on the needs of the gadget or
> function drivers and the connection speed?
>
> Alan Stern
>
Right, set_config() in composite.c does this in runtime based on the
values of MaxPower (from configFS), VBUS_DRAW defconfig and speed.
If we don't set MaxPower from configFS, this config helps to set it
during compile time. In fact MaxPower in configFS takes its default
value from CONFIG_USB_GADGET_VBUS_DRAW . Sent this patch because Kconfig
has this limitation where it's only allowing values upto 500mA.
Regards,
Prashanth K
next prev parent reply other threads:[~2025-01-21 4:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 11:17 Prashanth K
2025-01-20 14:47 ` Alan Stern
2025-01-21 4:20 ` Prashanth K [this message]
2025-01-21 15:06 ` Alan Stern
2025-01-21 16:49 ` Prashanth K
2025-01-21 19:26 ` Alan Stern
2025-01-22 4:02 ` Prashanth K
2025-02-20 4:17 ` Prashanth K
2025-02-20 15:15 ` Alan Stern
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=1b1587e8-5c38-4138-a27a-1de71ff07ce3@oss.qualcomm.com \
--to=prashanth.k@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=simona.vetter@ffwll.ch \
--cc=stern@rowland.harvard.edu \
--cc=tiwai@suse.de \
/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®