linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Artur Petrosyan <Arthur.Petrosyan@synopsys.com>
Cc: Felipe Balbi <balbi@kernel.org>,
	Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>,
	linux-usb@vger.kernel.org,
	Douglas Anderson <dianders@chromium.org>,
	John Youn <John.Youn@synopsys.com>,
	Paul Zimmerman <paulz@synopsys.com>,
	stable@vger.kernel.org, #@synopsys.com, 5.2@synopsys.com,
	Felipe Balbi <balbi@ti.com>,
	Kever Yang <kever.yang@rock-chips.com>
Subject: Re: [PATCH 3/3] usb: dwc2: Prevent core suspend when port connection flag is 0
Date: Fri, 26 Mar 2021 14:33:28 +0100	[thread overview]
Message-ID: <YF3iqIsjHVfit9C3@kroah.com> (raw)
In-Reply-To: <20210326102510.BDEDEA005D@mailhost.synopsys.com>

On Fri, Mar 26, 2021 at 02:25:09PM +0400, Artur Petrosyan wrote:
> In host mode port connection status flag is "0" when loading
> the driver. After loading the driver system asserts suspend
> which is handled by "_dwc2_hcd_suspend()" function. Before
> the system suspend the port connection status is "0". As
> result need to check the "port_connect_status" if it is "0",
> then skipping entering to suspend.
> 
> Cc: <stable@vger.kernel.org> # 5.2
> Fixes: 6f6d70597c15 ("usb: dwc2: bus suspend/resume for hosts with
> DWC2_POWER_DOWN_PARAM_NONE")

In the future, do not line-wrap the fixes line.

thanks,

greg k-h

  reply	other threads:[~2021-03-26 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 10:25 [PATCH 3/3] usb: dwc2: Prevent core suspend when port connection flag is 0 Artur Petrosyan
2021-03-26 13:33 ` Greg Kroah-Hartman [this message]
     [not found] <20210318061333.D6F9CA022F@mailhost.synopsys.com>
2021-03-18  6:23 ` Minas Harutyunyan
2021-03-23 11:25 ` Greg Kroah-Hartman

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=YF3iqIsjHVfit9C3@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=#@synopsys.com \
    --cc=5.2@synopsys.com \
    --cc=Arthur.Petrosyan@synopsys.com \
    --cc=John.Youn@synopsys.com \
    --cc=Minas.Harutyunyan@synopsys.com \
    --cc=balbi@kernel.org \
    --cc=balbi@ti.com \
    --cc=dianders@chromium.org \
    --cc=kever.yang@rock-chips.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=paulz@synopsys.com \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).