public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: Roger Quadros <rogerq@ti.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] usb: dwc3: add dual role support using OTG block
Date: Thu, 08 Mar 2018 15:12:50 +0200	[thread overview]
Message-ID: <87ina6btil.fsf@linux.intel.com> (raw)
In-Reply-To: <7c9382af-bd99-2599-35b1-863320517a0c@ti.com>

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


Hi,

Roger Quadros <rogerq@ti.com> writes:
> Felipe,
>
> On 08/03/18 12:39, Felipe Balbi wrote:
>> Roger Quadros <rogerq@ti.com> writes:
>> 
>>> This is useful on platforms (e.g. TI AM437x) that don't
>>> have ID available on a GPIO but do have the OTG block.
>>>
>>> We can obtain the ID state via the OTG block and use it
>>> for dual-role switching.
>>>
>>> Signed-off-by: Roger Quadros <rogerq@ti.com>
>> 
>> patch one applied fine to testing/next. But not this one:
>
> That's because you will need this commit from v4.16-rc3
>
> c4a5153e87fd	("usb: dwc3: core: Power-off core/PHYs on system_suspend in host mode")
>
> Could you please apply that and let me know if it works?

indeed, applied fine. thanks

-- 
balbi

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

      reply	other threads:[~2018-03-08 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 11:29 [PATCH v2 0/2] usb: dwc3: Add dual-role support using OTG core Roger Quadros
2018-02-27 11:29 ` [PATCH v2 1/2] usb: dwc3: core.h: add some register definitions Roger Quadros
2018-02-27 11:30 ` [PATCH v2 2/2] usb: dwc3: add dual role support using OTG block Roger Quadros
2018-03-08 10:39   ` Felipe Balbi
2018-03-08 12:31     ` Roger Quadros
2018-03-08 13:12       ` 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=87ina6btil.fsf@linux.intel.com \
    --to=balbi@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rogerq@ti.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