Lines Matching refs:class

14 device controller driver and USB device class drivers or customer applications.
40 There is an experimental implementation of the Audio class. It follows specification
74 The CDC ACM class is used as backend for different subsystems in Zephyr.
212 USB DFU class implementation is tightly coupled to :ref:`dfu` and :ref:`mcuboot_api`.
234 For the HID class interface, an IN interrupt endpoint is required for each instance,
312 issue will be fixed in the HID class implementation for the new USB support.
372 * CDC ECM class, enabled with :kconfig:option:`CONFIG_USB_DEVICE_NETWORK_ECM`
373 * CDC EEM class, enabled with :kconfig:option:`CONFIG_USB_DEVICE_NETWORK_EEM`
394 Implementing a non-standard USB class
405 * Optionally class, vendor and custom handlers
409 .. literalinclude:: ../../../../subsys/usb/device/class/loopback.c
417 .. literalinclude:: ../../../../subsys/usb/device/class/loopback.c
425 .. literalinclude:: ../../../../subsys/usb/device/class/loopback.c
433 class driver through the registered vendor handler.
435 For the loopback class driver, :c:func:`loopback_vendor_handler` processes
438 .. literalinclude:: ../../../../subsys/usb/device/class/loopback.c
444 The class driver waits for the :makevar:`USB_DC_CONFIGURED` device status code
453 host, such as a HID class device that implements a keyboard. A function
456 endpoint is required to implement a HID class device, and no endpoints are
457 required to implement a USB DFU class. A USB device that combines functions is
458 a multifunction USB device, for example, a combination of a HID class device
482 one or more CDC ACM and one or more CDC ECM class implementations is possible
485 Interface and endpoint descriptors of built-in USB class/function
492 means that the device side class/function in the Zephyr RTOS must check the