From: Gregory CLEMENT <gregory.clement@bootlin.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v2 3/3] arm64: dts: marvell: Fix pca954x i2c-mux node names
Date: Fri, 16 Jun 2023 14:04:32 +0200 [thread overview]
Message-ID: <87fs6rhaun.fsf@BL-laptop> (raw)
In-Reply-To: <685e7539-0a2b-4bf3-9725-a7a4780c82cb@lunn.ch>
Andrew Lunn <andrew@lunn.ch> writes:
> On Tue, May 23, 2023 at 05:50:21PM +0200, Geert Uytterhoeven wrote:
>> "make dtbs_check":
>>
>> arch/arm64/boot/dts/marvell/armada-8040-mcbin.dtb: i2c-switch at 70: $nodename:0: 'i2c-switch at 70' does not match '^(i2c-?)?mux'
>> From schema: Documentation/devicetree/bindings/i2c/i2c-mux-pca954x.yaml
>> arch/arm64/boot/dts/marvell/armada-8040-mcbin.dtb: i2c-switch at 70: Unevaluated properties are not allowed ('#address-cells', '#size-cells', 'i2c at 0', 'i2c at 1', 'i2c at 2' 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.
>>
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> Reviewed-by: Philippe Mathieu-Daud? <philmd@linaro.org>
>
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>
>
> Andrew
Applied on mvebu/dt64
Thanks,
Gregory
--
Gregory Clement, Bootlin
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2023-06-16 12:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 15:50 [PATCH v2 0/3] Fix pca954x i2c-mux node names Geert Uytterhoeven
2023-05-23 15:50 ` [PATCH v2 1/3] ARM: dts: aspeed: " Geert Uytterhoeven
2023-05-23 15:50 ` [PATCH v2 2/3] ARM: dts: nuvoton: " Geert Uytterhoeven
2023-05-23 15:50 ` [PATCH v2 3/3] arm64: dts: marvell: " Geert Uytterhoeven
2023-05-23 15:55 ` Andrew Lunn
2023-06-16 12:04 ` Gregory CLEMENT [this message]
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=87fs6rhaun.fsf@BL-laptop \
--to=gregory.clement@bootlin.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).