All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
To: Marek Vasut <marex@denx.de>,
	Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: Amelie Delaunay <amelie.delaunay@st.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: [PATCH] [RFC] usb: dwc2: Run the core connect in dwc2_hcd_init()
Date: Thu, 16 Apr 2020 13:37:17 +0000	[thread overview]
Message-ID: <8fb53f3a-a02b-3c53-0d9d-22b707bda786@synopsys.com> (raw)
In-Reply-To: <6ea2270d-19a4-7e8b-42fb-37a4a9d81e1f@denx.de>

Hi,

On 4/16/2020 1:46 PM, Marek Vasut wrote:
> On 4/15/20 5:10 PM, Minas Harutyunyan wrote:
>> Hi,
> 
> Hi,
> 
>> On 4/15/2020 6:55 PM, Marek Vasut wrote:
>>> On 4/15/20 10:37 AM, Minas Harutyunyan wrote:
>>>> Hi,
>>>>
>>>> On 4/14/2020 4:18 PM, Marek Vasut wrote:
>>>>> On 4/14/20 9:14 AM, Minas Harutyunyan wrote:
>>>>
>>>>>
>>>>>> 2. debug log
>>>>>
>>>>> What kind of debug log ?
>>>>>
>>>> Drivers debug log starting from dwc2 loading and connector connecting to
>>>> device, where issue seen.
>>>
>>> How do I enable the one you need ?
>>>
>> To enable debug prints from dwc2 use 'make menuconfig':
>>
>>    Symbol: USB_DWC2_DEBUG [=y]
> 
> Oh, this one, OK. There you go.
> 
> Note that there is no further output when I plug in the USB microB cable
> from a PC.
> 
1. Are you sure that you provided full debug log for dwc2? Actually 
first debug prints of dwc2 should be:

[72891.088917] dwc2 dwc2.1.auto: mapped PA ef100000 to VA 00000000ca45f000
[72891.088924] dwc2 dwc2.1.auto: registering common handler for irq16
[72891.088963] dwc2 dwc2.1.auto: Core Release: 4.00a (snpsid=4f54400a)
[72891.088974] dwc2 dwc2.1.auto: Forcing mode to host
[72891.100285] dwc2 dwc2.1.auto: Forcing mode to device
[72891.112307] dwc2 dwc2.1.auto: Clearing force mode bits
[72891.215275] dwc2 dwc2.1.auto: NonPeriodic TXFIFO size: 1024
[72891.215278] dwc2 dwc2.1.auto: RXFIFO size: 2048
...

2. Does your driver built for 'dual role device' or 'device only'?

3. First observation from register dumps: core in SOFT disconnect state, 
which can be reason of observed issue. Could you please update your 
patch and add only core_connect function call:

+	dwc2_hsotg_core_connect(hsotg);
+
  	return 0;

  error4:

Or instead of patch, if you have any utility in system which will allow 
from command line clear soft disconnect bit from DCTL register? Offset 
of DCTL register is 0x804. SoftDiscon bit number is 1. Clear this bit 
and then plug cable.

Unfortunately, currently I'm working from home and can't remotely 
connect/disconnect cable in lab to try to reproduce observed by you issue.

Thanks,
Minas




  reply	other threads:[~2020-04-16 15:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 14:31 [PATCH] [RFC] usb: dwc2: Run the core connect in dwc2_hcd_init() Marek Vasut
2020-04-13 14:45 ` Minas Harutyunyan
2020-04-13 14:54   ` Marek Vasut
2020-04-13 15:27     ` Minas Harutyunyan
2020-04-13 17:00       ` Marek Vasut
2020-04-14  7:14         ` Minas Harutyunyan
2020-04-14 12:18           ` Marek Vasut
2020-04-15  8:37             ` Minas Harutyunyan
2020-04-15 14:55               ` Marek Vasut
2020-04-15 15:10                 ` Minas Harutyunyan
2020-04-16  9:46                   ` Marek Vasut
2020-04-16 13:37                     ` Minas Harutyunyan [this message]
2020-04-16 14:31                       ` Marek Vasut
2020-04-17  9:00                         ` Minas Harutyunyan
2020-04-20 12:09                           ` Marek Vasut
2020-04-22 13:45                             ` Minas Harutyunyan
2020-04-22 14:21                               ` Marek Vasut
2020-05-14  0:10                                 ` Marek Vasut
2020-05-15  7:41                                   ` Minas Harutyunyan
2020-05-27  6:17                                     ` Minas Harutyunyan
2020-05-28 22:35                                       ` Marek Vasut

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=8fb53f3a-a02b-3c53-0d9d-22b707bda786@synopsys.com \
    --to=minas.harutyunyan@synopsys.com \
    --cc=amelie.delaunay@st.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=marex@denx.de \
    /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.