Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"jun.li@nxp.com" <jun.li@nxp.com>
Subject: Re: [PATCH v2 3/3] usb: dwc3: imx8mp: disable auto suspend for host role
Date: Fri, 9 Jan 2026 00:45:29 +0000	[thread overview]
Message-ID: <20260109004520.5l7tkyhgi6cooeda@synopsys.com> (raw)
In-Reply-To: <ft43w567youffka6qwrpbzkwctk3dttwsnaqgx45atwjhoenc7@rbpluqz7xpm4>

On Thu, Jan 08, 2026, Xu Yang wrote:
> On Tue, Dec 16, 2025 at 11:26:40PM +0000, Thinh Nguyen wrote:
> > On Fri, Dec 05, 2025, Xu Yang wrote:
> > > Do dwc3 core auto suspend enable for device and disable for host
> > > , this can make sure dwc3 core device auto suspend setting is
> > > correct all the time, the background of disable dwc3 core device
> > > auto suspend is to make its parent device suspend immediately
> > > (so wakeup enable can be enabled) after xhci-plat device suspended,
> > > for device mode, we keep the dwc3 core device auto suspend is to
> > > give some wait for gadget to be enumerated.
> > > 
> > > Note: It's a temporary solution until we switch to using the new
> > >       flatten model.
> > > 
> > > Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
> > > 
> > > ---
> > > Changes in v2:
> > >  - add a note suggested by Thinh
> > > ---
> > >  drivers/usb/dwc3/dwc3-imx8mp.c | 31 +++++++++++++++++++++++++++++++
> > >  1 file changed, 31 insertions(+)
> > > 
> > > diff --git a/drivers/usb/dwc3/dwc3-imx8mp.c b/drivers/usb/dwc3/dwc3-imx8mp.c
> > > index 8bece4baecbf..2e13ca588f42 100644
> > > --- a/drivers/usb/dwc3/dwc3-imx8mp.c
> > > +++ b/drivers/usb/dwc3/dwc3-imx8mp.c
> > > @@ -158,11 +158,31 @@ static irqreturn_t dwc3_imx8mp_interrupt(int irq, void *_dwc3_imx)
> > >  	return IRQ_HANDLED;
> > >  }
> > >  
> > > +static void dwc3_imx_pre_set_role(struct dwc3 *dwc, enum usb_role role)
> > > +{
> > > +	if (role == USB_ROLE_HOST)
> > > +		/*
> > > +		 * For xhci host, we need disable dwc core auto
> > > +		 * suspend, because during this auto suspend delay(5s),
> > > +		 * xhci host RUN_STOP is cleared and wakeup is not
> > > +		 * enabled, if device is inserted, xhci host can't
> > > +		 * response the connection.
> > > +		 */
> > > +		pm_runtime_dont_use_autosuspend(dwc->dev);
> > 
> > As noted previously, don't we need to unwind this in dwc3_imx8mp_remove
> > if the current mode device?
> 
> Thanks for the reminder. I check it, dwc3_core_remove() will call
> pm_runtime_dont_use_autosuspend(). So it seems unnecessary to unwind it
> again in dwc3_imx8mp_remove().
> 

Thanks for checking.

BR,
Thinh

  reply	other threads:[~2026-01-09  0:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05  3:29 [PATCH v2 1/3] usb: dwc3: drd: extend dwc3_pre_set_role() to extcon and otg usecase Xu Yang
2025-12-05  3:29 ` [PATCH v2 2/3] usb: dwc3: imx8mp: rename dwc3 to dwc3_pdev in struct dwc3_imx8mp Xu Yang
2025-12-05 15:12   ` Frank Li
2025-12-16 23:19   ` Thinh Nguyen
2025-12-05  3:29 ` [PATCH v2 3/3] usb: dwc3: imx8mp: disable auto suspend for host role Xu Yang
2025-12-16 23:26   ` Thinh Nguyen
2026-01-08  8:00     ` Xu Yang
2026-01-09  0:45       ` Thinh Nguyen [this message]
2025-12-16 23:18 ` [PATCH v2 1/3] usb: dwc3: drd: extend dwc3_pre_set_role() to extcon and otg usecase Thinh Nguyen

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=20260109004520.5l7tkyhgi6cooeda@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=imx@lists.linux.dev \
    --cc=jun.li@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=xu.yang_2@nxp.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