From: Dinh Nguyen <dinguyen@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH 05/11] ARM: dts: socfpga: Fix pca9548 i2c-mux node name
Date: Tue, 6 Dec 2022 15:01:54 -0600 [thread overview]
Message-ID: <98a97883-3303-20eb-5a18-cfa00af9443e@kernel.org> (raw)
In-Reply-To: <a7bcc2de6c2c0946f56b2d9f9584c55cf28545dc.1669999298.git.geert+renesas@glider.be>
On 12/2/22 10:49, Geert Uytterhoeven wrote:
> "make dtbs_check":
>
> arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dtb: i2cswitch at 70: $nodename:0: 'i2cswitch at 70' does not match '^(i2c-?)?mux'
> From schema: Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml
> arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dtb: i2cswitch 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 the PCA9548 node to "i2c-mux", to match the I2C bus
> multiplexer/switch DT bindings and the Generic Names Recommendation in
> the Devicetree Specification.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts b/arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts
> index f24f17c2f5ee6bc4..e0630b0eed036d35 100644
> --- a/arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts
> +++ b/arch/arm/boot/dts/socfpga_cyclone5_vining_fpga.dts
> @@ -141,7 +141,7 @@ at24 at 50 {
> reg = <0x50>;
> };
>
> - i2cswitch at 70 {
> + i2c-mux at 70 {
> compatible = "nxp,pca9548";
> #address-cells = <1>;
> #size-cells = <0>;
Applied!
Thanks,
Dinh
next prev parent reply other threads:[~2022-12-06 21:01 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
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 [this message]
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=98a97883-3303-20eb-5a18-cfa00af9443e@kernel.org \
--to=dinguyen@kernel.org \
--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).