Linux USB
 help / color / mirror / Atom feed
From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>,
	<gregkh@linuxfoundation.org>
Cc: <intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>, <linux-usb@vger.kernel.org>,
	<ravitejax.veesam@intel.com>
Subject: Re: [RFT PATCH] xhci: dbc: support runtime suspend while DbC is in enabled state
Date: Mon, 15 Jun 2026 17:44:52 +0530	[thread overview]
Message-ID: <8ed92dde-c6e2-4dcf-92d0-fb395b2c26fe@intel.com> (raw)
In-Reply-To: <20260615085508.2096592-1-mathias.nyman@linux.intel.com>

Hello Mathias,

On 6/15/2026 2:25 PM, Mathias Nyman wrote:
> Allow xHC to runtime suspend if DbC is in 'enabled' state for over
> 15 seconds without a connect.
> 
> Idea is that every time we go to 'enabled' state we make sure DbC runtime
> pm usage is '1' and save a timestamp. if the event loop still finds DbC in
> enabled state 15 seconds later then it decrease DbC runtime pm usage by
> calling pm_runtime_put().
> Enabled state is reached either when DbC is enabled by userspace or a
> connected/configured DbC is disconnected.
> 
> When a connect is detected we make sure DbC usage count is 1.
> 
> If DbC has been in 'enabled' state for 15 seconds and DbC usage is
> decreased to 0 by pm_runtime_put, then the whole xHC controller may
> runtime suspends to PCI D3 state if no other devices are using it
> 
> DbC sysfs file will show 'suspended' when xHC is suspended and will wake up
> and enable DbC at cable connect, or when user writes 'enable' to the file.
> 

The patch helps. Thank you!
Anytime time line on getting it merged?

==
Chaitanya

> Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com>
> ---
>   .../testing/sysfs-bus-pci-drivers-xhci_hcd    |  2 +-
>   drivers/usb/host/xhci-dbgcap.c                | 60 ++++++++++++++++++-
>   drivers/usb/host/xhci-dbgcap.h                |  3 +
>   3 files changed, 62 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/ABI/testing/sysfs-bus-pci-drivers-xhci_hcd b/Documentation/ABI/testing/sysfs-bus-pci-drivers-xhci_hcd
> index 98a8376a83d2..991765d84201 100644
> --- a/Documentation/ABI/testing/sysfs-bus-pci-drivers-xhci_hcd
> +++ b/Documentation/ABI/testing/sysfs-bus-pci-drivers-xhci_hcd
> @@ -22,7 +22,7 @@ Description:
>   
>   		Reading this attribute gives the state of the DbC. It
>   		can be one of the following states: disabled, enabled,
> -		initialized, connected or configured.
> +		initialized, connected, configured or suspended.
>   
>   What:		/sys/bus/pci/drivers/xhci_hcd/.../dbc_idVendor
>   Date:		March 2023
> diff --git a/drivers/usb/host/xhci-dbgcap.c b/drivers/usb/host/xhci-dbgcap.c
> index 8ff8ac300927..f228c46293ca 100644
> --- a/drivers/usb/host/xhci-dbgcap.c
> +++ b/drivers/usb/host/xhci-dbgcap.c
> @@ -647,6 +647,31 @@ static int xhci_dbc_enable_dce(struct xhci_dbc *dbc, bool enable)
>   
>   static void xhci_dbc_set_state(struct xhci_dbc *dbc, enum dbc_state new_state)
>   {
> +	if (dbc->state == new_state)
> +		return;
> +
> +	switch (new_state) {
> +	case DS_ENABLED:
> +		/*
> +		 * DbC pm usage is 1 here, both when moved from disconnect or
> +		 * configured states, or when setting initial DbC enable state.
> +		 * Just enable pending put
> +		 */
> +		dev_dbg(dbc->dev, "DbC set pending_rpm_put = 1\n");
> +		dbc->pending_rpm_put = 1;
> +		break;
> +	case DS_CONNECTED:
> +		if (dbc->pending_rpm_put)
> +			/* DbC pm usage still 1, just remove pending put */
> +			dbc->pending_rpm_put = 0;
> +		else
> +			/* DbC pm usage was put to 0, call get */
> +			pm_runtime_get(dbc->dev);
> +		break;
> +	default:
> +		break;
> +	}
> +
>   	dbc->state_timestamp = jiffies;
>   	dbc->state = new_state;
>   }
> @@ -682,7 +707,7 @@ static int xhci_dbc_start(struct xhci_dbc *dbc)
>   
>   	WARN_ON(!dbc);
>   
> -	pm_runtime_get_sync(dbc->dev); /* note this was self.controller */
> +	pm_runtime_get(dbc->dev);
>   
>   	spin_lock_irqsave(&dbc->lock, flags);
>   	ret = xhci_do_dbc_start(dbc);
> @@ -707,6 +732,7 @@ static int xhci_dbc_start(struct xhci_dbc *dbc)
>   static void xhci_dbc_stop(struct xhci_dbc *dbc)
>   {
>   	unsigned long		flags;
> +	bool			need_rpm_put = false;
>   
>   	WARN_ON(!dbc);
>   
> @@ -732,12 +758,20 @@ static void xhci_dbc_stop(struct xhci_dbc *dbc)
>   
>   	spin_lock_irqsave(&dbc->lock, flags);
>   	writel(0, &dbc->regs->control);
> +
> +	if (dbc->state == DS_CONNECTED || dbc->state == DS_CONFIGURED ||
> +	    dbc->pending_rpm_put)
> +		need_rpm_put = true;
> +
> +	dbc->pending_rpm_put = 0;
> +
>   	xhci_dbc_set_state(dbc, DS_DISABLED);
>   	spin_unlock_irqrestore(&dbc->lock, flags);
>   
>   	xhci_dbc_mem_cleanup(dbc);
>   
> -	pm_runtime_put(dbc->dev); /* note, was self.controller */
> +	if (need_rpm_put)
> +		pm_runtime_put(dbc->dev);
>   }
>   
>   static void
> @@ -911,6 +945,12 @@ static enum evtreturn xhci_dbc_do_handle_events(struct xhci_dbc *dbc)
>   			dev_info(dbc->dev, "DbC connected\n");
>   		} else if (!(ctrl & DBC_CTRL_DBC_ENABLE)) {
>   			dev_err(dbc->dev, "unexpected DbC disable, xHC reset?\n");
> +		} else if (dbc->pending_rpm_put &&
> +			   time_is_before_jiffies(dbc->state_timestamp +
> +				msecs_to_jiffies(DBC_AUTOSUSPEND_DELAY))) {
> +			dbc->pending_rpm_put = 0;
> +			dev_dbg(dbc->dev, "DbC Enabled state for 15 seconds, allow rpm suspend\n");
> +			pm_runtime_put(dbc->dev);
>   		}
>   
>   		return EVT_DONE;
> @@ -1099,6 +1139,9 @@ static ssize_t dbc_show(struct device *dev,
>   	if (dbc->state >= ARRAY_SIZE(dbc_state_strings))
>   		return sysfs_emit(buf, "unknown\n");
>   
> +	if (dbc->resume_required)
> +		return sysfs_emit(buf, "suspended\n");
> +
>   	return sysfs_emit(buf, "%s\n", dbc_state_strings[dbc->state]);
>   }
>   
> @@ -1113,12 +1156,25 @@ static ssize_t dbc_store(struct device *dev,
>   	dbc = xhci->dbc;
>   
>   	if (sysfs_streq(buf, "enable")) {
> +		pm_runtime_get_sync(dbc->dev);
> +
>   		mutex_lock(&dbc->enable_mutex);
> +		/*
> +		 * DbC may already be enabled here if xhci was suspended with
> +		 * dbc->resume_required set, and resumed by pm_runtime_get_sync()
> +		 * above. In this case we end up calling xhci_dbc_start() twice,
> +		 * second time returns an error but is harmless
> +		 */
>   		xhci_dbc_start(dbc);
> +
>   		mutex_unlock(&dbc->enable_mutex);
> +		pm_runtime_put(dbc->dev);
>   	} else if (sysfs_streq(buf, "disable")) {
>   		mutex_lock(&dbc->enable_mutex);
> +
> +		dbc->resume_required = 0;
>   		xhci_dbc_stop(dbc);
> +
>   		mutex_unlock(&dbc->enable_mutex);
>   	} else {
>   		return -EINVAL;
> diff --git a/drivers/usb/host/xhci-dbgcap.h b/drivers/usb/host/xhci-dbgcap.h
> index df7aca8bfe99..5b18efb2c1ea 100644
> --- a/drivers/usb/host/xhci-dbgcap.h
> +++ b/drivers/usb/host/xhci-dbgcap.h
> @@ -114,6 +114,8 @@ struct dbc_ep {
>   #define DBC_POLL_INTERVAL_MAX		5000	/* milliseconds */
>   #define DBC_XFER_INACTIVITY_TIMEOUT	10	/* milliseconds */
>   #define DBC_ENUMERATION_TIMEOUT		2000	/* milliseconds */
> +#define DBC_AUTOSUSPEND_DELAY		15000	/* milliseconds */
> +
>   /*
>    * Private structure for DbC hardware state:
>    */
> @@ -166,6 +168,7 @@ struct xhci_dbc {
>   	unsigned long			xfer_timestamp;
>   	unsigned long			state_timestamp;
>   	unsigned			resume_required:1;
> +	unsigned			pending_rpm_put:1;
>   	struct dbc_ep			eps[2];
>   
>   	const struct dbc_driver		*driver;


  reply	other threads:[~2026-06-15 12:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03  9:11 [PATCH 00/15] xhci features for usb-next Mathias Nyman
2026-06-03  9:11 ` [PATCH 01/15] usb: xhci: fix typo in xhci_set_port_power() comment Mathias Nyman
2026-06-03  9:11 ` [PATCH 02/15] usb: xhci: remove legacy 'num_trbs_free' tracking Mathias Nyman
2026-06-03  9:11 ` [PATCH 03/15] usb: xhci: Simplify xhci_quiesce() Mathias Nyman
2026-06-03  9:11 ` [PATCH 04/15] usb: xhci: Remove skip_isoc_td() Mathias Nyman
2026-06-03  9:11 ` [PATCH 05/15] usb: xhci: Remove isochronous URB_SHORT_NOT_OK handling Mathias Nyman
2026-06-03  9:11 ` [PATCH 06/15] usb: xhci: Improve Soft Retries after short transfers Mathias Nyman
2026-06-03  9:11 ` [PATCH 07/15] xhci: dbc: Fix sysfs ABI Documentation for xhci dbc states Mathias Nyman
2026-06-03  9:11 ` [PATCH 08/15] xhci: dbc: serialize enabling and disabling dbc Mathias Nyman
2026-06-15  6:11   ` Borah, Chaitanya Kumar
2026-06-15  8:47     ` Mathias Nyman
2026-06-15  8:55       ` [RFT PATCH] xhci: dbc: support runtime suspend while DbC is in enabled state Mathias Nyman
2026-06-15 12:14         ` Borah, Chaitanya Kumar [this message]
2026-06-03  9:11 ` [PATCH 09/15] xhci: dbc: add helper to set and clear DbC DCE enable bit Mathias Nyman
2026-06-03  9:11 ` [PATCH 10/15] xhci: dbc: add timestamps to DbC state changes in a new helper Mathias Nyman
2026-06-03  9:11 ` [PATCH 11/15] xhci: dbc: detect and recover hung DbC during enumeraton Mathias Nyman
2026-06-03  9:11 ` [PATCH 12/15] xhci: Prevent queuing new commands if xhci is inaccessible Mathias Nyman
2026-06-03  9:11 ` [PATCH 13/15] usb: xhci: refactor DCBAA struct Mathias Nyman
2026-06-03  9:11 ` [PATCH 14/15] usb: xhci: allocate DCBAA based on host controller max slots Mathias Nyman
2026-06-03  9:11 ` [PATCH 15/15] usb: xhci: allocate internal DCBAA mirror dynamically Mathias Nyman

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=8ed92dde-c6e2-4dcf-92d0-fb395b2c26fe@intel.com \
    --to=chaitanya.kumar.borah@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=ravitejax.veesam@intel.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