Message ID | cover.1723716331.git.stano.jakubek@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | Cleanup Spreadtrum/Unisoc ARM64 DT (part 2) | expand |
On Thu, 15 Aug 2024 12:12:21 +0200, Stanislav Jakubek wrote: > This series continues cleaning up various issues with the Spreadtrum/Unisoc > ARM64 DeviceTrees. > > Stanislav Jakubek (3): > arm64: dts: sprd: sp9860g-1h10: fix > constant-charge-voltage-max-microvolt property > arm64: dts: sprd: sc2731: fix bat-detect-gpios property > arm64: dts: sprd: sc2731: move fuel-gauge monitored-battery to device > DTS > > arch/arm64/boot/dts/sprd/sc2731.dtsi | 6 +++--- > arch/arm64/boot/dts/sprd/sp9860g-1h10.dts | 7 ++++++- > 2 files changed, 9 insertions(+), 4 deletions(-) > > -- > 2.34.1 > > > My bot found new DTB warnings on the .dts files added or changed in this series. Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings are fixed by another series. Ultimately, it is up to the platform maintainer whether these warnings are acceptable or not. No need to reply unless the platform maintainer has comments. If you already ran DT checks and didn't see these error(s), then make sure dt-schema is up to date: pip3 install dtschema --upgrade New warnings running 'make CHECK_DTBS=y sprd/sp9860g-1h10.dtb' for cover.1723716331.git.stano.jakubek@gmail.com: arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: fuel-gauge@a00: 'bat-detect-gpios', '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# arch/arm64/boot/dts/sprd/sp9860g-1h10.dtb: battery: 'internal-resistance-micro-ohms' does not match any of the regexes: '^ocv-capacity-table-[0-9]+$', 'pinctrl-[0-9]+' from schema $id: http://devicetree.org/schemas/power/supply/battery.yaml#
Hi all, not sure which tree this should go through, but could someone pick this up? It's been sitting for ~2.5 months. Thanks, Stanislav
Hi Stanislav, On Thu, 31 Oct 2024 at 02:06, Stanislav Jakubek <stano.jakubek@gmail.com> wrote: > > Hi all, > > not sure which tree this should go through, but could someone pick this up? > It's been sitting for ~2.5 months. One question is what do we do about those warnings reported by Rob's bot? Apart from that I suggest you send a pull request to soc@kernel.org directly. Thanks, Chunyan
On Thu, Oct 31, 2024 at 10:08:27AM +0800, Chunyan Zhang wrote: > Hi Stanislav, > > On Thu, 31 Oct 2024 at 02:06, Stanislav Jakubek <stano.jakubek@gmail.com> wrote: > > > > Hi all, > > > > not sure which tree this should go through, but could someone pick this up? > > It's been sitting for ~2.5 months. > > One question is what do we do about those warnings reported by Rob's bot? Hi, you're correct, we should do something about those, I'll be sending a V2 soon. Also found an issue with the 2nd patch, will write it up there. Regards, Stanislav > Apart from that I suggest you send a pull request to soc@kernel.org directly. > > Thanks, > Chunyan