That's the advantage when you use a device that doesn't have a PMIC and only goes into deep sleep mode for Off Mode. This is only supported by the proprietary, closed-source manufacturer firmware, for which of course no publicly available API description exists. Mainline support will therefore most likely not become available. So it basically just leaves reverse engineering and an out-of-tree implementation. Good luck.

moved to tvboxes

The board should have RT8821CU as wifi chip. Since Linux 6.17 there is no out of tree driver necessary anymore, mainline i used. So perhaps this is a an issue or regression upstream. You can try to switch to edge kernel, perhaps this has been addressed but not back-ported.

I compiled Linux from hardkernel–it works with the devicetree from petitboot firmware. There's a emmc-data-4b node (not in their source code) which does: &emmc_conf_pull_up { mux { drive-strength = <3>; groups = "emmc_nand_d0", "emmc_nand_d1", "emmc_nand_d2", "emmc_nand_d3"; function = "emmc"; input-enable; bias-pull-up; }; }; Trying this with mainline e.g. overlay=g12b-odroid-n2-spi isn't enough here. No option to wakeup (ir, lan, keyboard) is another reason to stick with 4.9.

Subject: Bluetooth: Unknown BR/EDR signaling command 0x16 / Wrong link type (-22) on meson-gx / Banana Pi M2 Pro Description: When connecting modern Android (POCO F7) and Windows/Linux devices (Lenovo Legion) via Bluetooth to Banana Pi M2 Pro, the dmesg log gets flooded with BR/EDR signaling errors during connection/disconnection phases. Steps taken: - Forced 'ControllerMode = bredr' in /etc/bluetooth/main.conf - Disabled USB autosuspend for the BT controller (set to -1) Logs: [ 345.122975] Bluetooth: Unknown BR/EDR signaling command 0x16 [ 345.123005] Bluetooth: Wrong link type (-22) Environment: - Board: Banana Pi M2 Pro (Amlogic S905X3) - Kernel version: 6.18.34-current-meson64 nano armbianEnv.txt extraargs=usbcore.autosuspend=-1 The problem with Bluetooth on bananapim2pro is that I constantly have trouble connecting. My tweaks to the settings fixed it somewhat, but not 100%... Finally, if all else fails, I use this method: sudo rmmod btusb sudo modprobe btusb sudo systemctl restart bluetooth sudo systemctl restart bluealsa But I have a question: are there any kernel/driver fixes or updates for this Bluetooth model?