From: Philip Li <philip.li@intel.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
Stanislav Jakubek <stano.jakubek@gmail.com>,
<oe-kbuild-all@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>
Subject: Re: [linux-next:master 3898/4224] arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: fuel-gauge@a00: 'battery-detect-gpios' is a required property
Date: Thu, 15 Aug 2024 10:19:11 +0800 [thread overview]
Message-ID: <Zr1ln0gSlaDeBhn9@rli9-mobl> (raw)
In-Reply-To: <82cde353-ca36-4272-a954-e816f551ca64@kernel.org>
On Wed, Aug 14, 2024 at 04:00:00PM +0200, Krzysztof Kozlowski wrote:
> On 13/08/2024 18:12, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 033a4691702cdca3a613256b0623b8eeacb4985e
> > commit: 0dcc203956537696e6f936eef886fde70e049f54 [3898/4224] arm64: dts: sprd: rename SDHCI and fuel gauge nodes to match bindings
> > config: arm64-randconfig-053-20240813 (https://download.01.org/0day-ci/archive/20240814/202408140049.pjQHYO6B-lkp@intel.com/config)
> > compiler: aarch64-linux-gcc (GCC) 14.1.0
> > dtschema version: 2024.6.dev10+ge5d88ac
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240814/202408140049.pjQHYO6B-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/202408140049.pjQHYO6B-lkp@intel.com/
> >
> > dtcheck warnings: (new ones prefixed by >>)
> > arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: ap-apb@70000000: $nodename:0: 'ap-apb@70000000' does not match '^([a-z][a-z0-9\\-]+-bus|bus|localbus|soc|axi|ahb|apb)(@.+)?$'
> > from schema $id: http://devicetree.org/schemas/simple-bus.yaml#
> > arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: ap-ahb: $nodename:0: 'ap-ahb' does not match '^([a-z][a-z0-9\\-]+-bus|bus|localbus|soc|axi|ahb|apb)(@.+)?$'
> > from schema $id: http://devicetree.org/schemas/simple-bus.yaml#
> > arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: aon: $nodename:0: 'aon' does not match '^([a-z][a-z0-9\\-]+-bus|bus|localbus|soc|axi|ahb|apb)(@.+)?$'
> > from schema $id: http://devicetree.org/schemas/simple-bus.yaml#
> > arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: /soc/aon/spi@40030000/pmic@0: failed to match any schema with compatible: ['sprd,sc2731']
> > arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: /soc/aon/spi@40030000/pmic@0/led-controller@200: failed to match any schema with compatible: ['sprd,sc2731-bltc']
> > arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: /soc/aon/spi@40030000/pmic@0/rtc@280: failed to match any schema with compatible: ['sprd,sc2731-rtc']
> > arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: /soc/aon/spi@40030000/pmic@0/efuse@380: failed to match any schema with compatible: ['sprd,sc2731-efuse']
> >>> arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: fuel-gauge@a00: 'battery-detect-gpios' is a required property
> > from schema $id: http://devicetree.org/schemas/power/supply/sc27xx-fg.yaml#
> >>> arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: fuel-gauge@a00: 'sprd,calib-resistance-micro-ohms' is a required property
> > from schema $id: http://devicetree.org/schemas/power/supply/sc27xx-fg.yaml#
> >>> arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: fuel-gauge@a00: 'bat-detect-gpio', 'interrupt-parent', 'interrupts' do not match any of the regexes: 'pinctrl-[0-9]+'
> > from schema $id: http://devicetree.org/schemas/power/supply/sc27xx-fg.yaml#
>
> These look like false positives. The commit only renamed the nodes, so
> all the warnings were there before, I think.
thanks for the info, we will avoid reporting similar problems on this
commit in future.
>
> Best regards,
> Krzysztof
>
>
prev parent reply other threads:[~2024-08-15 2:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 16:12 kernel test robot
2024-08-14 14:00 ` Krzysztof Kozlowski
2024-08-15 2:19 ` Philip Li [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=Zr1ln0gSlaDeBhn9@rli9-mobl \
--to=philip.li@intel.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=krzk@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=stano.jakubek@gmail.com \
/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