From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Chen-Yu Tsai <wenst@chromium.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 1/3] arm64: dts: mediatek: mt8173-elm: Drop pmic's #address-cells and #size-cells
Date: Thu, 9 Jan 2025 12:12:42 +0100 [thread overview]
Message-ID: <c140449f-8572-4a8f-9e79-5269cc0115e9@collabora.com> (raw)
In-Reply-To: <20250108083424.2732375-1-wenst@chromium.org>
Il 08/01/25 09:34, Chen-Yu Tsai ha scritto:
> The PMIC has child nodes for each of its functions. It is not an actual
> bus and no addressing is involved.
>
> Dropping the bogus properties fixes a DT validation error:
>
> arch/arm64/boot/dts/mediatek/mt8173-elm.dtb: pmic: '#address-cells', '#size-cells' do not match any of the regexes: 'pinctrl-[0-9]+'
> from schema $id: http://devicetree.org/schemas/mfd/mediatek,mt6397.yaml#
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202412212322.JTFpRD7X-lkp@intel.com/
> Fixes: 689b937bedde ("arm64: dts: mediatek: add mt8173 elm and hana board")
> Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
next prev parent reply other threads:[~2025-01-09 11:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 8:34 Chen-Yu Tsai
2025-01-08 8:34 ` [PATCH 2/3] arm64: dts: mediatek: mt8173: Fix disp-pwm compatible string Chen-Yu Tsai
2025-01-09 11:12 ` AngeloGioacchino Del Regno
2025-01-08 8:34 ` [PATCH 3/3] arm64: dts: mediatek: mt8173: Fix some node names Chen-Yu Tsai
2025-01-09 11:12 ` AngeloGioacchino Del Regno
2025-01-09 11:12 ` AngeloGioacchino Del Regno [this message]
2025-02-06 11:08 ` [PATCH 1/3] arm64: dts: mediatek: mt8173-elm: Drop pmic's #address-cells and #size-cells 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=c140449f-8572-4a8f-9e79-5269cc0115e9@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=lkp@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=wenst@chromium.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
all inboxes | Powered by JetHome®