devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Sergiu.Moga@microchip.com>
To: <krzysztof.kozlowski@linaro.org>, <broonie@kernel.org>,
	<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
	<Claudiu.Beznea@microchip.com>
Cc: <linux-spi@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<Kavyasree.Kotagiri@microchip.com>,
	<UNGLinuxDriver@microchip.com>, <Tudor.Ambarus@microchip.com>
Subject: Re: [PATCH v3] spi: dt-bindings: atmel,at91rm9200-spi: convert to json-schema
Date: Wed, 13 Jul 2022 08:12:53 +0000	[thread overview]
Message-ID: <134b2da3-9f6d-2769-f9d4-33e62b3e1262@microchip.com> (raw)
In-Reply-To: <dc26dd92-c107-bb8d-b40d-71b3568c52e5@linaro.org>

On 12.07.2022 19:32, Krzysztof Kozlowski wrote:
> On 12/07/2022 18:25, Sergiu Moga wrote:
>> Convert SPI DT binding for Atmel/Microchip SoCs to json-schema.
>>
>> Signed-off-by: Sergiu Moga <sergiu.moga@microchip.com>
>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>>
>> v1 -> v2:
>> - change subject headline prefix from "dt-bindings: spi" to "spi: atmel"
>> - change maintainer
>> - kept the compatbile as items (instead of switching to enums) and at91rm9200
>> as fallback for sam9x60, since the evolution of IP's is incremental.
>> - removed unnecessay "cs-gpios" property and descriptions
>> - added min/max for fifo-size property.
>>
>>
>> v2 -> v3:
>> - change subject headline prefix from "spi: atmel" to
>> "spi: dt-bindings: atmel,at91rm9200-spi: convert to json-schema"
>> - use enum instead of a range for "atmel,fifo-size"
>>
>>
>>   .../bindings/spi/atmel,at91rm9200-spi.yaml    | 76 +++++++++++++++++++
>>   .../devicetree/bindings/spi/spi_atmel.txt     | 36 ---------
>>   2 files changed, 76 insertions(+), 36 deletions(-)
>>   create mode 100644 Documentation/devicetree/bindings/spi/atmel,at91rm9200-spi.yaml
>>   delete mode 100644 Documentation/devicetree/bindings/spi/spi_atmel.txt
>>
>> diff --git a/Documentation/devicetree/bindings/spi/atmel,at91rm9200-spi.yaml b/Documentation/devicetree/bindings/spi/atmel,at91rm9200-spi.yaml
>> new file mode 100644
>> index 000000000000..084897cc8f66
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/spi/atmel,at91rm9200-spi.yaml
>> @@ -0,0 +1,76 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +# Copyright (C) 2022 Microchip Technology, Inc. and its subsidiaries
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/spi/atmel,spi.yaml#
> You need to test the bindings.
>
My apologies, I did notice the related error locally, but I somehow 
forgot to amend the commit before formatting the patch and sending it. I 
am sorry about this.
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Atmel SPI device
>> +
>> +maintainers:
>> +  - Tudor Ambarus <tudor.ambarus@microchip.com>
>> +
>> +allOf:
>> +  - $ref: spi-controller.yaml#
>> +
>> +properties:
>> +  compatible:
>> +    oneOf:
>> +      - items:
> I missed that part - this is one item, so no "items".
You are right, should be just a const I guess. Thank you.
> Best regards,
> Krzysztof

Regards,

     Sergiu


  reply	other threads:[~2022-07-13  8:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12 16:25 [PATCH v3] spi: dt-bindings: atmel,at91rm9200-spi: convert to json-schema Sergiu Moga
2022-07-12 16:32 ` Krzysztof Kozlowski
2022-07-13  8:12   ` Sergiu.Moga [this message]
2022-07-12 22:29 ` Rob Herring
2022-07-14 14:08 ` Mark Brown

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=134b2da3-9f6d-2769-f9d4-33e62b3e1262@microchip.com \
    --to=sergiu.moga@microchip.com \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Kavyasree.Kotagiri@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=broonie@kernel.org \
    --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=linux-spi@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).