From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.12]) (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 2F22923EAA4 for ; Tue, 30 Dec 2025 07:24:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.12 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767079456; cv=none; b=duBjI9JeEXIj1mvgrz7ntlZx/Lzo+urkmUpIxikCe8Yhx/srqE9ywLVJmAFjHu2SF+hyR1u9Q0aiTf4N3YhWp08cp2Ne5boOBELVjHiYBNxFhUv39PZdsI1bQ/EQACzIx7upIaGvmGxBX3mdEqDJLCFxnGACDW4h2mwmRkTuSSA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767079456; c=relaxed/simple; bh=wnpihVohUzCwwn8naLQMKXTDQIeEvoWSciTYk0XlrJA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=sbXcxyo+N77W+/1UXMW2mh/mtT6ItRkESyZgZt+qPwWHhfocMdU3tpywxWswZR8j8TiufKqZRlRtY+gz6nxFmiw6PYppUM6zfPChbCJLdWUPz8h66j3Q9z+0IRPL7lpxrYU/Jd6/5Bh3guaCwVbrYwFHtO+F1MBMIdShQgYWqIg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=NkMKxP0Q; arc=none smtp.client-ip=192.198.163.12 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass 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="NkMKxP0Q" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1767079454; x=1798615454; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=wnpihVohUzCwwn8naLQMKXTDQIeEvoWSciTYk0XlrJA=; b=NkMKxP0QFGb0PHi+KdIWlkOLgrBHbeluJCDwRj+MsP+jr+lv2ghvj+h5 wK9poHMuZtceNf8O1GuatwjeaW0wzbJOjOakeqkLqJ/14glKDbWyaaiDx hzzrAIzSc82yBtQbgtFrRj7PA1A8W8YQFc7+xvypETynHE4VqWmQqcdq0 IrqVJDBu/wQHZzWhI7UQ57FwadbxI1QIgTqztQsLJ4Gr9NykYh7T5rZDh RL0ipnpn9sMXAfVdnGEsTXcjchzL0zNzMuGHXRpF8kaKV9Cx1rf3OC2yi yZRWmniyW4ZA5+D6BJtq7LZuS3JjCvQyXIsE7YgKHbj2x+kEh6HvjMVhe w==; X-CSE-ConnectionGUID: RB5hAb/BSB2va1aYJmwsLQ== X-CSE-MsgGUID: dfCh0VMhTdajMinE5jsIUA== X-IronPort-AV: E=McAfee;i="6800,10657,11656"; a="72523307" X-IronPort-AV: E=Sophos;i="6.21,188,1763452800"; d="scan'208";a="72523307" Received: from orviesa009.jf.intel.com ([10.64.159.149]) by fmvoesa106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Dec 2025 23:24:13 -0800 X-CSE-ConnectionGUID: GQKFI+DITNOXuVBdhxXIhA== X-CSE-MsgGUID: WdyIWta4R2WFZUR96wUJxA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.21,188,1763452800"; d="scan'208";a="200912615" Received: from black.igk.intel.com ([10.91.253.5]) by orviesa009.jf.intel.com with ESMTP; 29 Dec 2025 23:24:12 -0800 Received: by black.igk.intel.com (Postfix, from userid 1001) id 665198E; Tue, 30 Dec 2025 08:24:11 +0100 (CET) Date: Tue, 30 Dec 2025 08:24:11 +0100 From: Mika Westerberg To: Jayi Li Cc: linux-kernel@vger.kernel.org Subject: Re: Question about commit 8cf9926c537c (thunderbolt: Reset only non-USB4 host routers in resume) Message-ID: <20251230072411.GC2275908@black.igk.intel.com> References: 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 In-Reply-To: Hi, On Thu, Dec 25, 2025 at 03:22:29PM +0800, Jayi Li wrote: > Hi Mika, > > Sorry to bother. I have a question about the above commit that I couldn't > figure out, and I'd really appreciate it if you could help. > > The commit message says: "There is no need to reset the USB4 host routers on > resume because they are reset already."But aside from `nhi_probe`, > > I haven't found where this reset occurs in the resume path. Could you please > clarify where this automatic reset happens or the rationale behind it? It's done when the router enters Sleep state so there is no need to do reset on the SW side.