Hello Toradex team,
We’re developing a product on the Luna SL1680 running Common Torizon OS 7.5.0-devel-20260123143454+build.0 (scarthgap), kernel 6.12.11-Torizon, and we’d like to request that several USB kernel drivers be enabled in the official SL1680 build.
We attach two USB peripherals that currently enumerate but have no usable driver, because the relevant class drivers aren’t compiled in the SL1680 kernel:
1. A Teensy 4.1 in USB Serial mode (CDC-ACM, VID:PID 16c0:0483) — needs the host-side CDC-ACM driver.
2. A Quectel EC200U-CN LTE modem — needs the USB serial ‘option’ driver for its AT/control ports, plus a USB-Ethernet class driver (ECM/RNDIS/NCM) for the data path.
Request: please enable the following as loadable modules (=m) in the SL1680 Torizon OS kernel:
CONFIG_USB_ACM (cdc_acm — CDC-ACM serial devices, e.g. Teensy)
CONFIG_USB_SERIAL_OPTION (option — WWAN modem AT/control ports)
CONFIG_USB_NET_CDCETHER (cdc_ether — modem ECM data mode)
CONFIG_USB_NET_RNDIS_HOST (rndis_host — modem RNDIS data mode)
Optionally, if they’re low-cost to include:
CONFIG_USB_NET_CDC_NCM (cdc_ncm — modem NCM data mode)
CONFIG_PPP / CONFIG_PPP_ASYNC (PPP dial-up over the modem serial port)
Current state on the running board:
# zcat /proc/config.gz | grep -E ‘USB_ACM|USB_SERIAL_OPTION|USB_USBNET|USB_NET_CDCETHER|USB_NET_RNDIS_HOST|USB_NET_CDC_NCM’
# CONFIG_USB_ACM is not set
# CONFIG_USB_SERIAL_OPTION is not set
# CONFIG_USB_NET_CDCETHER is not set
# CONFIG_USB_NET_RNDIS_HOST is not set
# CONFIG_USB_NET_CDC_NCM is not set
CONFIG_USB_USBNET=y
Note the usbnet framework (CONFIG_USB_USBNET) is already enabled, so only the leaf class drivers above are missing. These are all standard, widely-used USB class drivers for common serial peripherals and cellular modems, so we’d expect enabling them to be low-risk and broadly useful, with no negative impact on Torizon OS. We understand from your documentation (Building External Kernel Modules With Torizon) that in-tree config additions like these are handled on the Toradex build side, which is why we’re raising it with you.
As interim measures we’re using the generic usb-serial bind for the Teensy and can build modules externally, but having these in the base SL1680 image would let us retire those workarounds and receive the drivers via OTA.
Could you let us know whether these can be added to an upcoming SL1680 release? Happy to provide any further detail.