From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 170/170] arch/arm64/boot/dts/mediatek/mt8196-evb.dtb: outproc@32970000: 'mboxes', 'mediatek,gce-events' do not match any of the regexes: 'pinctrl-[0-9]+'
Date: Wed, 5 Feb 2025 11:19:37 +0800 [thread overview]
Message-ID: <202502051146.D9fAzVmr-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: 89cb8bc425a44875dc0420914465cbc1936bef3f
commit: 86aeba22de7abd0d6a22bebfbfcdfc4722ef49af [170/170] CHROMIUM: arm64: dts: mediatek: mt8196: Add DRM CRC setting
config: arm64-randconfig-051-20250204 (https://download.01.org/0day-ci/archive/20250205/202502051146.D9fAzVmr-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
dtschema version: 2024.12.dev6+gc4da38d
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250205/202502051146.D9fAzVmr-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/202502051146.D9fAzVmr-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
arch/arm64/boot/dts/mediatek/mt8196-evb.dtb: dma-controller@32890000: mediatek,larb:0: [92, 35] is too long
from schema $id: http://devicetree.org/schemas/display/mediatek/mediatek,exdma.yaml#
arch/arm64/boot/dts/mediatek/mt8196-evb.dtb: dma-controller@32890000: 'iommus' is a required property
from schema $id: http://devicetree.org/schemas/display/mediatek/mediatek,exdma.yaml#
arch/arm64/boot/dts/mediatek/mt8196-evb.dtb: dma-controller@328a0000: 'iommus' is a required property
from schema $id: http://devicetree.org/schemas/display/mediatek/mediatek,exdma.yaml#
arch/arm64/boot/dts/mediatek/mt8196-evb.dtb: dma-controller@328b0000: 'iommus' is a required property
from schema $id: http://devicetree.org/schemas/display/mediatek/mediatek,exdma.yaml#
arch/arm64/boot/dts/mediatek/mt8196-evb.dtb: dma-controller@328c0000: 'iommus' is a required property
from schema $id: http://devicetree.org/schemas/display/mediatek/mediatek,exdma.yaml#
>> arch/arm64/boot/dts/mediatek/mt8196-evb.dtb: outproc@32970000: 'mboxes', 'mediatek,gce-events' do not match any of the regexes: 'pinctrl-[0-9]+'
from schema $id: http://devicetree.org/schemas/display/mediatek/mediatek,outproc.yaml#
arch/arm64/boot/dts/mediatek/mt8196-evb.dtb: outproc@32990000: 'oneOf' conditional failed, one must be fixed:
'interrupts' is a required property
'interrupts-extended' is a required property
from schema $id: http://devicetree.org/schemas/display/mediatek/mediatek,outproc.yaml#
arch/arm64/boot/dts/mediatek/mt8196-evb.dtb: outproc@329a0000: 'oneOf' conditional failed, one must be fixed:
'interrupts' is a required property
'interrupts-extended' is a required property
from schema $id: http://devicetree.org/schemas/display/mediatek/mediatek,outproc.yaml#
arch/arm64/boot/dts/mediatek/mt8196-evb.dtb: outproc@329b0000: 'oneOf' conditional failed, one must be fixed:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-05 3:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202502051146.D9fAzVmr-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.