[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eb1fb4e2-42aa-4795-bc6c-dbcf1fa04f11@sirena.org.uk>
Date: Wed, 4 Jun 2025 12:35:21 +0100
From: Mark Brown <broonie@...nel.org>
To: samuel.kayode@...oirfairelinux.com
Cc: Lee Jones <lee@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Sebastian Reichel <sre@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
linux-pm@...r.kernel.org, Abel Vesa <abelvesa@...nel.org>,
Abel Vesa <abelvesa@...ux.com>, Robin Gong <b38343@...escale.com>,
Enric Balletbo i Serra <eballetbo@...il.com>
Subject: Re: [PATCH v4 3/6] regulator: pf1550: add support for regulator
On Tue, Jun 03, 2025 at 02:27:47PM -0400, Samuel Kayode via B4 Relay wrote:
> +static int pf1550_set_ramp_delay(struct regulator_dev *rdev, int ramp_delay)
> +{
> + int id = rdev_get_id(rdev);
> + unsigned int ramp_bits = 0;
> + int ret;
> +
> + if (id > PF1550_VREFDDR)
> + return -EACCES;
> +
> + if (ramp_delay > 0) {
> + ramp_delay = 6250 / ramp_delay;
> + ramp_bits = ramp_delay >> 1;
> + }
I'm not seeing validation of the maximum ramp_delay value here?
> + switch (irq_type) {
> + case PF1550_PMIC_IRQ_SW1_LS:
> + event = REGULATOR_EVENT_OVER_CURRENT;
> + case PF1550_PMIC_IRQ_SW1_HS:
> + event = REGULATOR_EVENT_OVER_CURRENT;
> + case PF1550_PMIC_IRQ_LDO1_FAULT:
> + event = REGULATOR_EVENT_OVER_CURRENT;
You appear to be flagging all these events as over current events which
doesn't seem entirely plausible.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists