From: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
To: Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: John Youn <John.Youn@synopsys.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc2: Fix SET/CLEAR_FEATURE and GET_STATUS flows
Date: Fri, 13 Dec 2019 11:54:11 +0000 [thread overview]
Message-ID: <d89dc76f-ab19-e7e7-1375-534cd2cfaa1c@synopsys.com> (raw)
In-Reply-To: <e314d265-6d87-eb7a-997e-52d77ccdb725@synopsys.com>
Hi Felipe,
On 12/10/2019 6:19 PM, Minas Harutyunyan wrote:
> Hi Felipe,
>
> On 12/10/2019 4:53 PM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Minas Harutyunyan <Minas.Harutyunyan@synopsys.com> writes:
>>
>>> SET/CLEAR_FEATURE for Remote Wakeup allowance not handled correctly.
>>> GET_STATUS handling provided not correct data on DATA Stage.
>>> Issue seen when gadget's dr_mode set to "otg" mode and connected
>>> to MacOS.
>>> Both are fixed and tested using USBCV Ch.9 tests.
>>>
>>> Signed-off-by: Minas Harutyunyan <hminas@synopsys.com>
>>
>> do you want to add a Fixes tag here?
>
> Fixes: fa389a6d7726 ("usb: dwc2: gadget: Add remote_wakeup_allowed flag")
>
Got tested tag by issue reported.
Tested-By: Jack Mitchell <ml@embed.me.uk>
Should I resubmit patch as v2 with added "Fixes" and "Tested-by" tags.
> Thanks,
> Minas
>
>>
next prev parent reply other threads:[~2019-12-13 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 11:21 [PATCH] usb: dwc2: Fix SET/CLEAR_FEATURE and GET_STATUS flows Minas Harutyunyan
2019-12-10 12:53 ` Felipe Balbi
2019-12-10 14:19 ` Minas Harutyunyan
2019-12-13 11:54 ` Minas Harutyunyan [this message]
2020-02-04 11:45 ` John Keeping
2020-02-04 11:50 ` Minas Harutyunyan
2020-02-04 15:04 ` John Keeping
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=d89dc76f-ab19-e7e7-1375-534cd2cfaa1c@synopsys.com \
--to=minas.harutyunyan@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.