From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: "Sean Wang" <sean.wang@mediatek.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH 2/2] ARM: dts: mediatek: mt7623: fix efuse fallback compatible
Date: Mon, 7 Oct 2024 16:06:53 +0200 [thread overview]
Message-ID: <d9565233-090b-4931-9e9f-89725db605e3@gmail.com> (raw)
In-Reply-To: <20240617094634.23173-2-zajec5@gmail.com>
On 17/06/2024 11:46, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Fix following validation error:
> arch/arm/boot/dts/mediatek/mt7623a-rfb-emmc.dtb: efuse@10206000: compatible: 'oneOf' conditional failed, one must be fixed:
> ['mediatek,mt7623-efuse', 'mediatek,mt8173-efuse'] is too long
> 'mediatek,mt8173-efuse' was expected
> 'mediatek,efuse' was expected
> from schema $id: http://devicetree.org/schemas/nvmem/mediatek,efuse.yaml#
> arch/arm/boot/dts/mediatek/mt7623a-rfb-emmc.dtb: efuse@10206000: Unevaluated properties are not allowed ('compatible' was unexpected)
> from schema $id: http://devicetree.org/schemas/nvmem/mediatek,efuse.yaml#
>
> Fixes: 43c7a91b4b3a ("arm: dts: mt7623: add efuse nodes to the mt7623.dtsi file")
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> arch/arm/boot/dts/mediatek/mt7623.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/mediatek/mt7623.dtsi b/arch/arm/boot/dts/mediatek/mt7623.dtsi
> index 9c5a52ce9351..748f9b366897 100644
> --- a/arch/arm/boot/dts/mediatek/mt7623.dtsi
> +++ b/arch/arm/boot/dts/mediatek/mt7623.dtsi
> @@ -328,7 +328,7 @@ sysirq: interrupt-controller@10200100 {
>
> efuse: efuse@10206000 {
> compatible = "mediatek,mt7623-efuse",
> - "mediatek,mt8173-efuse";
> + "mediatek,efuse";
Angelo stated that we should move away from generic fallbacks. Although the
binding states explicitly to use "mediatek,efuse" and deprecates the standalone
"mediate,mt8173-efuse", which could the default fallback. Angelo, what do you
think, take it or re-doing the binding first?
Regards,
Matthias
> reg = <0 0x10206000 0 0x1000>;
> #address-cells = <1>;
> #size-cells = <1>;
next prev parent reply other threads:[~2024-10-07 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 9:46 [PATCH 1/2] ARM: dts: mediatek: mt7623: fix IR nodename Rafał Miłecki
2024-06-17 9:46 ` [PATCH 2/2] ARM: dts: mediatek: mt7623: fix efuse fallback compatible Rafał Miłecki
2024-10-07 14:06 ` Matthias Brugger [this message]
2024-10-08 10:02 ` AngeloGioacchino Del Regno
2024-10-08 10:03 ` [PATCH 1/2] ARM: dts: mediatek: mt7623: fix IR nodename AngeloGioacchino Del Regno
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=d9565233-090b-4931-9e9f-89725db605e3@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=zajec5@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;
as well as URLs for NNTP newsgroup(s).