Hi Krzysztof, On Tue, Mar 14, 2023 at 09:01:10PM +0100, Krzysztof Kozlowski wrote: > On 14/03/2023 16:11, Markus Schneider-Pargmann wrote: > > These two new chips do not have state or wake pins. > > > > Signed-off-by: Markus Schneider-Pargmann <msp@xxxxxxxxxxxx> > > --- > > .../devicetree/bindings/net/can/tcan4x5x.txt | 11 ++++++++--- > > 1 file changed, 8 insertions(+), 3 deletions(-) > > > > diff --git a/Documentation/devicetree/bindings/net/can/tcan4x5x.txt b/Documentation/devicetree/bindings/net/can/tcan4x5x.txt > > index e3501bfa22e9..38a2b5369b44 100644 > > --- a/Documentation/devicetree/bindings/net/can/tcan4x5x.txt > > +++ b/Documentation/devicetree/bindings/net/can/tcan4x5x.txt > > @@ -4,7 +4,10 @@ Texas Instruments TCAN4x5x CAN Controller > > This file provides device node information for the TCAN4x5x interface contains. > > > > Required properties: > > - - compatible: "ti,tcan4x5x" > > + - compatible: > > + "ti,tcan4x5x" or > > + "ti,tcan4552" or > > + "ti,tcan4553" > > Awesome, they nicely fit into wildcard... Would be useful to deprecate > the wildcard at some point and switch to proper compatibles in such > case, because now they became confusing. > > Anyway: > > Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx> Thank you. Indeed the old generic name could be replaced, unfortunately I don't have a list of devices that this generic wildcard matches. Best, Markus