diff options
| author | Quentin Schulz <[email protected]> | 2025-04-18 14:08:20 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2025-04-25 11:21:45 +0000 |
| commit | 495df45f38c8ba3d74c3180a0a13a0ecbfa717d1 (patch) | |
| tree | 61694f4834a66bdb8da7d427298e222183cedcac /drivers/fpga/tests/fpga-bridge-test.c | |
| parent | usb: typec: ucsi: fix Clang -Wsign-conversion warning (diff) | |
| download | kernel-495df45f38c8ba3d74c3180a0a13a0ecbfa717d1.tar.gz kernel-495df45f38c8ba3d74c3180a0a13a0ecbfa717d1.zip | |
dt-bindings: usb: usb-device: relax compatible pattern to a contains
The dt-core typically allows multiple compatibles[1] but usb-device
currently forces a single compatible.
This is an issue when multiple devices with slightly different productID
all behave the same. This would require the driver to keep updating its
compatible matching table to include this new productID instead of doing
what is usually done: have two compatibles, the leftmost which matches
exactly the HW device definition, and the rightmost one as a fallback
which is assumed to be 100% compatible with the device at hand. If this
assumption turns out to be wrong, it is easy to work around this without
having to modify the device tree by handling the leftmost compatible in the driver.
[1] https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/dt-core.yaml#L21-L25
Signed-off-by: Quentin Schulz <[email protected]>
Reviewed-by: Rob Herring (Arm) <[email protected]>
Link: https://lore.kernel.org/r/20250418-dt-binding-usb-device-compatibles-v2-1-b3029f14e800@cherry.de
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'drivers/fpga/tests/fpga-bridge-test.c')
0 files changed, 0 insertions, 0 deletions