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 22:19:08 +0530 [thread overview]
Message-ID: <d308300f-2559-4d13-8d15-5a2416ac00c9@oss.qualcomm.com> (raw)
In-Reply-To: <e36303c0-9d1f-4c66-bc40-891958507275@rowland.harvard.edu>
On 21-01-25 08:36 pm, Alan Stern wrote:
> On Tue, Jan 21, 2025 at 09:50:08AM +0530, Prashanth K wrote:
>>
>>
>> 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.
>
> Why does MaxPower need to be set at compile time? Why not set it at
> runtime instead?
>
> If MaxPower gets set at runtime then it can take its default value to be
> 500 mA or 900 mA depending on the connection speed. There will be no
> need for CONFIG_USB_GAGDGET_VBUS_DRAW.
>
Yes, agreed. Can we mark CONFIG_USB_GAGDGET_VBUS_DRAW as legacy and
maybe also avoid configfs/composite from using it?
> You are trying to improve a compile-time limitation on a quantity which
> isn't known until runtime. The whole idea of doing it that way is
> fundamentally wrong. You shouldn't try to improve it a little, you
> should fix the basic mistake by doing everything at runtime.
>
> Alan Stern
>
Regards,
Prashanth K
next prev parent reply other threads:[~2025-01-21 16:49 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
2025-01-21 15:06 ` Alan Stern
2025-01-21 16:49 ` Prashanth K [this message]
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=d308300f-2559-4d13-8d15-5a2416ac00c9@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®