All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: Martin Kepplinger <martin.kepplinger@puri.sm>,
	Roger Quadros <rogerq@ti.com>
Cc: gregkh@linuxfoundation.org, sergei.shtylyov@cogentembedded.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] usb: dwc3: support continuous runtime PM with dual role
Date: Thu, 14 May 2020 13:40:37 +0300	[thread overview]
Message-ID: <87lflu4x5m.fsf@kernel.org> (raw)
In-Reply-To: <d1c38262-198c-c128-f2b7-3253bde37e5c@puri.sm>

[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

Martin Kepplinger <martin.kepplinger@puri.sm> writes:

> On 24.04.20 09:48, Roger Quadros wrote:
>> 
>> 
>> On 19/03/2020 12:02, Martin Kepplinger wrote:
>>> The DRD module calls dwc3_set_mode() on role switches, i.e. when a
>>> device is
>>> being plugged in. In order to support continuous runtime power
>>> management when
>>> plugging in / unplugging a cable, we need to call
>>> pm_runtime_get_sync() in
>>> this path.
>>>
>>> Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
>> 
>> Reviewed-by: Roger Quadros <rogerq@ti.com>
>> 
>> 
>
> thank you very much Roger. Anything else that is holding this back?

Merge window is holding it back :-) It has been in my tree for weeks:

https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git/commit/?h=testing/next&id=c2cd3452d5f8b66d49a73138fba5baadd5b489bd

Gotta wait for the next merge window for new features to be merged.

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2020-05-14 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 10:02 [PATCH v3] usb: dwc3: support continuous runtime PM with dual role Martin Kepplinger
2020-04-05 11:43 ` Martin Kepplinger
2020-04-24  7:42   ` Martin Kepplinger
2020-04-24  7:48 ` Roger Quadros
2020-05-05  9:44   ` Martin Kepplinger
2020-05-14 10:40     ` 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=87lflu4x5m.fsf@kernel.org \
    --to=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=martin.kepplinger@puri.sm \
    --cc=rogerq@ti.com \
    --cc=sergei.shtylyov@cogentembedded.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 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.