public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: grygorii.strashko@ti.com (Grygorii Strashko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: keystone: specify usb mode explicitly
Date: Thu, 25 Aug 2016 17:11:31 +0300	[thread overview]
Message-ID: <62e7960a-7f47-8125-c369-2407ffc5a2dd@ti.com> (raw)
In-Reply-To: <09af5947-1a0e-9f44-e046-67276062530d@oracle.com>

Hi Santosh,

On 07/18/2016 08:49 PM, Santosh Shilimkar wrote:
> On 7/18/2016 10:45 AM, Grygorii Strashko wrote:
>> Hi Santosh,
>> On 06/28/2016 12:42 PM, Grygorii Strashko wrote:
>>> The USB OTG mode is not supported by Kestone 2 devices, as result, the
>>> USB devices enumeration and detection will not work properly when
>>> kernel is built with CONFIG_USB_DWC3_DUAL_ROLE=y (default for multi
>>> platform build):
>>>   - it's required to load gadget drivers manually to make host mode
>>> work and this confuses current Keystone 2 users
>>>   - device mode is not working, because port can't detect and switch to
>>> peripheral/host mode dynamically.
>>>
>>> Hence, specify usb mode explicitly in DT: usb0 = "host" for all KS2
>>> devices and usb1 = "peripheral" for K2E.
>>>
>>> Cc: Sekhar Nori <nsekhar@ti.com>
>>> Cc: Roger Quadros <rogerq@ti.com>
>>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>>
>> Do you expect any additional actions from my side relate to this patch?
>>
> Nope. I will pick this up though it has to wait for next merge window
> now.

I'd like to remind you about this patch. 
Would you like me to resend it ?
(I've checked - it can be applied as is on top master and next/master without issues)

-- 
regards,
-grygorii

  reply	other threads:[~2016-08-25 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  9:42 [PATCH] ARM: dts: keystone: specify usb mode explicitly Grygorii Strashko
2016-07-18 17:45 ` Grygorii Strashko
2016-07-18 17:49   ` Santosh Shilimkar
2016-08-25 14:11     ` Grygorii Strashko [this message]
2016-08-25 16:31       ` Santosh Shilimkar

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=62e7960a-7f47-8125-c369-2407ffc5a2dd@ti.com \
    --to=grygorii.strashko@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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