mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Dzmitry Sankouski <dsankouski@gmail.com>
Cc: linux-kernel@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	 Chanwoo Choi <cw00.choi@samsung.com>,
	devicetree@vger.kernel.org,
	 Krzysztof Kozlowski <krzk@kernel.org>,
	 Bjorn Andersson <andersson@kernel.org>,
	Lee Jones <lee@kernel.org>,
	 Konrad Dybcio <konradybcio@kernel.org>,
	 Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/2] starqltechn: fix max77705 device irqs
Date: Tue, 02 Sep 2025 08:17:52 -0500	[thread overview]
Message-ID: <175678731004.877933.17610642849252704344.robh@kernel.org> (raw)
In-Reply-To: <20250831-starqltechn-correct_max77705_nodes-v1-0-5f2af9d13dad@gmail.com>


On Sun, 31 Aug 2025 01:21:20 +0300, Dzmitry Sankouski wrote:
> For max77705 charger and fuelgauge subdevice, use max77705 interrupt
> controller.
> 
> Signed-off-by: Dzmitry Sankouski <dsankouski@gmail.com>
> ---
> Dzmitry Sankouski (2):
>       dt-bindings: add mfd/max77705 definitions
>       arch: arm64: sdm845: starqltechn: fix max77705 interrupts
> 
>  MAINTAINERS                                             |  1 +
>  arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dts | 13 ++++++++-----
>  include/dt-bindings/mfd/max77705.h                      | 16 ++++++++++++++++
>  3 files changed, 25 insertions(+), 5 deletions(-)
> ---
> base-commit: 3cace99d63192a7250461b058279a42d91075d0c
> change-id: 20250830-starqltechn-correct_max77705_nodes-1162dc2d9fe7
> prerequisite-change-id: 20250830-max77705_77976_charger_improvement-e3f417bfaa56:v1
> prerequisite-patch-id: 534eff3c30a7b998f90f7be9537ff54c7f68543b
> prerequisite-patch-id: 60362587901a812e50ab0e9a2cf25eeea769ef9c
> prerequisite-patch-id: 09e302f4c28ec741f2985f858d72627d15e197f0
> prerequisite-patch-id: 195796a157978c67980cdd3e1bacbd0ae677e3a3
> prerequisite-patch-id: efdf7936ffca1f97fc550118ae9a2a0795828f88
> prerequisite-patch-id: bc2ce3683ecab7a91fe2ca00d35798d0f4ea5f80
> prerequisite-patch-id: 2547b245dce99798d36835b1d729b21b6d1906e5
> prerequisite-patch-id: 30d3ca50e1b09abd360ddf33982223cce24c6859
> prerequisite-patch-id: deac1d76b95764903b7b6c937d7d4b43ed9f74ed
> prerequisite-change-id: 20250831-max77705-fix_interrupt_handling-0889cee6936d:v1
> prerequisite-patch-id: f2f0ada814ee906cdc40b88427650d08b89a5d1a
> 
> Best regards,
> --
> Dzmitry Sankouski <dsankouski@gmail.com>
> 
> 
> 


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


This patch series was applied (using b4) to base:
 Base: using specified base-commit 3cace99d63192a7250461b058279a42d91075d0c
 Deps: looking for dependencies matching 10 patch-ids
 Deps: Applying prerequisite patch: [PATCH 1/9] power: supply: max77705_charger: move active discharge setting to mfd parent
 Deps: Applying prerequisite patch: [PATCH 2/9] power: supply: max77705_charger: refactoring: rename charger to chg
 Deps: Applying prerequisite patch: [PATCH 3/9] power: supply: max77705_charger: use regfields for config registers
 Deps: Applying prerequisite patch: [PATCH 4/9] power: supply: max77705_charger: return error when config fails
 Deps: Applying prerequisite patch: [PATCH 5/9] power: supply: max77705_charger: add writable properties
 Deps: Applying prerequisite patch: [PATCH 6/9] power: supply: max77705_charger: rework interrupts
 Deps: Applying prerequisite patch: [PATCH 7/9] power: supply: max77705_charger: use REGMAP_IRQ_REG_LINE macro
 Deps: Applying prerequisite patch: [PATCH 8/9] power: supply: max77705_charger: implement aicl feature
 Deps: Applying prerequisite patch: [PATCH 9/9] power: supply: max77976_charger: fix constant current reporting
 Deps: Applying prerequisite patch: [PATCH] mfd: max77705: rework interrupts

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/qcom/' for 20250831-starqltechn-correct_max77705_nodes-v1-0-5f2af9d13dad@gmail.com:

arch/arm64/boot/dts/qcom/sdm845-samsung-starqltechn.dtb: pmic@66 (maxim,max77705): '#address-cells', '#interrupt-cells', '#size-cells', 'interrupt-controller' do not match any of the regexes: '^pinctrl-[0-9]+$'
	from schema $id: http://devicetree.org/schemas/mfd/maxim,max77705.yaml#






      parent reply	other threads:[~2025-09-02 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-30 22:21 Dzmitry Sankouski
2025-08-30 22:21 ` [PATCH 1/2] dt-bindings: add mfd/max77705 definitions Dzmitry Sankouski
2025-08-31 10:05   ` Dmitry Baryshkov
2025-08-31 10:25     ` Krzysztof Kozlowski
2025-08-30 22:21 ` [PATCH 2/2] arch: arm64: sdm845: starqltechn: fix max77705 interrupts Dzmitry Sankouski
2025-09-02 13:17 ` Rob Herring (Arm) [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=175678731004.877933.17610642849252704344.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dsankouski@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®