devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <krzysztof.kozlowski@linaro.org>,
	<Kavyasree.Kotagiri@microchip.com>, <robh+dt@kernel.org>,
	<Nicolas.Ferre@microchip.com>, <Claudiu.Beznea@microchip.com>,
	<krzysztof.kozlowski+dt@linaro.org>
Cc: <UNGLinuxDriver@microchip.com>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] dt-bindings: mfd: atmel,flexcom: Convert to json-schema
Date: Fri, 17 Jun 2022 23:04:38 +0000	[thread overview]
Message-ID: <5f679b6c-9561-1b41-d2bb-ec3d0155d2a3@microchip.com> (raw)
In-Reply-To: <1a7fc699-6381-f2db-178f-169bc1ebf064@linaro.org>



On 18/06/2022 00:00, Krzysztof Kozlowski wrote:
> On 17/06/2022 06:07, Kavyasree Kotagiri wrote:
>> Convert the Atmel flexcom device tree bindings to json schema.
>>
>> Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
>> ---
>> v3 -> v4:
>>  - Corrected format of enum used for compatible string.
>>
>> v2 -> v3:
>>  - used enum for compatible string.
>>  - changed irq flag to IRQ_TYPE_LEVEL_HIGH in example.
>>  - fixed dtschema errors.
>>
>> v1 -> v2:
>>  - Fix title.
>>
>>  .../bindings/mfd/atmel,flexcom.yaml           | 104 ++++++++++++++++++
>>  .../devicetree/bindings/mfd/atmel-flexcom.txt |  63 -----------
>>  2 files changed, 104 insertions(+), 63 deletions(-)
>>  create mode 100644 Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml
>>  delete mode 100644 Documentation/devicetree/bindings/mfd/atmel-flexcom.txt
>>
>> diff --git a/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml b/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml
>> new file mode 100644
>> index 000000000000..fdb1645d123f
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/mfd/atmel,flexcom.yaml
>> @@ -0,0 +1,104 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/mfd/atmel,flexcom.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Atmel Flexcom (Flexible Serial Communication Unit)
>> +
>> +maintainers:
>> +  - Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
>> +
>> +description:
>> +  The Atmel Flexcom is just a wrapper which embeds a SPI controller,
>> +  an I2C controller and an USART. Only one function can be used at a
>> +  time and is chosen at boot time according to the device tree.
>> +
>> +properties:
>> +  compatible:
>> +    enum:
>> +      - atmel,sama5d2-flexcom
>> +
>> +  reg:
>> +    maxItems: 1
>> +
>> +  clocks:
>> +    maxItems: 1
>> +
>> +  "#address-cells":
>> +    const: 1
>> +
>> +  "#size-cells":
>> +    const: 1
>> +
>> +  ranges:
>> +    description:
>> +      One range for the full I/O register region. (including USART,
>> +      TWI and SPI registers).
>> +    items:
>> +      maxItems: 3
>> +
>> +  atmel,flexcom-mode:
>> +    description: |
>> +      Specifies the flexcom mode as follows:
>> +      1: USART
>> +      2: SPI
>> +      3: I2C.
>> +    $ref: /schemas/types.yaml#/definitions/uint32
>> +    enum: [1, 2, 3]
>> +
>> +patternProperties:
>> +  "^serial@[0-9a-f]+$":
>> +    description: See atmel-usart.txt for details of USART bindings.
>> +    type: object
>> +
>> +  "^spi@[0-9a-f]+$":
>> +    description: See ../spi/spi_atmel.txt for details of SPI bindings.
>> +    type: object
>> +
>> +    properties:
>> +      compatible:
>> +        const: atmel,at91rm9200-spi
>> +
>> +  "^i2c@[0-9a-f]+$":
>> +    description: See ../i2c/i2c-at91.txt for details of I2C bindings.
>> +    type: object
>> +
>> +required:
>> +  - compatible
>> +  - reg
>> +  - clocks
>> +  - "#address-cells"
>> +  - "#size-cells"
>> +  - ranges
>> +  - atmel,flexcom-mode
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> +  - |
>> +    #include <dt-bindings/interrupt-controller/arm-gic.h>
>> +
>> +    flx0: flexcom@f8034000 {
>> +          compatible = "atmel,sama5d2-flexcom";
> 
> The bindings look good, but you have here weird indentation. I don't
> remember if I pointed out this already, so in any case sorry for
> bringing it up so late. The indentation should be four spaces which
> nicely aligns with " - |".
> 
> 
> 
>> +          reg = <0xf8034000 0x200>;
>> +          clocks = <&flx0_clk>;
>> +          #address-cells = <1>;
>> +          #size-cells = <1>;
>> +          ranges = <0x0 0xf8034000 0x800>;
>> +          atmel,flexcom-mode = <2>;
>> +
>> +          spi0: spi@400 {
>> +                compatible = "atmel,at91rm9200-spi";
> 
> 4 spaces
> 
> Rob's bot also complained about compatible. Are you sure you use here
> correct compatible?

It's in Documentation/devicetree/bindings/spi/spi_atmel.txt
So that'll explain the error..

Thanks,
Conor.

Conor

  reply	other threads:[~2022-06-17 23:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 13:07 [PATCH v4 0/3] Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri
2022-06-17 13:07 ` [PATCH v4 1/3] dt-bindings: mfd: atmel,flexcom: Convert to json-schema Kavyasree Kotagiri
2022-06-17 13:58   ` Rob Herring
2022-06-20 11:45     ` Kavyasree.Kotagiri
2022-06-28 21:16       ` Rob Herring
2022-07-05  6:36         ` Kavyasree.Kotagiri
2022-06-17 23:00   ` Krzysztof Kozlowski
2022-06-17 23:04     ` Conor.Dooley [this message]
2022-06-20 11:43       ` Kavyasree.Kotagiri
2022-06-17 13:07 ` [PATCH v4 2/3] dt-bindings: mfd: atmel,flexcom: Add new compatible string for lan966x Kavyasree Kotagiri
2022-06-17 13:58   ` Rob Herring
2022-06-17 23:04   ` Krzysztof Kozlowski
2022-06-17 13:07 ` [PATCH v4 3/3] mfd: atmel-flexcom: Add support for lan966x flexcom chip-select configuration Kavyasree Kotagiri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5f679b6c-9561-1b41-d2bb-ec3d0155d2a3@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Kavyasree.Kotagiri@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).