From: "Macpaul Lin (林智斌)" <Macpaul.Lin@mediatek.com>
To: "robh@kernel.org" <robh@kernel.org>
Cc: "Pablo Sun (孫毓翔)" <pablo.sun@mediatek.com>,
"Chris-qj Chen (陳奇進)" <Chris-qj.Chen@mediatek.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"Alexandre Mergnat" <amergnat@baylibre.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"macpaul@gmail.com" <macpaul@gmail.com>,
"Bear Wang (萩原惟德)" <bear.wang@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"Sen Chu (储森)" <Sen.Chu@mediatek.com>
Subject: Re: [PATCH v3] arm64: dts: mediatek: mt6359: fix dtbs_check error for audio-codec
Date: Fri, 21 Feb 2025 07:18:31 +0000 [thread overview]
Message-ID: <7f9ddfe089a13dd70ae99cf292d00d689ae2f2fb.camel@mediatek.com> (raw)
In-Reply-To: <173992516365.2065360.13568840928707086513.robh@kernel.org>
On Tue, 2025-02-18 at 18:42 -0600, Rob Herring (Arm) wrote:
>
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>
>
> On Mon, 17 Feb 2025 19:37:36 +0800, Macpaul Lin wrote:
> > This change fixes these dtbs_check errors for audio-codec:
> > 1. pmic: 'mt6359codec' does not match any of the regexes: 'pinctrl-
> > [0-9]+'
> > - Replace device node name to generic 'audio-codec'
> > 2. pmic: regulators: 'compatible' is a required property
> > - Add 'mediatek,mt6359-codec' to compatible.
> >
[snip]
> My bot found new DTB warnings on the .dts files added or changed in
> this
> series.
Dear Angelo,
Please help to review and pick-up this patch to fix dtbs check error
for 'mt6359rtc'.
[PATCH v3] arm64: dts: mediatek: mt6359: fix dtbs_check error for RTC
and regulators
https://lore.kernel.org/all/20250214084954.1181435-1-macpaul.lin@mediatek.com/
Thanks!
> arch/arm64/boot/dts/mediatek/mt8195-cherry-tomato-r2.dtb: pmic:
> '#sound-dai-cells', 'mt6359rtc' do not match any of the regexes:
> 'pinctrl-[0-9]+'
> from schema $id:
Best regards,
Macpaul Lin
prev parent reply other threads:[~2025-02-21 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 11:37 [PATCH v3] arm64: dts: mediatek: mt6359: fix dtbs_check error for audio-codec Macpaul Lin
2025-02-18 8:54 ` AngeloGioacchino Del Regno
2025-02-19 0:42 ` Rob Herring (Arm)
2025-02-21 7:18 ` Macpaul Lin (林智斌) [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=7f9ddfe089a13dd70ae99cf292d00d689ae2f2fb.camel@mediatek.com \
--to=macpaul.lin@mediatek.com \
--cc=Chris-qj.Chen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Sen.Chu@mediatek.com \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bear.wang@mediatek.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-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=macpaul@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=pablo.sun@mediatek.com \
--cc=robh@kernel.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