From: Rob Herring <robh@kernel.org>
To: Kavyasree Kotagiri <kavyasree.kotagiri@microchip.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
krzysztof.kozlowski@linaro.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, UNGLinuxDriver@microchip.com,
Claudiu.Beznea@microchip.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/3] dt-bindings: mfd: atmel,flexcom: Convert to json-schema
Date: Fri, 17 Jun 2022 07:58:32 -0600 [thread overview]
Message-ID: <1655474312.882258.1508989.nullmailer@robh.at.kernel.org> (raw)
In-Reply-To: <20220617130729.12072-2-kavyasree.kotagiri@microchip.com>
On Fri, 17 Jun 2022 18:37:27 +0530, 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
>
Running 'make dtbs_check' with the schema in this patch gives the
following warnings. Consider if they are expected or the schema is
incorrect. These may not be new warnings.
Note that it is not yet a requirement to have 0 warnings for dtbs_check.
This will change in the future.
Full log is available here: https://patchwork.ozlabs.org/patch/
flexcom@f0000000: spi@400:compatible:0: 'atmel,at91rm9200-spi' was expected
arch/arm/boot/dts/at91-sam9x60ek.dtb
flexcom@f0000000: spi@400:compatible: ['microchip,sam9x60-spi', 'atmel,at91rm9200-spi'] is too long
arch/arm/boot/dts/at91-sam9x60ek.dtb
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-17 13:59 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 [this message]
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
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=1655474312.882258.1508989.nullmailer@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=kavyasree.kotagiri@microchip.com \
--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).