Re: [EXT] Re: [PATCH] arm64: dts: imx93-11x11-frdm: enable additional devices

[Francesco Valla <francesco@valla.it>]

Hi Joseph,

On lunedì 8 giugno 2026 07:14:24 Ora legale dell’Europa centrale Joseph Guo 
wrote:
> On 6/5/2026 7:36 PM, Francesco Valla wrote:
> > Caution: This is an external email. Please take care when clicking links
> > or opening attachments. When in doubt, report the message using the
> > 'Report this email' button
> > 
> > 
> > Hi Joseph,
> > 
> > On venerdì 5 giugno 2026 10:59:08 Ora legale dell’Europa centrale Joseph
> > Guo> 
> > wrote:
> >> On Thu, Jan 15, 2026 at 06:11:34PM +0100, Francesco Valla wrote:
> >>> Enable additional devices on the i.MX93 FRDM board:
> >>>   - CAN port and associated transceiver
> >>>   - Bluetooth portion of the IW612 chipset
> >>>   - WiFi SDIO port
> >>>   - user buttons
> >>> 
> >>> The WiFi portion of the on-board IW612 chipset is still not supported
> >>> upstream, but since SDIO is a discoverable bus it will be probed once it
> >>> is.
> >>> 
> >>> Signed-off-by: Francesco Valla <francesco@valla.it>
> >>> ---
> > 
> > [...]
> > 
> >> Hi Francesco,
> >> 
> >> Do you ever tried bluetooth feature? The bluetooth failed to scan with
> >> 'device-wakeup-gpios' property.
> >> 
> >> Regards,
> >> Joseph
> > 
> > Yes, Bluetooth was tested using bluetoothctl, I just briefly re-tested it
> > with latest master branch (7.1.0-rc6).
> > 
> > Can you clarify what you mean with "The bluetooth failed to scan
> > with 'device-wakeup-gpios' property."?
> 
> Hi Francesco,
> 
> If 'device-wakeup-gpios' property is set. The bluetoothctl can work, but
> errors will show up if try to scan the bluetooth devices.
> 
> [bluetoothctl]> scan on
> SetDiscoveryFilter success
> Failed to start discovery: org.bluez.Error.InProgress
> hci0 class of device changed: 0x000000
> hci0 new_settings: bondable ssp br/edr le secure-conn cis-central
> cis-peripheral iso-broadcaster sync-receiver ll-privacy past-sender
> past-receiver [CHG] Controller 20:BA:36:5C:B0:D8 Class: 0x00000000 (0)
> [CHG] Controller 20:BA:36:5C:B0:D8 Powered: no
> [CHG] Controller 20:BA:36:5C:B0:D8 Discovering: no
> [CHG] Controller 20:BA:36:5C:B0:D8 PowerState: on
> [bluetoothctl]> discoverable on
> Failed to set discoverable on: org.bluez.Error.Failed
> 
> After remove the 'device-wakeup-gpios' node. The bluetooth can work
> normally.

This is not my experience:

[bluetoothctl]> scan on
SetDiscoveryFilter success
hci0 type 7 discovering on
Discovery started
[CHG] Controller B8:F4:4F:AA:9D:1C Discovering: yes
[NEW] Device C4:DE:E2:52:B9:96 BWT Perla BLue 16L 0025-003A

[bluetoothctl]> discoverable on
hci0 new_settings: powered connectable bondable ssp br/edr le secure-conn cis-
central cis-peripheral iso-broadcaster sync-receiver ll-privacy past-sender 
past-receiver 
[CHG] Controller B8:F4:4F:AA:9D:1C Connectable: yes
hci0 new_settings: powered connectable discoverable bondable ssp br/edr le 
secure-conn cis-central cis-peripheral iso-broadcaster sync-receiver ll-
privacy past-sender past-receiver 
Changing discoverable on succeeded
[CHG] Controller B8:F4:4F:AA:9D:1C Discoverable: yes


I also enabled the driver debug prints (through #define DEBUG) and can confirm
that the GPIO is being driven:

root@imx93-11x11-frdm:~# dmesg|grep h2c
[   13.524321] hci0: Set Wakeup Method response: status=0, h2c_wakeupmode=4
[   15.586748] hci0: Set h2c_ps_gpio: high
[   28.459963] hci0: Set h2c_ps_gpio: low
[   32.034623] hci0: Set h2c_ps_gpio: high

Maybe we have a different board revision? Do you know if there is a way I can
read mine?


Regards,
Francesco