On Thu, May 02, 2024 at 08:27:59PM +0200, Christoph Fritz wrote: > Add dt-bindings for serial LIN bus adapters. These adapters are > basically just LIN transceivers that are hard-wired to serial devices. > > Signed-off-by: Christoph Fritz <christoph.fritz@xxxxxxxxx> > --- > .../bindings/net/can/hexdev,lin-serdev.yaml | 32 +++++++++++++++++++ > 1 file changed, 32 insertions(+) > create mode 100644 Documentation/devicetree/bindings/net/can/hexdev,lin-serdev.yaml > > diff --git a/Documentation/devicetree/bindings/net/can/hexdev,lin-serdev.yaml b/Documentation/devicetree/bindings/net/can/hexdev,lin-serdev.yaml > new file mode 100644 > index 0000000000000..c178eb9be1391 > --- /dev/null > +++ b/Documentation/devicetree/bindings/net/can/hexdev,lin-serdev.yaml > @@ -0,0 +1,32 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/net/can/hexdev,lin-serdev.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Serial LIN Adapter > + > +description: > + LIN transceiver, mostly hard-wired to a serial device, used for communication > + on a LIN bus. > + For more details on an adapter, visit <https://hexdev.de/hexlin#tty>. > + > +maintainers: > + - Christoph Fritz <christoph.fritz@xxxxxxxxx> > + > +properties: > + compatible: > + const: hexdev,lin-serdev Maybe I've just missed something on earlier versions that I didn't read, but the name of the device on the website you link is "hexLIN", so why is "lin-serdev" used here instead? > + > +required: > + - compatible > + > +additionalProperties: false > + > +examples: > + - | > + serial { > + linbus { > + compatible = "hexdev,lin-serdev"; > + }; > + }; > -- > 2.39.2 >
Attachment:
signature.asc
Description: PGP signature
