From: 'Greg Kroah-Hartman' <gregkh@linuxfoundation.org>
To: linyyuan@codeaurora.org
Cc: 'Felipe Balbi' <balbi@kernel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: eem: fix command packet transfer issue
Date: Thu, 10 Jun 2021 08:50:57 +0200 [thread overview]
Message-ID: <YMG2UWeqodfTRRnQ@kroah.com> (raw)
In-Reply-To: <000201d75dbf$58d1cc40$0a7564c0$@codeaurora.org>
On Thu, Jun 10, 2021 at 02:10:40PM +0800, linyyuan@codeaurora.org wrote:
> From: Linyu Yuan <linyyuan@codeaurora.com>
>
> there is following warning,
> [<ffffff8008905a94>] dwc3_gadget_ep_queue+0x1b4/0x1c8
> [<ffffff800895ec9c>] usb_ep_queue+0x3c/0x120
> [<ffffff80089677a0>] eem_unwrap+0x180/0x330
> [<ffffff80089634f8>] rx_complete+0x70/0x230
> [<ffffff800895edbc>] usb_gadget_giveback_request+0x3c/0xe8
> [<ffffff8008901e7c>] dwc3_gadget_giveback+0xb4/0x190
> [<ffffff8008905254>] dwc3_endpoint_transfer_complete+0x32c/0x410
> [<ffffff80089060fc>] dwc3_bh_work+0x654/0x12e8
> [<ffffff80080c63fc>] process_one_work+0x1d4/0x4a8
> [<ffffff80080c6720>] worker_thread+0x50/0x4a8
> [<ffffff80080cc8e8>] kthread+0xe8/0x100
> [<ffffff8008083980>] ret_from_fork+0x10/0x50
> request ffffffc0716bf200 belongs to 'ep0out'
>
> when gadget receive a eem command packet from host, it need to response,
> but queue usb request to wrong endpoint.
What is the full warning here? THe above traceback is a bit odd and
does not show what is happening.
> fix it by queue usb request to eem IN endpoint and allow host read it.
I do not understand how this matches up with your kernel patch, when you
resend this, can you please expand on this and make it more obvious what
you are doing here?
thanks,
greg k-h
prev parent reply other threads:[~2021-06-10 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 6:10 [PATCH] usb: gadget: eem: fix command packet transfer issue linyyuan
2021-06-10 6:49 ` 'Greg Kroah-Hartman'
2021-06-10 6:50 ` 'Greg Kroah-Hartman' [this message]
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=YMG2UWeqodfTRRnQ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linyyuan@codeaurora.org \
--cc=stable@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