From: Mark Brown <broonie@kernel.org>
To: samuel.kayode@savoirfairelinux.com
Cc: 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>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sebastian Reichel <sre@kernel.org>,
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 3/6] regulator: pf1550: add support for regulator
Date: Wed, 28 May 2025 11:58:58 +0100 [thread overview]
Message-ID: <99a2f5bd-5b73-4f4e-95c6-8bc03ffed90c@sirena.org.uk> (raw)
In-Reply-To: <20250527-pf1550-v3-3-45f69453cd51@savoirfairelinux.com>
[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]
On Tue, May 27, 2025 at 06:25:35PM -0400, Samuel Kayode via B4 Relay wrote:
> @@ -0,0 +1,353 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * pf1550.c - regulator driver for the PF1550
Please make the entire comment a C++ one so things look more
intentional.
> + *
> + * Copyright (C) 2016 Freescale Semiconductor, Inc.
> + * Robin Gong <yibin.gong@freescale.com>
Presumably there's been some updates since then?
> +static int pf1550_set_ramp_delay(struct regulator_dev *rdev, int ramp_delay)
> +{
> + int id = rdev_get_id(rdev);
> + unsigned int ramp_bits;
> + int ret;
> +
> + if (id > PF1550_VREFDDR)
> + return -EACCES;
> +
> + ramp_delay = 6250 / ramp_delay;
> + ramp_bits = ramp_delay >> 1;
> + ret = regmap_update_bits(rdev->regmap, rdev->desc->vsel_reg + 4, 0x10,
> + ramp_bits << 4);
Shouldn't we validate the value of ramp_delay?
> +static irqreturn_t pf1550_regulator_irq_handler(int irq, void *data)
> +{
> + switch (irq_type) {
> + case PF1550_PMIC_IRQ_SW1_LS:
> + case PF1550_PMIC_IRQ_SW2_LS:
> + case PF1550_PMIC_IRQ_SW3_LS:
> + dev_info(dev, "lowside interrupt triggered! irq_type=%d\n",
> + irq_type);
> + break;
> + case PF1550_PMIC_IRQ_SW1_HS:
> + case PF1550_PMIC_IRQ_SW2_HS:
> + case PF1550_PMIC_IRQ_SW3_HS:
> + dev_info(dev, "highside interrupt triggered! irq_type=%d\n",
> + irq_type);
> + break;
Are these under and overvoltage events which should be reported as such?
> + case PF1550_PMIC_IRQ_LDO1_FAULT:
> + case PF1550_PMIC_IRQ_LDO2_FAULT:
> + case PF1550_PMIC_IRQ_LDO3_FAULT:
> + dev_info(dev, "ldo fault triggered! irq_type=%d\n", irq_type);
> + break;
Similarly, we can report error events.
> + case PF1550_PMIC_IRQ_TEMP_110:
> + case PF1550_PMIC_IRQ_TEMP_125:
> + dev_info(dev, "thermal exception triggered! irq_type=%d\n",
> + irq_type);
> + break;
We also have an over temperature event type.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-28 10:59 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
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 [this message]
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=99a2f5bd-5b73-4f4e-95c6-8bc03ffed90c@sirena.org.uk \
--to=broonie@kernel.org \
--cc=abelvesa@kernel.org \
--cc=abelvesa@linux.com \
--cc=b38343@freescale.com \
--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®