On 20/11/2023 18:06, Théo Lebrun wrote: > On this platform, the controller & its wrapper are reset on resume. This > makes it have a different behavior from other platforms. > > We allow using the new compatible with a fallback onto the original > ti,j721e-usb compatible. We therefore allow using an older kernel with Where is fallback ti,j721e-usb used? Please point me to the code. > a more recent devicetree. > > Acked-by: Conor Dooley <conor.dooley@xxxxxxxxxxxxx> > Signed-off-by: Théo Lebrun <theo.lebrun@xxxxxxxxxxx> > --- > Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml b/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > index 95ff9791baea..69a222dfd9ff 100644 > --- a/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > +++ b/Documentation/devicetree/bindings/usb/ti,j721e-usb.yaml > @@ -12,11 +12,15 @@ maintainers: > properties: > compatible: > oneOf: > + - const: ti,j7200-usb > - const: ti,j721e-usb > - const: ti,am64-usb > - items: > - const: ti,j721e-usb > - const: ti,am64-usb > + - items: > + - const: ti,j721e-usb This makes little sense. It's already on the list. Twice! Don't add it third time. I am sorry, but this binding makes no sense. I mean, existing binding makes no sense, but your change is not making it anyhow better. Best regards, Krzysztof
