From: Selvarasu Ganesan <selvarasu.g@samsung.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: quic_jjohnson@quicinc.com, kees@kernel.org,
abdul.rahim@myyahoo.com, m.grzeschik@pengutronix.de,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
jh0801.jung@samsung.com, dh10.jung@samsung.com,
naushad@samsung.com, akash.m5@samsung.com, rc93.raju@samsung.com,
taehyun.cho@samsung.com, hongpooh.kim@samsung.com,
eomji.oh@samsung.com, shijie.cai@samsung.com,
alim.akhtar@samsung.com, stable@vger.kernel.org,
thiagu.r@samsung.com
Subject: Re: [PATCH] usb: gadget: f_midi: Fixing wMaxPacketSize exceeded issue during MIDI bind retries
Date: Sat, 18 Jan 2025 11:39:58 +0530 [thread overview]
Message-ID: <52a0dd32-59be-4b41-859d-a8b4c8787792@samsung.com> (raw)
In-Reply-To: <2025011726-hydration-nephew-0d65@gregkh>
On 1/17/2025 4:35 PM, Greg KH wrote:
> On Thu, Jan 16, 2025 at 10:49:24AM +0530, Selvarasu Ganesan wrote:
>> On 12/21/2024 11:37 PM, Selvarasu Ganesan wrote:
>>> On 12/20/2024 8:45 PM, Greg KH wrote:
>>>> On Fri, Dec 20, 2024 at 07:02:06PM +0530, Selvarasu Ganesan wrote:
>>>>> On 12/20/2024 5:54 PM, Greg KH wrote:
>>>>>> On Wed, Dec 18, 2024 at 03:51:50PM +0530, Selvarasu Ganesan wrote:
>>>>>>> On 12/18/2024 11:01 AM, Greg KH wrote:
>>>>>>>> On Sun, Dec 08, 2024 at 08:53:20PM +0530, Selvarasu Ganesan wrote:
>>>>>>>>> The current implementation sets the wMaxPacketSize of bulk in/out
>>>>>>>>> endpoints to 1024 bytes at the end of the f_midi_bind function.
>>>>>>>>> However,
>>>>>>>>> in cases where there is a failure in the first midi bind attempt,
>>>>>>>>> consider rebinding.
>>>>>>>> What considers rebinding? Your change does not modify that.
>>>>>>> Hi Greg,
>>>>>>> Thanks for your review comments.
>>>>>>>
>>>>>>>
>>>>>>> Here the term "rebind" in this context refers to attempting to
>>>>>>> bind the
>>>>>>> MIDI function a second time in certain scenarios.
>>>>>>> The situations where rebinding is considered include:
>>>>>>>
>>>>>>> * When there is a failure in the first UDC write attempt,
>>>>>>> which may be
>>>>>>> caused by other functions bind along with MIDI
>>>>>>> * Runtime composition change : Example : MIDI,ADB to MIDI. Or
>>>>>>> MIDI to
>>>>>>> MIDI,ADB
>>>>>>>
>>>>>>> The issue arises during the second time the "f_midi_bind" function is
>>>>>>> called. The problem lies in the fact that the size of
>>>>>>> "bulk_in_desc.wMaxPacketSize" is set to 1024 during the first call,
>>>>>>> which exceeds the hardware capability of the dwc3 TX/RX FIFO
>>>>>>> (ep->maxpacket_limit = 512).
>>>>>> Ok, but then why not properly reset ALL of the options/values when a
>>>>>> failure happens, not just this one when the initialization happens
>>>>>> again? Odds are you might be missing the change of something else
>>>>>> here
>>>>>> as well, right?
>>>>> Are you suggesting that we reset the entire value of
>>>>> usb_endpoint_descriptor before call usb_ep_autoconfig? If so, Sorry
>>>>> I am
>>>>> not clear on your reasoning for wanting to reset all options/values.
>>>>> After all, all values will be overwritten
>>>>> afterusb_ep_autoconfig.Additionally, the wMaxPacketSize is the only
>>>>> value being checked during the EP claim process (usb_ep_autoconfig),
>>>>> and
>>>>> it has caused issues where claiming wMaxPacketSize is grater than
>>>>> ep->maxpacket_limit.
>>>> Then fix up that value on failure, if things fail you should reset it
>>>> back to a "known good state", right? And what's wrong with resetting
>>>> all of the values anyway, wouldn't that be the correct thing to do?
>>> Yes, It's back to known good state if we reset wMaxPacketSize. There
>>> is no point to reset all values in the usb endpoint descriptor
>>> structure as all the member of this structure are predefined value
>>> except wMaxPacketSize and bEndpointAddress. The bEndpointAddress is
>>> obtain as part of usb_ep_autoconfig.
>>>
>>> static struct usb_endpoint_descriptor bulk_out_desc = {
>>> .bLength = USB_DT_ENDPOINT_AUDIO_SIZE,
>>> .bDescriptorType = USB_DT_ENDPOINT,
>>> .bEndpointAddress = USB_DIR_OUT,
>>> .bmAttributes = USB_ENDPOINT_XFER_BULK,
>>> };
>>>
>> HI Greg,
>>
>> Gentle remainder for your further comments or suggestions on this.
> Sorry, I don't remember, it was thousands of patches reviewed ago. If
> you feel your submission was correct, and no changes are needed, resend
> with an expanded changelog text to help explain things so I don't have
> the same questions again.
>
> thanks,
>
> greg k-h
Hi Greg,
I understand. Thanks for your update.
Yes, no changes are needed. I updated new version with expanded
changelog in below link.
https://lore.kernel.org/all/20250118060134.927-1-selvarasu.g@samsung.com/
Thanks,
Selva
>
next prev parent reply other threads:[~2025-01-18 6:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241208152338epcas5p4fde427bb4467414417083221067ac7ab@epcas5p4.samsung.com>
2024-12-08 15:23 ` [PATCH] usb: gadget: f_midi: Fixing wMaxPacketSize exceeded issue during MIDI bind retries Selvarasu Ganesan
2024-12-10 9:53 ` Selvarasu Ganesan
2024-12-10 10:18 ` Greg KH
2024-12-10 14:11 ` Selvarasu Ganesan
2024-12-10 14:25 ` Greg KH
2024-12-12 12:28 ` Selvarasu Ganesan
2024-12-18 5:31 ` Greg KH
2024-12-18 10:21 ` Selvarasu Ganesan
2024-12-18 15:51 ` Alan Stern
2024-12-19 4:06 ` Selvarasu Ganesan
2024-12-20 12:24 ` Greg KH
2024-12-20 13:32 ` Selvarasu Ganesan
2024-12-20 15:15 ` Greg KH
2024-12-21 18:07 ` Selvarasu Ganesan
2025-01-06 5:17 ` Selvarasu Ganesan
2025-01-16 5:19 ` Selvarasu Ganesan
2025-01-17 11:05 ` Greg KH
2025-01-18 6:09 ` Selvarasu Ganesan [this message]
[not found] <CGME20241208151349epcas5p1a94ca45020318f54885072d4987160b3@epcas5p1.samsung.com>
2024-12-08 15:13 ` Faraz Ata
2024-12-08 15:28 ` Selvarasu Ganesan
2024-12-08 15:48 ` Greg KH
2024-12-08 16:00 ` Selvarasu Ganesan
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=52a0dd32-59be-4b41-859d-a8b4c8787792@samsung.com \
--to=selvarasu.g@samsung.com \
--cc=abdul.rahim@myyahoo.com \
--cc=akash.m5@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=dh10.jung@samsung.com \
--cc=eomji.oh@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=hongpooh.kim@samsung.com \
--cc=jh0801.jung@samsung.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=naushad@samsung.com \
--cc=quic_jjohnson@quicinc.com \
--cc=rc93.raju@samsung.com \
--cc=shijie.cai@samsung.com \
--cc=stable@vger.kernel.org \
--cc=taehyun.cho@samsung.com \
--cc=thiagu.r@samsung.com \
/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