From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sendmail.purelymail.com (sendmail.purelymail.com [34.202.193.197]) (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 AA6D83AA1B8 for ; Tue, 28 Jul 2026 13:18:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=34.202.193.197 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785244696; cv=none; b=UlnZcx3tZdgDkUZTevWNQYmVH0Y7+vRmPttbgJlJfZ5Wh/Owxfd1FvK0IJ2U/LzRrX2geZgyeKt8p93/Jn/QEHZ7EiQbvIm00HvMIJ+s2bMX0QDDMDZC0crduIlCuEMDpJkJk6VCRCNsXQlUJHerXXReaZfksGphkXSvvMi+D08= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785244696; c=relaxed/simple; bh=k/0bgHTdGeiys2OlIJV0qG7DjpYC2Czq9ewKhCiKYM4=; h=Content-Type:Date:Message-Id:Subject:Cc:From:To:Mime-Version: References:In-Reply-To; b=FuPZYsGhus5fzYtRWQcpeFNUQUO221TE9UEt1iDVcAfNwk0rXNKsir6gJmbFLaFWXjcrekvJydzUmaCF5V2PEIotWOdhh7UAIBHe7iv2dsRARKwIdXHFReOsPwNjKfgK1G6K57ujTk9U3YrwOE2/h1t6kpIJgFPe3vfpi5Jf1vE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=rcpassos.me; spf=pass smtp.mailfrom=rcpassos.me; dkim=pass (2048-bit key) header.d=rcpassos.me header.i=@rcpassos.me header.b=dR9iiudj; dkim=pass (2048-bit key) header.d=purelymail.com header.i=@purelymail.com header.b=ilj05tAF; arc=none smtp.client-ip=34.202.193.197 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=rcpassos.me Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=rcpassos.me Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=rcpassos.me header.i=@rcpassos.me header.b="dR9iiudj"; dkim=pass (2048-bit key) header.d=purelymail.com header.i=@purelymail.com header.b="ilj05tAF" Authentication-Results: purelymail.com; auth=pass DKIM-Signature: a=rsa-sha256; b=dR9iiudjgExkdeow1Z6EoPkyeGEv5ki2UFYQ6JNfpjHbVS4LK4i2/HhO4o2ToS/Y25oTBtm8jOXp2hXsL15zNNjctUKebjMhp75ISz6dh7YEfy5XOcfbDm9ijIWgLY+pwHPv9aBDqBMWLw4WpFtnyh/o1A+ntiOqPvO2S/JbgLq3U/nAsiP5S1Pxgo377Xqibh1XsPBUYaJM/rPGz+5NCZbNltseSSSqexcpa1/xO5/WeR1IHM/IEHib7ylFWy4/kyWEU2UJ6o0uiQCAqJ/dp164dDnua9yCboD+vWp5Is8JGBfMTKTeV0/59gHhAAlnVvQ7kSAjlAntU2QE4nD/5A==; s=purelymail3; d=rcpassos.me; v=1; bh=k/0bgHTdGeiys2OlIJV0qG7DjpYC2Czq9ewKhCiKYM4=; h=Received:Date:Subject:From:To; DKIM-Signature: a=rsa-sha256; b=ilj05tAFxt5IMxAIfuiA7RFAd0BEWl7iUxIgnodeOcbqdnqqfM+heIZg5NVsrCpN8kdBEj2SpYiXQ9GGMrvRKc3d5BEAqDXT+uOf8/JKo32yCoFztQ0eHLjqyyreYCwldNs7ZjImRil3SZeJMFDsxGfQKhglve45S2yV+EqcrYYoJRXYuMBYuQGgX5vqQ/Gd6PMZyjAtEoVSIs/FLt2muHn3l4JmyJvkklSLeYdcqODZkWMHRQcWEIYtJ4B3aVoBdblPBUbBvU+uylJOt3kQ2ZwPPLJIdLdLaJGsLDj31CtwU6MuEVgyiVmsz0NJTJMnBhJkTfOwyTHmhXZj6VPbRA==; s=purelymail3; d=purelymail.com; v=1; bh=k/0bgHTdGeiys2OlIJV0qG7DjpYC2Czq9ewKhCiKYM4=; h=Feedback-ID:Received:Date:Subject:From:To; Feedback-ID: 45355:7809:null:purelymail X-Pm-Original-To: linux-bluetooth@vger.kernel.org Received: by smtp.purelymail.com (Purelymail SMTP) with ESMTPSA id 1312514001; (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Tue, 28 Jul 2026 13:17:52 +0000 (UTC) Content-Type: text/plain; charset=UTF-8 Date: Tue, 28 Jul 2026 10:17:49 -0300 Message-Id: Subject: Re: [PATCH v2] Bluetooth: Properly disable remote wakeup for MT7922/MT7925 on Ryzen platform Cc: "Luiz Augusto von Dentz" , =?utf-8?b?Q2hyaXMgTHUgKOmZuOeomuazkyk=?= , =?utf-8?b?V2lsbC1DWSBMZWUgKOadjuaUv+epjik=?= , =?utf-8?b?U1MgV3UgKOW3q+aGsuasoyk=?= , , , , From: "Rafael Passos" To: "Rong Zhang" , "Rafael Passos" , "Marcel Holtmann" , "Luiz Augusto von Dentz" , "Matthias Brugger" , "AngeloGioacchino Del Regno" Precedence: bulk X-Mailing-List: linux-bluetooth@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Mailer: aerc 0.21.0 References: <20260701-btmtk-ryzen-remote-wakeup-v2-1-767ac7907472@rong.moe> <79D5F3E6-8F40-4422-BB2D-16691E377394@rong.moe> In-Reply-To: Hi again, On Mon Jul 6, 2026 at 4:39 PM -03, Rong Zhang wrote: > Hi Rafael, > > Hmm, interesting. My speculation is that it doesn't matter which options = are changed, but some changed options cause the BIOS to reinitialize someth= ing. Does resetting the BIOS settings to default help? I was unable to trigger the same issue again. It has been working fine (even when running without your patch). I believe the reset with bios config changes fixed it for good. > Could you provide more details about your device's USB and PCI topology? = Does the NIC's USB connect to one of the USB root hubs of the SoC (i.e., CP= U) or the chipset? I believe its a hub connected to the chipset. /: Bus 001.Port 001: Dev 001, Class=3Droot_hub, Driver=3Dxhci_hcd/12p, 480= M | ... |__ Port 008: Dev 004, If 0, Class=3DWireless, Driver=3Dbtusb, 480M In the block diagram on the manual [1], Key "E" Wifi is tied to the AMD PROM21 CHipset. > And I guess your device runs into the issue without any precursor? Once b= oot, try running the script below to capture more clues into dmesg, and wai= t for the issue to appear. > > #!/bin/sh > > ddcmd() > { > echo "$*" | sudo tee /proc/dynamic_debug/control; > } > > ddcmd file drivers/usb/core/hub.c +p > ddcmd file drivers/usb/core/driver.c +p > ddcmd func handle_tx_event +p Thanks for the script! I'm learning a bit with it! > I would do the below experiments if I had a buggy device like that. Some = extra hardware is required though. > > Connect another NIC (w/ Bluetooth interface) to the same M.2 port after t= riggering the enumeration failure, and see if the enumeration failure persi= sts. It is integrated (soldered) to my motherboard. [1] page 10 https://download.asrock.com/Manual/B850M%20Steel%20Legend%20WiF= i.pdf Thanks, Rafael Passos