From: Rob Herring <robh@kernel.org>
To: Stanislav Jakubek <stano.jakubek@gmail.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Ray Jui <rjui@broadcom.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] dt-bindings: i2c: brcm,kona-i2c: convert to YAML
Date: Mon, 24 Apr 2023 08:28:08 -0500 [thread overview]
Message-ID: <168234258850.2489090.5138716439435477956.robh@kernel.org> (raw)
In-Reply-To: <72ba28004afb733224f7294a146fc2a6a5a834a7.1682252615.git.stano.jakubek@gmail.com>
On Sun, 23 Apr 2023 14:40:18 +0200, Stanislav Jakubek wrote:
> Convert Broadcom Kona family I2C bindings to DT schema.
>
> Changes during conversion:
> - add used, but previously undocumented SoC-specific compatibles
> - drop references to SoCs that are not upstream
> - add supported clock frequencies according to the Linux driver [1]
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/i2c/busses/i2c-bcm-kona.c#n731
>
> Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
> ---
> Changes in v2:
> - add missing arm-gic.h include
> - fix indentation to 4 spaces
>
> .../devicetree/bindings/i2c/brcm,kona-i2c.txt | 35 -----------
> .../bindings/i2c/brcm,kona-i2c.yaml | 59 +++++++++++++++++++
> 2 files changed, 59 insertions(+), 35 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/i2c/brcm,kona-i2c.txt
> create mode 100644 Documentation/devicetree/bindings/i2c/brcm,kona-i2c.yaml
>
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/project/devicetree-bindings/patch/72ba28004afb733224f7294a146fc2a6a5a834a7.1682252615.git.stano.jakubek@gmail.com
i2c@16000: compatible:0: 'brcm,kona-i2c' is not one of ['brcm,bcm11351-i2c', 'brcm,bcm21664-i2c', 'brcm,bcm23550-i2c']
arch/arm/boot/dts/bcm23550-sparrow.dtb
i2c@16000: compatible: ['brcm,kona-i2c'] is too short
arch/arm/boot/dts/bcm23550-sparrow.dtb
i2c@17000: compatible:0: 'brcm,kona-i2c' is not one of ['brcm,bcm11351-i2c', 'brcm,bcm21664-i2c', 'brcm,bcm23550-i2c']
arch/arm/boot/dts/bcm23550-sparrow.dtb
i2c@17000: compatible: ['brcm,kona-i2c'] is too short
arch/arm/boot/dts/bcm23550-sparrow.dtb
i2c@18000: compatible:0: 'brcm,kona-i2c' is not one of ['brcm,bcm11351-i2c', 'brcm,bcm21664-i2c', 'brcm,bcm23550-i2c']
arch/arm/boot/dts/bcm23550-sparrow.dtb
i2c@18000: compatible: ['brcm,kona-i2c'] is too short
arch/arm/boot/dts/bcm23550-sparrow.dtb
i2c@1c000: compatible:0: 'brcm,kona-i2c' is not one of ['brcm,bcm11351-i2c', 'brcm,bcm21664-i2c', 'brcm,bcm23550-i2c']
arch/arm/boot/dts/bcm23550-sparrow.dtb
i2c@1c000: compatible: ['brcm,kona-i2c'] is too short
arch/arm/boot/dts/bcm23550-sparrow.dtb
next prev parent reply other threads:[~2023-04-24 13:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-23 12:39 [PATCH v2 1/2] ARM: dts: bcm23550: Add SoC-specific I2C compatible Stanislav Jakubek
2023-04-23 12:40 ` [PATCH v2 2/2] dt-bindings: i2c: brcm,kona-i2c: convert to YAML Stanislav Jakubek
2023-04-24 13:28 ` Rob Herring [this message]
2023-04-26 17:23 ` Stanislav Jakubek
2023-04-30 6:55 ` Wolfram Sang
2023-04-30 12:12 ` Krzysztof Kozlowski
2023-05-03 15:38 ` Wolfram Sang
2023-04-24 13:53 ` Krzysztof Kozlowski
2023-04-26 17:16 ` Stanislav Jakubek
2023-04-27 15:54 ` Krzysztof Kozlowski
2023-05-04 4:22 ` Wolfram Sang
2023-05-08 18:54 ` [PATCH v2 1/2] ARM: dts: bcm23550: Add SoC-specific I2C compatible Florian Fainelli
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=168234258850.2489090.5138716439435477956.robh@kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stano.jakubek@gmail.com \
/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