From: Rob Herring <robh@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: "Lee Jones" <lee@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Lubomir Rintel" <lkundrak@v3.sk>,
"Dmitry Osipenko" <digetx@gmail.com>,
"Shree Ramamoorthy" <s-ramamoorthy@ti.com>,
"Heiko Stuebner" <heiko@sntech.de>,
"Joseph Chen" <chenjh@rock-chips.com>,
"Chris Zhong" <zyw@rock-chips.com>,
"Zhang Qing" <zhangqing@rock-chips.com>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Andreas Kemnade" <andreas@kemnade.info>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Julien Panis" <jpanis@baylibre.com>,
"Matti Vaittinen" <mazziesaccount@gmail.com>,
"Alexander Kurz" <akurz@blala.de>,
"André Draszik" <andre.draszik@linaro.org>,
mfd@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, "Peng Fan" <peng.fan@nxp.com>
Subject: Re: [PATCH 00/10] dt-bindings: mfd: Use generic power-controller schema
Date: Wed, 5 Aug 2026 16:10:54 -0500 [thread overview]
Message-ID: <20260805211054.GA1783131-robh@kernel.org> (raw)
In-Reply-To: <20260804-mfd-syspower-v1-0-a440783c2e78@nxp.com>
On Tue, Aug 04, 2026 at 10:16:35PM +0800, Peng Fan (OSS) wrote:
> The generic power-controller.yaml schema has been added to dt-schema[1],
> providing a common definition for the `system-power-controller` boolean
> property. Convert MFD bindings that locally define this property to
> instead reference the shared schema.
>
> The common change across all patches is:
> - Add a $ref to /schemas/power/power-controller.yaml#
> - Remove the local `system-power-controller` property definition
> - Switch from additionalProperties to unevaluatedProperties
>
> This is a pick of patches 2-11 from [2], rebased to linux-next/master,
> no changes. Patch 1 (the generic power-controller.yaml schema itself)
> is dropped since it has already been picked up by dt-schema.
>
> [1] https://github.com/devicetree-org/dt-schema/pull/187
> [2] https://lore.kernel.org/all/177523251875.1559844.9690289848283345069.b4-ty@b4/
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> Peng Fan (10):
> dt-bindings: mfd: ene-kb[3]930: Use generic power-controller schema
> dt-bindings: mfd: ti,tps65910: Use generic power-controller schema
> dt-bindings: mfd: rockchip,rk8x: Use generic power-controller schema
> dt-bindings: mfd: ricoh,rn5t618: Use generic power-controller schema
> dt-bindings: mfd: netronix,ntxec: Use generic power-controller schema
> dt-bindings: mfd: ti,twl: Use generic power-controller schema
> dt-bindings: mfd: ti,tps6594: Use generic power-controller schema
> dt-bindings: mfd: rohm,bd71828-pmic: Use generic power-controller schema
> dt-bindings: mfd: fsl,mc13xxx: Use generic power-controller schema
> dt-bindings: mfd: samsung,s2mpg10-pmic: Use generic power-controller schema
Can we hold off on this until at least the next cycle. This change
effectively bumps the minimum version of dtschema. While
power-controller.yaml is added to dtschema, it is not yet in a released
version. I'm not all that sure these changes are much improvement given
it is a single boolean.
Rob
next prev parent reply other threads:[~2026-08-05 21:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 14:16 [PATCH 00/10] dt-bindings: mfd: Use generic power-controller schema Peng Fan (OSS)
2026-08-04 14:16 ` [PATCH 01/10] dt-bindings: mfd: ene-kb[3]930: " Peng Fan (OSS)
2026-08-04 15:11 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 02/10] dt-bindings: mfd: ti,tps65910: " Peng Fan (OSS)
2026-08-04 15:23 ` sashiko-bot
2026-08-05 21:12 ` Rob Herring
2026-08-04 14:16 ` [PATCH 03/10] dt-bindings: mfd: rockchip,rk8x: " Peng Fan (OSS)
2026-08-04 15:30 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 04/10] dt-bindings: mfd: ricoh,rn5t618: " Peng Fan (OSS)
2026-08-04 15:34 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 05/10] dt-bindings: mfd: netronix,ntxec: " Peng Fan (OSS)
2026-08-04 15:44 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 06/10] dt-bindings: mfd: ti,twl: " Peng Fan (OSS)
2026-08-04 15:51 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 07/10] dt-bindings: mfd: ti,tps6594: " Peng Fan (OSS)
2026-08-04 15:55 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 08/10] dt-bindings: mfd: rohm,bd71828-pmic: " Peng Fan (OSS)
2026-08-04 16:01 ` sashiko-bot
2026-08-05 7:14 ` Matti Vaittinen
2026-08-04 14:16 ` [PATCH 09/10] dt-bindings: mfd: fsl,mc13xxx: " Peng Fan (OSS)
2026-08-04 16:10 ` sashiko-bot
2026-08-04 14:16 ` [PATCH 10/10] dt-bindings: mfd: samsung,s2mpg10-pmic: " Peng Fan (OSS)
2026-08-04 16:14 ` sashiko-bot
2026-08-05 21:10 ` Rob Herring [this message]
2026-08-06 1:11 ` [PATCH 00/10] dt-bindings: mfd: " Peng Fan
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=20260805211054.GA1783131-robh@kernel.org \
--to=robh@kernel.org \
--cc=akurz@blala.de \
--cc=andre.draszik@linaro.org \
--cc=andreas@kemnade.info \
--cc=chenjh@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=heiko@sntech.de \
--cc=j.neuschaefer@gmx.net \
--cc=jpanis@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=mazziesaccount@gmail.com \
--cc=mfd@lists.linux.dev \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=s-ramamoorthy@ti.com \
--cc=sebastian.reichel@collabora.com \
--cc=zhangqing@rock-chips.com \
--cc=zyw@rock-chips.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