From: Felipe Balbi <balbi@kernel.org>
To: John Keeping <john@metanate.com>
Cc: Minas Harutyunyan <hminas@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: dwc2: Implement set_selfpowered()
Date: Thu, 06 Feb 2020 20:34:23 +0200 [thread overview]
Message-ID: <877e0z5zv4.fsf@kernel.org> (raw)
In-Reply-To: <20200205164448.0c7532c1.john@metanate.com>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
John Keeping <john@metanate.com> writes:
> On Wed, 05 Feb 2020 18:36:21 +0200
> Felipe Balbi <balbi@kernel.org> wrote:
>
>> John Keeping <john@metanate.com> writes:
>>
>> > dwc2 always reports as self-powered in response to a device status
>> > request. Implement the set_selfpowered() operations so that the gadget
>> > can report as bus-powered when appropriate.
>> >
>> > This is modelled on the dwc3 implementation.
>> >
>> > Signed-off-by: John Keeping <john@metanate.com>
>> > ---
>>
>> what's the dependency here?
>
> It depends on 6de1e301b9cf ("usb: dwc2: Fix SET/CLEAR_FEATURE and
> GET_STATUS flows") in your testing/fixes tree.
>
> Sorry, I should have mentioned that in the original message.
No worries, I'll wait until those reach mainline before merging
$subject, then.
cheers
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2020-02-06 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:29 [PATCH] usb: dwc2: Implement set_selfpowered() John Keeping
2020-02-05 7:59 ` Minas Harutyunyan
2020-02-05 11:56 ` John Keeping
2020-02-05 12:05 ` Minas Harutyunyan
2020-02-05 16:36 ` Felipe Balbi
2020-02-05 16:44 ` John Keeping
2020-02-06 18:34 ` Felipe Balbi [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=877e0z5zv4.fsf@kernel.org \
--to=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hminas@synopsys.com \
--cc=john@metanate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).