From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; dkim=none Received: from mx3.molgen.mpg.de (mx3.molgen.mpg.de [141.14.17.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2479EB5; Sun, 19 Nov 2023 23:52:38 -0800 (PST) Received: from [192.168.0.183] (ip5f5af683.dynamic.kabel-deutschland.de [95.90.246.131]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id 7D62961E5FE01; Mon, 20 Nov 2023 08:52:20 +0100 (CET) Message-ID: Date: Mon, 20 Nov 2023 08:52:19 +0100 Precedence: bulk X-Mailing-List: linux-usb@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Qualcomm Atheros QCA61x4 keeps drawing 0.85 W despite Bluetooth being disable in GNOME Content-Language: en-US To: Alan Stern Cc: Marcel Holtmann , Johan Hedberg , Luiz Augusto von Dentz , linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, linux-pm@vger.kernel.org, Hans de Goede , Mike Jones References: <22494842-a785-4151-915d-6f3a677d96cb@molgen.mpg.de> <1f3cb0cc-4bb0-471f-a785-a5d237cd46a3@rowland.harvard.edu> From: Paul Menzel In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Dear Alan, Than you again for your quick reply. Am 20.11.23 um 03:26 schrieb Alan Stern: > On Sun, Nov 19, 2023 at 11:09:32PM +0100, Paul Menzel wrote: >> $ sudo modprobe btusb > >> $ grep . /sys/bus/usb/devices/1-3/power/* >> /sys/bus/usb/devices/1-3/power/active_duration:119053224 >> /sys/bus/usb/devices/1-3/power/async:enabled >> /sys/bus/usb/devices/1-3/power/autosuspend:2 >> /sys/bus/usb/devices/1-3/power/autosuspend_delay_ms:2000 >> /sys/bus/usb/devices/1-3/power/connected_duration:148065372 >> /sys/bus/usb/devices/1-3/power/control:auto >> /sys/bus/usb/devices/1-3/power/level:auto >> /sys/bus/usb/devices/1-3/power/persist:1 >> /sys/bus/usb/devices/1-3/power/runtime_active_kids:0 >> /sys/bus/usb/devices/1-3/power/runtime_active_time:119060567 >> /sys/bus/usb/devices/1-3/power/runtime_enabled:enabled >> /sys/bus/usb/devices/1-3/power/runtime_status:active >> /sys/bus/usb/devices/1-3/power/runtime_suspended_time:28831453 >> /sys/bus/usb/devices/1-3/power/runtime_usage:0 >> /sys/bus/usb/devices/1-3/power/wakeup:disabled >> ``` > > Hmmm. It's not immediately clear why the device isn't being suspended. > The btusb driver does support autosuspend. > > Can you also post the output from > > grep . /sys/bus/usb/devices/1-3:*/power/* > > with the driver module loaded? I should have asked for it before. ``` $ sudo modprobe btusb $ sudo dmesg | tail -9 [319747.390712] r8152 4-1.2:1.0 enx18dbf22dccf3: carrier on [320256.946094] bluetooth hci0: firmware: direct-loading firmware qca/rampatch_usb_00000302.bin [320256.949333] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000302.bin [320256.949349] Bluetooth: hci0: QCA: patch rome 0x302 build 0x3e8, firmware rome 0x302 build 0x111 [320256.949643] usbcore: registered new interface driver btusb [320257.308935] bluetooth hci0: firmware: direct-loading firmware qca/nvm_usb_00000302.bin [320257.309043] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000302.bin [320257.336220] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported. [320257.638188] Bluetooth: MGMT ver 1.22 $ /sbin/rfkill ID TYPE DEVICE SOFT HARD 1 wlan phy0 blocked unblocked 28 bluetooth hci0 blocked unblocked $ grep . /sys/bus/usb/devices/1-3:*/power/* /sys/bus/usb/devices/1-3:1.0/power/async:enabled /sys/bus/usb/devices/1-3:1.0/power/runtime_active_kids:0 /sys/bus/usb/devices/1-3:1.0/power/runtime_enabled:enabled /sys/bus/usb/devices/1-3:1.0/power/runtime_status:suspended /sys/bus/usb/devices/1-3:1.0/power/runtime_usage:0 /sys/bus/usb/devices/1-3:1.1/power/async:enabled /sys/bus/usb/devices/1-3:1.1/power/runtime_active_kids:0 /sys/bus/usb/devices/1-3:1.1/power/runtime_enabled:enabled /sys/bus/usb/devices/1-3:1.1/power/runtime_status:suspended /sys/bus/usb/devices/1-3:1.1/power/runtime_usage:0 ``` For completeness: ``` $ grep . /sys/bus/usb/devices/1-3/power/* /sys/bus/usb/devices/1-3/power/active_duration:120462288 /sys/bus/usb/devices/1-3/power/async:enabled /sys/bus/usb/devices/1-3/power/autosuspend:2 /sys/bus/usb/devices/1-3/power/autosuspend_delay_ms:2000 /sys/bus/usb/devices/1-3/power/connected_duration:155617216 /sys/bus/usb/devices/1-3/power/control:auto /sys/bus/usb/devices/1-3/power/level:auto /sys/bus/usb/devices/1-3/power/persist:1 /sys/bus/usb/devices/1-3/power/runtime_active_kids:0 /sys/bus/usb/devices/1-3/power/runtime_active_time:120468920 /sys/bus/usb/devices/1-3/power/runtime_enabled:enabled /sys/bus/usb/devices/1-3/power/runtime_status:active /sys/bus/usb/devices/1-3/power/runtime_suspended_time:34969407 /sys/bus/usb/devices/1-3/power/runtime_usage:0 /sys/bus/usb/devices/1-3/power/wakeup:disabled ``` >> ``` >> $ sudo modprobe -r btusb >> $ sudo dmesg | tail -1 >> [314106.155163] usbcore: deregistering interface driver btusb >> $ grep . /sys/bus/usb/devices/1-3/power/* >> /sys/bus/usb/devices/1-3/power/active_duration:119072176 >> /sys/bus/usb/devices/1-3/power/async:enabled >> /sys/bus/usb/devices/1-3/power/autosuspend:2 >> /sys/bus/usb/devices/1-3/power/autosuspend_delay_ms:2000 >> /sys/bus/usb/devices/1-3/power/connected_duration:148320980 >> /sys/bus/usb/devices/1-3/power/control:auto >> /sys/bus/usb/devices/1-3/power/level:auto >> /sys/bus/usb/devices/1-3/power/persist:1 >> /sys/bus/usb/devices/1-3/power/runtime_active_kids:0 >> /sys/bus/usb/devices/1-3/power/runtime_active_time:119079518 >> /sys/bus/usb/devices/1-3/power/runtime_enabled:enabled >> /sys/bus/usb/devices/1-3/power/runtime_status:suspended >> /sys/bus/usb/devices/1-3/power/runtime_suspended_time:29068110 >> /sys/bus/usb/devices/1-3/power/runtime_usage:0 >> /sys/bus/usb/devices/1-3/power/wakeup:disabled >> ``` > > Okay, and here we see that without the driver, the device does get > suspended. Indeed. Thank you for pointing at `runtime_status:suspended` compared to `runtime_status:active`. Kind regards, Paul