From: Philip Li <philip.li@intel.com>
To: Marek Vasut <marex@nabladev.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
kernel test robot <lkp@intel.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
<oe-kbuild-all@lists.linux.dev>, Frank Li <Frank.Li@nxp.com>
Subject: Re: [linux-next:master 1377/10910] arch/arm64/boot/dts/freescale/imx8mm-data-modul-edm-sbc-overlay-cm4.dtb: vdev0buffer@b8400000 (shared-dma-pool): Unevaluated properties are not allowed ('no-map', 'reg' were unexpected)
Date: Tue, 29 Sep 2026 09:33:19 +0800 [thread overview]
Message-ID: <arsVX0tTq2WaVM9S@rli9-mobl> (raw)
In-Reply-To: <17c2d593-194c-47ff-9c55-b86cba82f415@nabladev.com>
On Mon, Sep 28, 2026 at 09:05:03PM +0200, Marek Vasut wrote:
> On 9/28/26 7:00 AM, Krzysztof Kozlowski wrote:
> > On 27/09/2026 20:06, Marek Vasut wrote:
> > > On 9/27/26 6:59 PM, Krzysztof Kozlowski wrote:
> > > > On 26/09/2026 01:00, Marek Vasut wrote:
> > > > > On 9/25/26 11:46 PM, kernel test robot wrote:
> > > > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > > > > > head: f5f84daefcd92d7a630066635ecea1433ed5eac7
> > > > > > commit: 9a14f327dfcbbb0fa24974cb3a928ea3d7409768 [1377/10910] arm64: dts: imx8mm: imx8mp: Add CM DTOs for Data Modul i.MX8M Mini and Plus eDM SBC
> > > > > > config: arm64-randconfig-2400-20260921 (https://download.01.org/0day-ci/archive/20260925/202609252351.5UfBIiOJ-lkp@intel.com/config)
> > > > > > compiler: aarch64-linux-gcc (GCC) 8.5.0
> > > > > > dtschema: 2026.10.dev2+g840a01d41
> > > > > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260925/202609252351.5UfBIiOJ-lkp@intel.com/reproduce)
> > > > > >
> > > > > > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > > > > > the same patch/commit), kindly add following tags
> > > > > > | Reported-by: kernel test robot <lkp@intel.com>
> > > > > > | Closes: https://lore.kernel.org/oe-kbuild-all/202609252351.5UfBIiOJ-lkp@intel.com/
> > > > > >
> > > > > > dtcheck warnings: (new ones prefixed by >>)
> > > > > > from schema $id: http://devicetree.org/schemas/reserved-memory/shared-dma-pool.yaml
> > > > > > > > arch/arm64/boot/dts/freescale/imx8mm-data-modul-edm-sbc-overlay-cm4.dtb: vdev0buffer@b8400000 (shared-dma-pool): Unevaluated properties are not allowed ('no-map', 'reg' were unexpected)
> > > > > > from schema $id: http://devicetree.org/schemas/reserved-memory/shared-dma-pool.yaml
> > > > > > --
> > > > > > from schema $id: http://devicetree.org/schemas/reserved-memory/shared-dma-pool.yaml
> > > > > > > > arch/arm64/boot/dts/freescale/imx8mp-data-modul-edm-sbc-overlay-cm7.dtb: vdev0buffer@55400000 (shared-dma-pool): Unevaluated properties are not allowed ('no-map', 'reg' were unexpected)
> > > > > > from schema $id: http://devicetree.org/schemas/reserved-memory/shared-dma-pool.yaml
> > > > > +CC krzk, I just cannot reproduce this locally. Do you know what I might
> > > > > be missing here ? Thank you !
> > > >
> > > > The things or versions listed in top of that email.
> > > Linux has plenty of examples of such shared-dma-pool/no-map entries:
> > >
> > > arch/arm64/boot/dts/freescale/imx952-evk.dts- vdev0buffer:
> > > vdev0buffer@88020000 {
> > > arch/arm64/boot/dts/freescale/imx952-evk.dts: compatible =
> > > "shared-dma-pool";
> > > arch/arm64/boot/dts/freescale/imx952-evk.dts- reg = <0 0x88020000 0
> > > 0x100000>;
> > > arch/arm64/boot/dts/freescale/imx952-evk.dts- no-map;
> > > arch/arm64/boot/dts/freescale/imx952-evk.dts- };
> > >
> > > Are those broken and need to be fixed, or is it dt-schema that is broken ?
> >
> > This could be caused by recent dtschema change, which was also recently
> > fixed. The LKP report had dtschema git version and as you can check it
> > points exactly to the version changing reserved nodes (which introduced
> > issues). Not to the latest one which fixes the issue.
> >
> > If issue is reproduced with 840a01d but not with later, then obviously
> > everything is fine.
> I can confirm that the issue does not happen with current dt-schema/main
> 5687115902ba ("schemas: reserved-memory: Fix invalid oneOf match with
> iommu-addresses") .
Sorry for the false positive report, I will fix the bot to upgrade the dtschema
to use 2026.10.dev4+g568711590 version.
>
next prev parent reply other threads:[~2026-09-29 1:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 21:46 [linux-next:master 1377/10910] arch/arm64/boot/dts/freescale/imx8mm-data-modul-edm-sbc-overlay-cm4.dtb: vdev0buffer@b8400000 (shared-dma-pool): Unevaluated properties are not allowed ('no-map', 'reg' were unexpected) kernel test robot
2026-09-25 23:00 ` Marek Vasut
2026-09-27 16:59 ` Krzysztof Kozlowski
2026-09-27 18:06 ` Marek Vasut
2026-09-28 5:00 ` Krzysztof Kozlowski
2026-09-28 19:05 ` Marek Vasut
2026-09-29 1:33 ` Philip Li [this message]
2026-09-29 3:10 ` Marek Vasut
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=arsVX0tTq2WaVM9S@rli9-mobl \
--to=philip.li@intel.com \
--cc=Frank.Li@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lkp@intel.com \
--cc=marex@nabladev.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.