From: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com> To: John Stultz <john.stultz@linaro.org>, Minas Harutyunyan <Minas.Harutyunyan@synopsys.com> Cc: lkml <linux-kernel@vger.kernel.org>, John Youn <John.Youn@synopsys.com>, Vardan Mikayelyan <mvardan@synopsys.com>, Artur Petrosyan <Arthur.Petrosyan@synopsys.com>, Grigor Tovmasyan <Grigor.Tovmasyan@synopsys.com>, Felipe Balbi <felipe.balbi@linux.intel.com>, "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org> Subject: Re: [PATCH] usb: dwc2: Fix HiKey regression caused by power_down feature Date: Tue, 22 May 2018 14:24:47 +0000 [thread overview] Message-ID: <410670D7E743164D87FA6160E7907A560131356C4E@am04wembxa.internal.synopsys.com> (raw) In-Reply-To: CALAqxLVZXs97sryfPaGY5Gq50-FZROgaBADNXXadcyiNhP3EPQ@mail.gmail.com Hi John, Please provide log with debug enabled configuration. On 5/21/2018 11:41 PM, John Stultz wrote: > On Mon, May 21, 2018 at 1:45 AM, Minas Harutyunyan > <Minas.Harutyunyan@synopsys.com> wrote: >> Hi John, >> >> On 5/19/2018 4:49 AM, John Stultz wrote: >>> In 4.17-rc, commit 03ea6d6e9e1f ("usb: dwc2: Enable power down") >>> caused the HiKey board to not correctly handle switching between >>> usb-gadget and usb-host mode. >>> >>> Unplugging the OTG port would result in: OTG port you mean MicroAB, Correct? dwc2 driver loaded when some device connected to OTG port? And below message printed after disconnect the device from OTG port? >>> [ 42.240973] dwc2 f72c0000.usb: dwc2_restore_host_registers: no host registers to restore >>> [ 42.249066] dwc2 f72c0000.usb: dwc2_host_exit_hibernation: failed to restore host registers >>> >>> And the USB-host ports would not function. USB-host ports - you mean 2 USB A-ports, connected to TS3USB221 HUB? Switching ports between OTG and Host ports via TS3USB221 Switch performing automatically or by some SW tool? >>> >>> And plugging in the OTG port, we would see: >>> [ 46.046557] WARNING: CPU: 3 PID: 6 at drivers/usb/dwc2/gadget.c:260 dwc2_hsotg_init_fifo+0x194/0x1a0 >>> [ 46.055761] CPU: 3 PID: 6 Comm: kworker/u16:0 Not tainted 4.17.0-rc5-00030-ge67da8c #231 >>> [ 46.055767] Hardware name: HiKey Development Board (DT) >>> [ 46.055784] Workqueue: dwc2 dwc2_conn_id_status_change >>> ... >>> >> Could you please send full log to debug. > > Full dmesg log attached. > > I unplugged the usb-otg port at 136 > and replugged it back in at 141 > > >>> p->uframe_sched = false; >>> p->change_speed_quirk = true; >>> + p->power_down = false; >> >> power_down declared as int, suggested to update as follow: >> p->power_down = DWC2_POWER_DOWN_PARAM_NONE; >> >> This can be accepted as temporary solution until we will fully debug >> hibernation feature for HiKey platform. > > Ok, will re-send with the suggested change above. > > thanks > -john >
WARNING: multiple messages have this Message-ID (diff)
From: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com> To: John Stultz <john.stultz@linaro.org>, Minas Harutyunyan <Minas.Harutyunyan@synopsys.com> Cc: lkml <linux-kernel@vger.kernel.org>, John Youn <John.Youn@synopsys.com>, Vardan Mikayelyan <mvardan@synopsys.com>, Artur Petrosyan <Arthur.Petrosyan@synopsys.com>, Grigor Tovmasyan <Grigor.Tovmasyan@synopsys.com>, Felipe Balbi <felipe.balbi@linux.intel.com>, "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org> Subject: usb: dwc2: Fix HiKey regression caused by power_down feature Date: Tue, 22 May 2018 14:24:47 +0000 [thread overview] Message-ID: <410670D7E743164D87FA6160E7907A560131356C4E@am04wembxa.internal.synopsys.com> (raw) Hi John, Please provide log with debug enabled configuration. On 5/21/2018 11:41 PM, John Stultz wrote: > On Mon, May 21, 2018 at 1:45 AM, Minas Harutyunyan > <Minas.Harutyunyan@synopsys.com> wrote: >> Hi John, >> >> On 5/19/2018 4:49 AM, John Stultz wrote: >>> In 4.17-rc, commit 03ea6d6e9e1f ("usb: dwc2: Enable power down") >>> caused the HiKey board to not correctly handle switching between >>> usb-gadget and usb-host mode. >>> >>> Unplugging the OTG port would result in: OTG port you mean MicroAB, Correct? dwc2 driver loaded when some device connected to OTG port? And below message printed after disconnect the device from OTG port? >>> [ 42.240973] dwc2 f72c0000.usb: dwc2_restore_host_registers: no host registers to restore >>> [ 42.249066] dwc2 f72c0000.usb: dwc2_host_exit_hibernation: failed to restore host registers >>> >>> And the USB-host ports would not function. USB-host ports - you mean 2 USB A-ports, connected to TS3USB221 HUB? Switching ports between OTG and Host ports via TS3USB221 Switch performing automatically or by some SW tool? >>> >>> And plugging in the OTG port, we would see: >>> [ 46.046557] WARNING: CPU: 3 PID: 6 at drivers/usb/dwc2/gadget.c:260 dwc2_hsotg_init_fifo+0x194/0x1a0 >>> [ 46.055761] CPU: 3 PID: 6 Comm: kworker/u16:0 Not tainted 4.17.0-rc5-00030-ge67da8c #231 >>> [ 46.055767] Hardware name: HiKey Development Board (DT) >>> [ 46.055784] Workqueue: dwc2 dwc2_conn_id_status_change >>> ... >>> >> Could you please send full log to debug. > > Full dmesg log attached. > > I unplugged the usb-otg port at 136 > and replugged it back in at 141 > > >>> p->uframe_sched = false; >>> p->change_speed_quirk = true; >>> + p->power_down = false; >> >> power_down declared as int, suggested to update as follow: >> p->power_down = DWC2_POWER_DOWN_PARAM_NONE; >> >> This can be accepted as temporary solution until we will fully debug >> hibernation feature for HiKey platform. > > Ok, will re-send with the suggested change above. > > thanks > -john > --- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-05-22 14:24 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-19 0:49 [PATCH] usb: dwc2: Fix HiKey regression caused by power_down feature John Stultz 2018-05-19 0:49 ` John Stultz 2018-05-21 8:45 ` [PATCH] " Minas Harutyunyan 2018-05-21 8:45 ` Minas Harutyunyan 2018-05-21 19:40 ` [PATCH] " John Stultz 2018-05-21 19:40 ` John Stultz 2018-05-22 14:24 ` Minas Harutyunyan [this message] 2018-05-22 14:24 ` Minas Harutyunyan 2018-05-22 21:57 ` [PATCH] " John Stultz 2018-05-22 21:57 ` John Stultz 2018-09-20 14:17 ` [PATCH] " Artur Petrosyan 2018-09-20 14:17 ` Artur Petrosyan 2018-09-21 1:05 ` [PATCH] " John Stultz 2018-09-21 1:05 ` John Stultz 2018-09-24 5:57 ` [PATCH] " Artur Petrosyan 2018-09-24 5:57 ` Artur Petrosyan 2018-09-24 18:51 ` [PATCH] " John Stultz 2018-09-24 18:51 ` John Stultz 2018-09-25 10:04 ` [PATCH] " Artur Petrosyan 2018-09-25 10:04 ` Artur Petrosyan 2018-09-25 17:59 ` [PATCH] " John Stultz 2018-09-25 17:59 ` John Stultz 2018-09-26 6:02 ` [PATCH] " Artur Petrosyan 2018-09-26 6:02 ` Artur Petrosyan [not found] ` <CALAqxLWOBFO_CjfBFNwbC+qNjtK=TgYrPusb4r5-dThBD5bVnw@mail.gmail.com> 2018-10-01 6:56 ` [PATCH] " Artur Petrosyan 2018-10-01 6:56 ` Artur Petrosyan 2018-09-27 12:33 ` [PATCH] " Artur Petrosyan 2018-09-27 12:33 ` Artur Petrosyan 2018-09-28 18:32 ` [PATCH] " John Stultz 2018-09-28 18:32 ` John Stultz 2018-10-01 7:06 ` [PATCH] " Artur Petrosyan 2018-10-01 7:06 ` Artur Petrosyan
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=410670D7E743164D87FA6160E7907A560131356C4E@am04wembxa.internal.synopsys.com \ --to=minas.harutyunyan@synopsys.com \ --cc=Arthur.Petrosyan@synopsys.com \ --cc=Grigor.Tovmasyan@synopsys.com \ --cc=John.Youn@synopsys.com \ --cc=felipe.balbi@linux.intel.com \ --cc=john.stultz@linaro.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-usb@vger.kernel.org \ --cc=mvardan@synopsys.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: linkBe 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.