Commit 675d0e3c authored by Kory Maincent's avatar Kory Maincent Committed by Paolo Abeni
Browse files

net: pse-pd: Avoid setting max_uA in regulator constraints 



Setting the max_uA constraint in the regulator API imposes a current
limit during the regulator registration process. This behavior conflicts
with preserving the maximum PI power budget configuration across reboots.

Instead, compare the desired current limit to MAX_PI_CURRENT in the
pse_pi_set_current_limit() function to ensure proper handling of the
power budget.

Acked-by: default avatarOleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: default avatarKory Maincent <kory.maincent@bootlin.com>
Signed-off-by: default avatarPaolo Abeni <pabeni@redhat.com>
parent 514dcf78

drivers/net/pse-pd/pse_core.c

+4 −3
Original line number Diff line number Diff line
@@ -357,6 +357,9 @@ static int pse_pi_set_current_limit(struct regulator_dev *rdev, int min_uA, 
	if (!ops->pi_set_current_limit)

		return -EOPNOTSUPP;



	if (max_uA > MAX_PI_CURRENT)

		return -ERANGE;



	id = rdev_get_id(rdev);

	mutex_lock(&pcdev->lock);

	ret = ops->pi_set_current_limit(pcdev, id, max_uA);
@@ -403,11 +406,9 @@ devm_pse_pi_regulator_register(struct pse_controller_dev *pcdev, 


	rinit_data->constraints.valid_ops_mask = REGULATOR_CHANGE_STATUS;



	if (pcdev->ops->pi_set_current_limit) {

	if (pcdev->ops->pi_set_current_limit)

		rinit_data->constraints.valid_ops_mask |=

			REGULATOR_CHANGE_CURRENT;

		rinit_data->constraints.max_uA = MAX_PI_CURRENT;

	}



	rinit_data->supply_regulator = "vpwr";