From: Krzysztof Kozlowski <krzk@kernel.org>
To: samuel.kayode@savoirfairelinux.com, Lee Jones <lee@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sebastian Reichel <sre@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, linux-pm@vger.kernel.org,
eballetbo@gmail.com, abelvesa@linux.com, b38343@freescale.com,
yibin.gong@nxp.com, Abel Vesa <abelvesa@kernel.org>
Subject: Re: [PATCH v3 1/6] dt-bindings: mfd: add pf1550
Date: Wed, 28 May 2025 08:08:17 +0200 [thread overview]
Message-ID: <250c9bf7-c958-4383-9b3f-45b4174585c5@kernel.org> (raw)
In-Reply-To: <20250527-pf1550-v3-1-45f69453cd51@savoirfairelinux.com>
On 28/05/2025 00:25, Samuel Kayode via B4 Relay wrote:
> From: Samuel Kayode <samuel.kayode@savoirfairelinux.com>
>
> Add a DT binding document for pf1550 PMIC. This describes the core mfd
> device along with its children: regulators, charger and onkey.
>
> Signed-off-by: Samuel Kayode <samuel.kayode@savoirfairelinux.com>
> ---
> v3:
> - Address Krzysztof's feedback:
> - Fold charger and onkey objects
> - Drop compatible for sub-devices: onkey, charger and regulator.
> - Drop constant voltage property already included in
> monitored-battery
> - Fix whitespace warnings
> - Fix license
> v2:
> - Add yamls for the PMIC and the sub-devices
> ---
> Documentation/devicetree/bindings/mfd/pf1550.yaml | 139 ++++++++++++++++++++++
Filename: nothing improved.
> 1 file changed, 139 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/pf1550.yaml b/Documentation/devicetree/bindings/mfd/pf1550.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..7f22cb91eb5542c8aa616525ed1e78efa2a863d3
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mfd/pf1550.yaml
...
> +
> + patternProperties:
> + "^(ldo[1-3]|sw[1-3]|vrefddr)$":
> + type: object
> + $ref: /schemas/regulator/regulator.yaml
> + description:
> + regulator configuration for ldo1-3, buck converters(sw1-3)
> + and DDR termination reference voltage (vrefddr)
> + unevaluatedProperties: false
> +
> + additionalProperties: false
> +
> + monitored-battery:
> + $ref: /schemas/types.yaml#/definitions/phandle
> + description: |
> + A phandle to a monitored battery node that contains a valid value
> + for:
> + constant-charge-voltage-max-microvolt.
> +
> + fsl,thermal-regulation:
-celsius or whatever is in standard suffixes:
https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/property-units.yaml
> + $ref: /schemas/types.yaml#/definitions/uint32
Drop
> + description:
> + Temperature threshold for thermal regulation of charger in celsius.
But this now makes me wonder whether this should be just part of thermal
zone and get the threshold from there. I assume this is temperature of
CHARGER, not the battery. If battery, you have such properties in
battery.yaml (monitored-batter).
@Sebastian,
Are there existing bindings or devices which regulate temperature based
on thermal-zones in DT?
> + enum: [ 60, 75, 90, 105 ]
> +
> + fsl,min-system-microvolt:
> + description:
> + System specific lower limit voltage.
> + enum: [ 3500000, 3700000, 4300000 ]
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + battery: battery-cell {
> + compatible = "simple-battery";
> + constant-charge-voltage-max-microvolt = <4400000>;
> + operating-range-celsius = <0 75>;
So this looks like duplicating thermal-regulation property.
> + };
Blank line
> + #include <dt-bindings/interrupt-controller/irq.h>
> + #include <dt-bindings/input/linux-event-codes.h>
Includes go before battery-cell.
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-28 6:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 22:25 [PATCH v3 0/6] add support for pf1550 PMIC MFD-based drivers Samuel Kayode via B4 Relay
2025-05-27 22:25 ` [PATCH v3 1/6] dt-bindings: mfd: add pf1550 Samuel Kayode via B4 Relay
2025-05-28 6:08 ` Krzysztof Kozlowski [this message]
2025-05-28 17:48 ` Samuel Kayode
2025-05-27 22:25 ` [PATCH v3 2/6] mfd: pf1550: add core mfd driver Samuel Kayode via B4 Relay
2025-06-02 6:08 ` Dan Carpenter
2025-05-27 22:25 ` [PATCH v3 3/6] regulator: pf1550: add support for regulator Samuel Kayode via B4 Relay
2025-05-28 10:58 ` Mark Brown
2025-05-29 1:44 ` kernel test robot
2025-05-27 22:25 ` [PATCH v3 4/6] input: pf1550: add onkey support Samuel Kayode via B4 Relay
2025-05-28 0:20 ` Dmitry Torokhov
2025-06-02 0:42 ` Samuel Kayode
2025-05-28 16:22 ` kernel test robot
2025-05-27 22:25 ` [PATCH v3 5/6] power: supply: pf1550: add battery charger support Samuel Kayode via B4 Relay
2025-06-02 18:44 ` Markus Elfring
2025-06-04 14:08 ` Samuel Kayode
2025-05-27 22:25 ` [PATCH v3 6/6] MAINTAINERS: add an entry for pf1550 mfd driver Samuel Kayode via B4 Relay
2025-05-28 6:10 ` Krzysztof Kozlowski
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=250c9bf7-c958-4383-9b3f-45b4174585c5@kernel.org \
--to=krzk@kernel.org \
--cc=abelvesa@kernel.org \
--cc=abelvesa@linux.com \
--cc=b38343@freescale.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=eballetbo@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=samuel.kayode@savoirfairelinux.com \
--cc=sre@kernel.org \
--cc=yibin.gong@nxp.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
all inboxes | Powered by JetHome®