public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: "Neronin, Niklas" <niklas.neronin@linux.intel.com>
To: Michal Pecio <michal.pecio@gmail.com>
Cc: mathias.nyman@linux.intel.com, linux-usb@vger.kernel.org,
	raoxu@uniontech.com, Thinh.Nguyen@synopsys.com
Subject: Re: [RFC PATCH 06/12] usb: xhci: move initialization for lifetime objects
Date: Fri, 6 Mar 2026 11:47:18 +0200	[thread overview]
Message-ID: <f64abf52-6b9b-4eb3-b9de-a215cd7e2e82@linux.intel.com> (raw)
In-Reply-To: <20260305231417.4415aa36.michal.pecio@gmail.com>



On 06/03/2026 0.14, Michal Pecio wrote:
> On Thu,  5 Mar 2026 15:48:18 +0100, Niklas Neronin wrote:
>> Initialize objects that exist for the lifetime of the driver only once,
>> rather than repeatedly. These objects do not require re-initialization
>> after events such as S4 (suspend-to-disk).
>>
>> Signed-off-by: Niklas Neronin <niklas.neronin@linux.intel.com>
>> ---
>>  drivers/usb/host/xhci-mem.c |  1 -
>>  drivers/usb/host/xhci.c     | 15 ++++++++-------
>>  2 files changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/usb/host/xhci-mem.c b/drivers/usb/host/xhci-mem.c
>> index 005b7bc1bfda..fae75969e49a 100644
>> --- a/drivers/usb/host/xhci-mem.c
>> +++ b/drivers/usb/host/xhci-mem.c
>> @@ -2001,7 +2001,6 @@ void xhci_mem_cleanup(struct xhci_hcd *xhci)
>>  	xhci->port_caps = NULL;
>>  	xhci->interrupters = NULL;
>>  
>> -	xhci->page_size = 0;
>>  	xhci->usb2_rhub.bus_state.bus_suspended = 0;
>>  	xhci->usb3_rhub.bus_state.bus_suspended = 0;
>>  }
>> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
>> index d9519a9e9e17..338e93f39937 100644
>> --- a/drivers/usb/host/xhci.c
>> +++ b/drivers/usb/host/xhci.c
>> @@ -549,13 +549,6 @@ static int xhci_init(struct usb_hcd *hcd)
>>  	int retval;
>>  
>>  	xhci_dbg_trace(xhci, trace_xhci_dbg_init, "Starting %s", __func__);
>> -	spin_lock_init(&xhci->lock);
>> -
>> -	INIT_LIST_HEAD(&xhci->cmd_list);
> 
> Can we prove that this list is empty?
> 
> If there is any leftover garbage there, INIT_LIST_HEAD simply leaks it.
> Without it, the garbage stays on the list.

I assume you are referring to the resume path.
In this case xhci_cleanup_command_queue() is called before xhci_init().

xhci_resume()
├─xhci_mem_cleanup()
│  └─xhci_cleanup_command_queue()
└─xhci_init()

> 
>> -	INIT_DELAYED_WORK(&xhci->cmd_timer, xhci_handle_command_timeout);
>> -	init_completion(&xhci->cmd_ring_stop_completion);
>> -	xhci_hcd_page_size(xhci);
>> -	memset(xhci->devs, 0, MAX_HC_SLOTS * sizeof(*xhci->devs));
>>  
>>  	retval = xhci_mem_init(xhci, GFP_KERNEL);
>>  	if (retval)
>> @@ -5522,6 +5515,14 @@ int xhci_gen_setup(struct usb_hcd *hcd, xhci_get_quirks_t get_quirks)
>>  		dma_set_coherent_mask(dev, DMA_BIT_MASK(32));
>>  	}
>>  
>> +	spin_lock_init(&xhci->lock);
>> +	INIT_LIST_HEAD(&xhci->cmd_list);
>> +	INIT_DELAYED_WORK(&xhci->cmd_timer, xhci_handle_command_timeout);
>> +	init_completion(&xhci->cmd_ring_stop_completion);
>> +	xhci_hcd_page_size(xhci);
>> +
>> +	memset(xhci->devs, 0, MAX_HC_SLOTS * sizeof(*xhci->devs));
>> +
>>  	xhci_dbg(xhci, "Calling HCD init\n");
>>  	/* Initialize HCD and host controller data structures. */
>>  	retval = xhci_init(hcd);
>> -- 
>> 2.50.1
>>


  reply	other threads:[~2026-03-06  9:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05 14:48 [RFC PATCH 00/12] usb: xhci: groundwork for secondary interrupters Niklas Neronin
2026-03-05 14:48 ` [RFC PATCH 01/12] usb: xhci: simplify CMRT initialization logic Niklas Neronin
2026-03-05 14:48 ` [RFC PATCH 02/12] usb: xhci: relocate Restore/Controller error check Niklas Neronin
2026-03-05 14:48 ` [RFC PATCH 03/12] usb: xhci: simplify USBSTS register reset Niklas Neronin
2026-03-05 19:26   ` Michal Pecio
2026-03-05 14:48 ` [RFC PATCH 04/12] usb: xhci: move reserving command ring trb Niklas Neronin
2026-03-05 14:48 ` [RFC PATCH 05/12] usb: xhci: move ring initialization Niklas Neronin
2026-03-05 14:48 ` [RFC PATCH 06/12] usb: xhci: move initialization for lifetime objects Niklas Neronin
2026-03-05 22:14   ` Michal Pecio
2026-03-06  9:47     ` Neronin, Niklas [this message]
2026-03-05 14:48 ` [RFC PATCH 07/12] usb: xhci: split core allocation and initialization Niklas Neronin
2026-03-05 22:23   ` Michal Pecio
2026-03-05 14:48 ` [RFC PATCH 08/12] usb: xhci: improve debug messages during suspend Niklas Neronin
2026-03-05 14:48 ` [RFC PATCH 09/12] usb: xhci: optimize resuming from S4 (suspend-to-RAM) Niklas Neronin
2026-03-06  6:52   ` raoxu
2026-03-06 10:16     ` Neronin, Niklas
2026-03-06  7:05   ` Michal Pecio
2026-03-05 14:48 ` [RFC PATCH 10/12] usb: xhci: add interrupter type Niklas Neronin
2026-03-05 14:48 ` [RFC PATCH 11/12] usb: xhci: prepare for multiple interrupters Niklas Neronin
2026-03-05 14:48 ` [RFC PATCH 12/12] usb: xhci: prepare IRQ handler " Niklas Neronin
2026-03-06  6:53   ` raoxu

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=f64abf52-6b9b-4eb3-b9de-a215cd7e2e82@linux.intel.com \
    --to=niklas.neronin@linux.intel.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@linux.intel.com \
    --cc=michal.pecio@gmail.com \
    --cc=raoxu@uniontech.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