On Thu, Jun 5, 2025 at 9:14 AM Alexey Charkov [off-list ref] wrote:
On Thu, Jun 5, 2025 at 10:32 AM Alexey Charkov [off-list ref] wrote:
quoted
On Thu, Jun 5, 2025 at 6:43 AM Jimmy Hon [off-list ref] wrote:
quoted
quoted
+&sdio {
+ bus-width = <4>;
+ cap-sdio-irq;
+ disable-wp;
+ keep-power-in-suspend;
+ mmc-pwrseq = <&sdio_pwrseq>;
+ no-sd;
+ no-mmc;
+ non-removable;
+ sd-uhs-sdr50;
+ sd-uhs-sdr104;
+ vmmc-supply = <&vcc_3v3_s3>;
+ vqmmc-supply = <&vcc_1v8_s3>;
+ wakeup-source;
+ status = "okay";
+};
When you enable the sdio node on your v1.2 board with the broadcom
chip (using SYN43752), does the btsdio.ko bind to the device and
create an extra rfkill bluetooth node?
Good question, I didn't have it enabled in my build:
# CONFIG_BT_HCIBTSDIO is not set
Let me add it and report back.
So I've rebuilt it with btsdio.ko module enabled. As I boot the
system, WiFi (via SDIO) and Bluetooth (via UART) drivers get probed
and load their respective firmwares. btsdio.ko doesn't get
auto-loaded. If I load it manually after booting, it doesn't bind to
anything and doesn't create any extra rfkill nodes.
Is there anything else I need to check or look out for?
Best regards,
Alexey
That should be all you need to check. I guess they stopped incorrectly
advertising SDIO_DEVICE_CLASS for bluetooth.
Jimmy