From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 95145220F29; Thu, 18 Sep 2025 16:21:02 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.13 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758212465; cv=none; b=g18H/zuFJ/ZHQstpykVg1KFLq2elYipLMIjbkHQWuzJOSKapAMbzruw/said+rUnBtFBEic8fNM2EX/FIPGOhiN9iZVcmVdC1K1mtbO3owFRescvzRT6OTn/UD3N2Lu7mWgmO/x8JH6hDM37u4AtN6Hr7Mo0ZO4UToBU58KX67w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758212465; c=relaxed/simple; bh=S+EWJM8EzP/r6P87HOeFwbiFLDxiM6Sd7XrZsIPPRmY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Q7nKq8blUUD+YMiMHYhYZUmQGZT8pAoVX5IKsBDsgbJfHmss+X/8hSQAF7xIj9tO/A+0rAEMN4n+kIKnv3ZisiMJFk6VYY6VMbLkFursa+qKUTGYxtRw2pzLWETr/NAp+ZDo8hz+ggkvGt4TkKt1bfYJT4SsZi/buvQBNLtOfQI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=none smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=aiugJSaI; arc=none smtp.client-ip=198.175.65.13 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="aiugJSaI" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1758212463; x=1789748463; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=S+EWJM8EzP/r6P87HOeFwbiFLDxiM6Sd7XrZsIPPRmY=; b=aiugJSaI+p5blVUQCk6iBRB2pt6CQVXDGH8pSCU/cz+pgNRFhRyaj+Nb XP28wuTd7qrbn/Kh6xmv1LeH+G14v45uKNxBPp5is2Lfwk/3+w3DlZABf TNQlbFAKbkcAvVsXFXRloCwas20Zjp2gN/zTcurqXcDTwpnkYkObhTmO2 IHLzJxhfUEM8Zg03tWsKzP1k26CW7DO0JUxDk+78XMIrmyNgsb5g0BiAA O56NGFuHtnq/QEr9Yu47ucd8ypVwYKgZUmVGy5Kjw0fmxW9rNYX9GJOI+ 2htPK4zpsGoilFiSFaOQwZ4VgjNX5JTockBw81kNnQMtcS1cgmdDGYkdi Q==; X-CSE-ConnectionGUID: WpUMEkpySF6JXNJQUZfPNA== X-CSE-MsgGUID: hjwTmDGsStOJfTP3WZuBRw== X-IronPort-AV: E=McAfee;i="6800,10657,11557"; a="71661065" X-IronPort-AV: E=Sophos;i="6.18,275,1751266800"; d="scan'208";a="71661065" Received: from fmviesa005.fm.intel.com ([10.60.135.145]) by orvoesa105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Sep 2025 09:21:02 -0700 X-CSE-ConnectionGUID: 5B5qUr3KTEGEazcHVxeKaA== X-CSE-MsgGUID: TeQeYWMKSP6wQNr/suHJXA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.18,275,1751266800"; d="scan'208";a="180006111" Received: from black.igk.intel.com ([10.91.253.5]) by fmviesa005.fm.intel.com with ESMTP; 18 Sep 2025 09:21:00 -0700 Received: by black.igk.intel.com (Postfix, from userid 1001) id 3418D97; Thu, 18 Sep 2025 18:20:59 +0200 (CEST) Date: Thu, 18 Sep 2025 18:20:59 +0200 From: Mika Westerberg To: =?utf-8?B?5p2O5L2z5oCh?= Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, jiayi_dec@163.com Subject: Re: [PATCH RFC] thunderbolt: Re-add DP resources on resume Message-ID: <20250918162059.GL2912318@black.igk.intel.com> References: <20250917082456.1790252-1-lijiayi@kylinos.cn> <0540df54-efd6-4b79-90f9-ec305e1f5f7e@kylinos.cn> <20250917125017.GI2912318@black.igk.intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Hi, On Thu, Sep 18, 2025 at 04:34:31PM +0800, 李佳怡 wrote: > > > 在 2025/9/17 20:50, Mika Westerberg 写道: > > On Wed, Sep 17, 2025 at 06:12:31PM +0800, 李佳怡 wrote: > > > > > > As requested, I've attached the complete dmesg output (from boot to after > > > resume) reproducing the issue. > > > > > > Testing Methodology: > > > 1. Start with the Targus Thunderbolt dock already connected to the system > > > 2. Enter S3 suspend (sleep) with no DP monitor connected to the dock > > > 3. Resume from S3 > > > 4. After the system has fully resumed, connect the DP monitor to the dock > > > > Thanks! It is badly line wrapped. I wonder if you can just attach it? > > Anyways I found some unexpected things there: > > > > > [ 8.647850] With USB4 patch v1.0.0 > > > > What is this? ;-) > > Thanks for your help! > > This is a self-compiled kernel based on version 5.4 with backported > Thunderbolt drivers. I will also attach the kernel log from a build using > the linux-6.6.y branch of the community linux-stable repository. Okay but I really suggest using more recent kernel. 6.16 is current stable so that would be good. > > > [ 8.647860] ACPI: bus type thunderbolt registered > > > [ 8.664660] [7] nhi_probe:1326: thunderbolt 0000:2c:00.0: total paths: 21 > > > [ 8.665209] [7] tb_ring_alloc:586: thunderbolt 0000:2c:00.0: allocating > > > TX ring 0 of size 10 > > > [ 8.665243] [7] tb_ring_alloc:586: thunderbolt 0000:2c:00.0: allocating > > > RX ring 0 of size 10 > > > [ 8.665267] [7] tb_ctl_alloc:665: thunderbolt 0000:2c:00.0: control > > > channel created > > > [ 8.665272] [7] icm_probe:2549: thunderbolt 0000:2c:00.0: ICM not > > > supported on this controller > > > [ 8.665285] [7] tb_ring_free:840: thunderbolt 0000:2c:00.0: freeing RX > > > ring 0 > > > [ 8.665294] [7] tb_ring_free:840: thunderbolt 0000:2c:00.0: freeing TX > > > ring 0 > > > > What is this? > > > > Is this Intel TB/USB4 controller or something else? All USB4 compliant > > controllers should go directly to tb.c as that's the part dealing with > > software connection manager. The above looks like it tries first with the > > firmware connection manager and that should not happen outside of Intel > > Thunderbolt 3 hosts. > > Yes, there is a mistake. I discovered that during the USB4_NATIVE_CONTROL > negotiation in the firmware, an OSC_CAPABILITIES_MASK_ERROR bit was being > set incorrectly, which should not have happened. > > The log I will attach next has been modified to fix this issue. [..] > [ 0.498976] [1] tb_switch_reset:1666: thunderbolt 0000:2c:00.0: 0: resetting > [ 0.533329] [1] tb_add_dp_resources:217: thunderbolt 0000:2c:00.0: 0:10: DP IN resource available > [ 0.533959] [1] tb_add_dp_resources:217: thunderbolt 0000:2c:00.0: 0:11: DP IN resource available The DP IN resources were added here. [..] > [ 19.035726] [171] tb_switch_set_wake:3445: thunderbolt 0000:2c:00.0: 0: enabling wakeup: 0x3f > [ 19.037401] [171] tb_ring_stop:768: thunderbolt 0000:2c:00.0: stopping RX ring 0 > [ 19.037412] [171] ring_interrupt_active:141: thunderbolt 0000:2c:00.0: disabling interrupt at register 0x38200 bit 21 (0x200001 -> 0x1) > [ 19.037439] [171] tb_ring_stop:768: thunderbolt 0000:2c:00.0: stopping TX ring 0 > [ 19.037449] [171] ring_interrupt_active:141: thunderbolt 0000:2c:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) > [ 19.037463] [171] tb_ctl_stop:733: thunderbolt 0000:2c:00.0: control channel stopped Runtime suspend. (and a couple more) > [ 266.399800] [3870] tb_ctl_start:703: thunderbolt 0000:2c:00.0: control channel starting... > [ 266.399808] [3870] tb_ring_start:693: thunderbolt 0000:2c:00.0: starting TX ring 0 > [ 266.399821] [3870] ring_interrupt_active:141: thunderbolt 0000:2c:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) > [ 266.399826] [3870] tb_ring_start:693: thunderbolt 0000:2c:00.0: starting RX ring 0 > [ 266.399837] [3870] ring_interrupt_active:141: thunderbolt 0000:2c:00.0: enabling interrupt at register 0x38200 bit 21 (0x1 -> 0x200001) > [ 266.399848] [3870] tb_switch_resume:3478: thunderbolt 0000:2c:00.0: 0: resuming switch > [ 266.399852] [3870] tb_switch_configure:2590: thunderbolt 0000:2c:00.0: restoring Switch at 0x0 (depth: 0, up port: 5) > [ 266.400032] [3870] tb_switch_set_wake:3447: thunderbolt 0000:2c:00.0: 0: disabling wakeup Around this time you should see the hotplug events coming to the DP IN adapters. But there is none. There is a bit in the DP adapter config space (DHP) that can be used to disable this but the spec says it defaults to 0. Anyways I suggest to check that (and also the Plugged bit). You can dump these using tbtools [1]. Let me know if you want help with that. BTW, what is the device vendor? This is not Intel TB/USB4 controller so I'm curious what is it :) [1] https://github.com/intel/tbtools