On 19/01/2023 18:47, Eddie James wrote: > The I2C Responder translates I2C commands to CFAM or SCOM operations, > effectively implementing an FSI master. > > Signed-off-by: Eddie James <eajames@xxxxxxxxxxxxx> > --- > .../devicetree/bindings/fsi/ibm,i2cr.yaml | 42 +++++++++++++++++++ > 1 file changed, 42 insertions(+) > create mode 100644 Documentation/devicetree/bindings/fsi/ibm,i2cr.yaml > > diff --git a/Documentation/devicetree/bindings/fsi/ibm,i2cr.yaml b/Documentation/devicetree/bindings/fsi/ibm,i2cr.yaml > new file mode 100644 > index 000000000000..929ca10988f9 > --- /dev/null > +++ b/Documentation/devicetree/bindings/fsi/ibm,i2cr.yaml > @@ -0,0 +1,42 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/fsi/ibm,i2cr.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: IBM I2C Responder virtual FSI master > + > +maintainers: > + - Eddie James <eajames@xxxxxxxxxxxxx> > + > +description: | > + This binding describes an I2C device called the I2C Responder (I2CR). The In the binding, don't write description of the binding. In the binding, write about the hardware. Rephrase it so the hardware is the subject. > + I2CR translates commands sent over I2C bus to FSI CFAM reads and writes or > + SCOM operations. The CFAM access means that the I2CR can act as an FSI > + master. > + > +properties: > + compatible: > + enum: > + - ibm,i2cr > + > + reg: > + maxItems: 1 Does not look like you tested the bindings. Please run `make dt_binding_check` (see Documentation/devicetree/bindings/writing-schema.rst for instructions). > + > +required: > + - compatible > + - reg > + > +additionalProperties: false > + > +examples: > + - | > + i2c { Use 4 spaces for example indentation. > + #address-cells = <1>; > + #size-cells = <0>; > + > + i2cr@20 { > + compatible = "ibm,i2cr"; > + reg = <0x20>; > + }; > + }; Best regards, Krzysztof
