From: Andrea della Porta <andrea.porta@suse.com>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: kernel test robot <lkp@intel.com>,
Andrea della Porta <andrea.porta@suse.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Florian Fainelli <florian.fainelli@broadcom.com>
Subject: Re: [linux-next:master 3392/8232] arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtb: /soc@107c000000/timer@7c003000: failed to match any schema with compatible: ['brcm,bcm2835-system-timer']
Date: Tue, 2 Jul 2024 11:55:56 +0200 [thread overview]
Message-ID: <ZoPOrBdevxVrrZfW@apocalypse> (raw)
In-Reply-To: <bfc60a7e-54d2-48a6-a288-4fe76d66507a@gmx.net>
Hi stefan,
On 16:53 Wed 26 Jun , Stefan Wahren wrote:
> Am 26.06.24 um 04:02 schrieb kernel test robot:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 0fc4bfab2cd45f9acb86c4f04b5191e114e901ed
> > commit: cbda7c3ffe6d78933ee8c2d5e71de60ff4f4847b [3392/8232] arm64: dts: broadcom: Add minimal support for Raspberry Pi 5
> > config: arm64-randconfig-051-20240626 (https://download.01.org/0day-ci/archive/20240626/202406260927.CS1A5Ugr-lkp@intel.com/config)
> > compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
> > dtschema version: 2024.6.dev1+g833054f
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240626/202406260927.CS1A5Ugr-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/202406260927.CS1A5Ugr-lkp@intel.com/
> >
> > dtcheck warnings: (new ones prefixed by >>)
> > arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtb: /: failed to match any schema with compatible: ['raspberrypi,5-model-b', 'brcm,bcm2712']
> > arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtb: /: failed to match any schema with compatible: ['raspberrypi,5-model-b', 'brcm,bcm2712']
Ack, will take a look asap.
> > arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtb: /soc@107c000000/mmc@fff000: failed to match any schema with compatible: ['brcm,bcm2712-sdhci', 'brcm,sdhci-brcmstb']
> I think the last one can be ignored, because the relevant dt-bindings
> change is in Ulf Hansson's tree.
Ok.
> > > > arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtb: /soc@107c000000/timer@7c003000: failed to match any schema with compatible: ['brcm,bcm2835-system-timer']
> > > > arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dtb: /soc@107c000000/local-intc@7cd00000: failed to match any schema with compatible: ['brcm,bcm2836-l1-intc']
> > > >
> I can take care of these binding conversions. But don't expect fast
> results during the summertime.
Really appreciated, many thanks.
Best regards,
Andrea
>
> Best regards
prev parent reply other threads:[~2024-07-02 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 2:02 kernel test robot
2024-06-26 14:53 ` Stefan Wahren
2024-07-02 9:55 ` Andrea della Porta [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=ZoPOrBdevxVrrZfW@apocalypse \
--to=andrea.porta@suse.com \
--cc=florian.fainelli@broadcom.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wahrenst@gmx.net \
/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