On Tue, Aug 29, 2023 at 02:06:38PM -0700, Wesley Cheng wrote:
Add a new definition for specifying how many XHCI secondary interrupters can be allocated. XHCI in general can potentially support up to 1024 interrupters, which some uses may want to limit depending on how many users utilize the interrupters.
Signed-off-by: Wesley Cheng quic_wcheng@quicinc.com
.../devicetree/bindings/usb/snps,dwc3.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/snps,dwc3.yaml b/Documentation/devicetree/bindings/usb/snps,dwc3.yaml index a696f23730d3..596762ef9b9f 100644 --- a/Documentation/devicetree/bindings/usb/snps,dwc3.yaml +++ b/Documentation/devicetree/bindings/usb/snps,dwc3.yaml @@ -376,6 +376,19 @@ properties: items: enum: [1, 4, 8, 16, 32, 64, 128, 256]
- snps,num-hc-interrupters:
Why do you still have this when you defined a common property?
If you want to limit it here, just do:
num-hc-interrupters: maximum: 8
- description:
Defines the maximum number of XHCI host controller interrupters that can
be supported. The XHCI host controller has support to allocate multiple
event rings, which can be assigned to different clients/users. The DWC3
controller has a maximum of 8 interrupters. If this is not defined then
the value will be defaulted to 1. This parameter is used only when
operating in host mode.
- $ref: /schemas/types.yaml#/definitions/uint8
- minimum: 1
- maximum: 8
- default: 1
- port: $ref: /schemas/graph.yaml#/properties/port description: