From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [conor:riscv-dt-for-next 2/10] arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dtb: syscon@20002000 (microchip,pic64gx-mss-top-sysreg): interrupt-controller@54:compatible:0: 'microchip,mpfs-irqmux' was expected
Date: Sat, 16 May 2026 11:34:15 +0200 [thread overview]
Message-ID: <202605161130.2bhKAGvG-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "dtcheck: binding changes may go via different trees"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Conor Dooley <conor.dooley@microchip.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git riscv-dt-for-next
head: 3869417f8996fb076998342d0db560fdd795a3a6
commit: 4ce4a46cdb2404bcd53ca58a18aeda673f37fbe9 [2/10] riscv: dts: microchip: update pic64gx gpio interrupts to better match the SoC
:::::: branch date: 17 hours ago
:::::: commit date: 11 days ago
config: riscv-randconfig-2052-20260516 (https://download.01.org/0day-ci/archive/20260516/202605161130.2bhKAGvG-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 13.4.0
dtschema: 2026.5.dev9+gdf9ad30c5
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260516/202605161130.2bhKAGvG-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/r/202605161130.2bhKAGvG-lkp@intel.com/
dtcheck warnings: (new ones prefixed by >>)
>> arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dtb: syscon@20002000 (microchip,pic64gx-mss-top-sysreg): interrupt-controller@54:compatible:0: 'microchip,mpfs-irqmux' was expected
from schema $id: http://devicetree.org/schemas/soc/microchip/microchip,mpfs-mss-top-sysreg.yaml
>> arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dtb: syscon@20002000 (microchip,pic64gx-mss-top-sysreg): interrupt-controller@54:compatible: ['microchip,pic64gx-irqmux', 'microchip,mpfs-irqmux'] is too long
from schema $id: http://devicetree.org/schemas/soc/microchip/microchip,mpfs-mss-top-sysreg.yaml
>> arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dtb: interrupt-controller@54 (microchip,pic64gx-irqmux): compatible:0: 'microchip,mpfs-irqmux' was expected
from schema $id: http://devicetree.org/schemas/soc/microchip/microchip,mpfs-irqmux.yaml
>> arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dtb: interrupt-controller@54 (microchip,pic64gx-irqmux): compatible: ['microchip,pic64gx-irqmux', 'microchip,mpfs-irqmux'] is too long
from schema $id: http://devicetree.org/schemas/soc/microchip/microchip,mpfs-irqmux.yaml
>> arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dtb: /soc/syscon@20002000/interrupt-controller@54: failed to match any schema with compatible: ['microchip,pic64gx-irqmux', 'microchip,mpfs-irqmux']
arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dtb: gpio@20120000 (microchip,pic64gx-gpio): #interrupt-cells: 2 was expected
from schema $id: http://devicetree.org/schemas/gpio/microchip,mpfs-gpio.yaml
arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dtb: gpio@20121000 (microchip,pic64gx-gpio): #interrupt-cells: 2 was expected
from schema $id: http://devicetree.org/schemas/gpio/microchip,mpfs-gpio.yaml
arch/riscv/boot/dts/microchip/pic64gx-curiosity-kit.dtb: gpio@20122000 (microchip,pic64gx-gpio): #interrupt-cells: 2 was expected
from schema $id: http://devicetree.org/schemas/gpio/microchip,mpfs-gpio.yaml
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-16 9:34 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=202605161130.2bhKAGvG-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.