From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: linux-nfc@lists.01.org
Subject: Re: [PATCH 1/7] dt-bindings: nfc: nxp, nci: convert to dtschema
Date: Sun, 10 Oct 2021 22:52:56 +0200 [thread overview]
Message-ID: <0e26d0e6-9468-63b5-a357-af4c4e7ec677@canonical.com> (raw)
In-Reply-To: <1633894316.441793.3158669.nullmailer@robh.at.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2234 bytes --]
On 10/10/2021 21:31, Rob Herring wrote:
> On Sun, 10 Oct 2021 16:23:11 +0200, Krzysztof Kozlowski wrote:
>> Convert the NXP NCI NFC controller to DT schema format.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>> ---
>> .../devicetree/bindings/net/nfc/nxp,nci.yaml | 61 +++++++++++++++++++
>> .../devicetree/bindings/net/nfc/nxp-nci.txt | 33 ----------
>> MAINTAINERS | 1 +
>> 3 files changed, 62 insertions(+), 33 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/net/nfc/nxp,nci.yaml
>> delete mode 100644 Documentation/devicetree/bindings/net/nfc/nxp-nci.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/1539010
>
>
> nfc(a)28: 'clock-frequency' is a required property
> arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dt.yaml
>
> nfc(a)28: compatible:0: 'nxp,nxp-nci-i2c' was expected
> arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dt.yaml
>
> nfc(a)28: compatible: Additional items are not allowed ('nxp,nxp-nci-i2c' was unexpected)
> arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dt.yaml
>
> nfc(a)28: compatible: ['nxp,pn547', 'nxp,nxp-nci-i2c'] is too long
> arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dt.yaml
>
> nfc(a)30: 'clock-frequency' is a required property
> arch/arm/boot/dts/ste-ux500-samsung-janice.dt.yaml
>
> nfc(a)30: compatible:0: 'nxp,nxp-nci-i2c' was expected
> arch/arm/boot/dts/ste-ux500-samsung-janice.dt.yaml
>
> nfc(a)30: compatible: Additional items are not allowed ('nxp,nxp-nci-i2c' was unexpected)
> arch/arm/boot/dts/ste-ux500-samsung-janice.dt.yaml
>
> nfc(a)30: compatible: ['nxp,pn547', 'nxp,nxp-nci-i2c'] is too long
> arch/arm/boot/dts/ste-ux500-samsung-janice.dt.yaml
>
I missed that new compatible. I'll send a patch adding nxp,nxp-nci-i2c
and try to fix the DTS (missing clock-frequency).
Best regards,
Krzysztof
next parent reply other threads:[~2021-10-10 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1633894316.441793.3158669.nullmailer@robh.at.kernel.org>
2021-10-10 20:52 ` Krzysztof Kozlowski [this message]
2021-10-10 20:58 ` [PATCH 1/7] dt-bindings: nfc: nxp, nci: convert to dtschema Krzysztof Kozlowski
2021-10-10 14:23 Krzysztof Kozlowski
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=0e26d0e6-9468-63b5-a357-af4c4e7ec677@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=linux-nfc@lists.01.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 read-only IMAP folder(s) and NNTP newsgroup(s).