Allocate 0x837C-0x837D for TEILE Elektronik MIB GmbH DSP#321
Merged
Spritetm merged 1 commit intoJun 2, 2026
Conversation
Two PIDs for a single ESP32-P4 based DSP product with two USB boot modes: - 0x837C: UAC2.0 audio composite + custom DFU/RPC interface - 0x837D: vendor-specific remote-control interface (alternative mode) The host distinguishes the active mode by PID. A custom PID is needed because the vendor-specific interface uses a non-standard host driver rather than the default TinyUSB class PIDs.
Member
|
Looks good, merged! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Device description
A digital signal processor (DSP) audio product. It exposes two USB personalities selected by its boot mode, and the host recognizes which mode is active by the PID:
Chip
ESP32-P4 (using its native USB interface).
Why a custom PID is needed
The vendor-specific remote-control protocol uses a non-standard host driver rather than the default TinyUSB class drivers, so the pre-allocated TinyUSB PIDs don't apply. Two PIDs are required because the product has two distinct boot modes presenting different USB descriptors, and the host distinguishes them by PID.
Company
TEILE Elektronik MIB GmbH. This is a proprietary product.