From: Tony Lindgren <tony@atomide.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 01/11] ARM: dts: ti: Fix pca954x i2c-mux node names
Date: Thu, 19 Jan 2023 10:18:29 +0200 [thread overview]
Message-ID: <Y8j81dFnDQjpAorw@atomide.com> (raw)
In-Reply-To: <bc964109db8a5f29124580165e925bd3bfe36661.1669999298.git.geert+renesas@glider.be>
* Geert Uytterhoeven <geert+renesas@glider.be> [221202 18:50]:
> "make dtbs_check":
>
> arch/arm/boot/dts/am3874-iceboard.dtb: pca9548 at 70: $nodename:0: 'pca9548 at 70' does not match '^(i2c-?)?mux'
> From schema: Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml
> arch/arm/boot/dts/am3874-iceboard.dtb: pca9548 at 70: Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'i2c at 0', 'i2c at 1', 'i2c at 2', 'i2c at 3', 'i2c at 4', 'i2c at 5', 'i2c at 6', 'i2c at 7' were unexpected)
> From schema: Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml
> ...
>
> Fix this by renaming PCA954x nodes to "i2c-mux", to match the I2C bus
> multiplexer/switch DT bindings and the Generic Names Recommendation in
> the Devicetree Specification.
Applying this patch into omap-for-v6.3/dt thanks.
Tony
next prev parent reply other threads:[~2023-01-19 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 16:49 [PATCH 00/11] Fix pca954x i2c-mux node names Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 01/11] ARM: dts: ti: " Geert Uytterhoeven
2023-01-19 8:18 ` Tony Lindgren [this message]
2022-12-02 16:49 ` [PATCH 02/11] ARM: dts: aspeed: " Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 03/11] ARM: dts: imx: Fix pca9547 i2c-mux node name Geert Uytterhoeven
2022-12-31 12:39 ` Shawn Guo
2022-12-02 16:49 ` [PATCH 04/11] ARM: dts: nuvoton: Fix pca954x i2c-mux node names Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 05/11] ARM: dts: socfpga: Fix pca9548 i2c-mux node name Geert Uytterhoeven
2022-12-06 21:01 ` Dinh Nguyen
2022-12-02 16:49 ` [PATCH 06/11] ARM: dts: vf610: Fix pca9548 i2c-mux node names Geert Uytterhoeven
2022-12-31 12:39 ` Shawn Guo
2022-12-02 16:49 ` [PATCH 07/11] arm64: dts: freescale: Fix pca954x " Geert Uytterhoeven
2022-12-31 12:40 ` Shawn Guo
2022-12-02 16:49 ` [PATCH 08/11] arm64: dts: marvell: " Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 09/11] arm64: dts: renesas: ulcb-kf: Fix pca9548 " Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 10/11] MIPS: mscc: jaguar2: Fix pca9545 " Geert Uytterhoeven
2022-12-02 16:49 ` [PATCH 11/11] powerpc: dts: fsl: Fix pca954x " Geert Uytterhoeven
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=Y8j81dFnDQjpAorw@atomide.com \
--to=tony@atomide.com \
--cc=linux-aspeed@lists.ozlabs.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).