In preparation for future support of PSE budget evaluation strategy and
power management, we need the power budget value of the power supply.

This addition allows the regulator to track the available power
budget, which will be essential for prioritizing ports when
making power allocation decisions.

The related budget evaluation strategy patch series sent:
https://lore.kernel.org/netdev/20250104161622.7b82dfdf@kmaincent-XPS-13-7390/T/#t

Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
---
Changes in v2:
- Add event notifier in case of power request over budget.
- Track how much budget is used instead of free power budget.
- Link to v1: https://lore.kernel.org/r/20250113-feature_regulator_pw_budget-v1-0-01e1d95c2015@bootlin.com

---
Kory Maincent (2):
      regulator: Add support for power budget
      regulator: dt-bindings: Add regulator-power-budget-milliwatt property

 .../devicetree/bindings/regulator/regulator.yaml   |   3 +
 drivers/regulator/core.c                           | 114 +++++++++++++++++++++
 drivers/regulator/of_regulator.c                   |   3 +
 include/linux/regulator/consumer.h                 |  21 ++++
 include/linux/regulator/driver.h                   |   2 +
 include/linux/regulator/machine.h                  |   2 +
 6 files changed, 145 insertions(+)
---
base-commit: 36d9fc502ebc4dd56ea95de1e4f10a4ac5c1691c
change-id: 20250110-feature_regulator_pw_budget-f0e7396afa05

Best regards,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

On Wed, 15 Jan 2025 15:41:56 +0100, Kory Maincent wrote:
> In preparation for future support of PSE budget evaluation strategy and
> power management, we need the power budget value of the power supply.
> 
> This addition allows the regulator to track the available power
> budget, which will be essential for prioritizing ports when
> making power allocation decisions.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/2] regulator: Add support for power budget
      commit: 42d7c87b4e1251f36eceac987e74623e7cda8577
[2/2] regulator: dt-bindings: Add regulator-power-budget-milliwatt property
      commit: 367a8200a91025289f9664e468fbc2b67c95e70e

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark

On Wed, 15 Jan 2025 15:41:56 +0100
Kory Maincent <kory.maincent@bootlin.com> wrote:

> In preparation for future support of PSE budget evaluation strategy and
> power management, we need the power budget value of the power supply.
> 
> This addition allows the regulator to track the available power
> budget, which will be essential for prioritizing ports when
> making power allocation decisions.
> 
> The related budget evaluation strategy patch series sent:
> https://lore.kernel.org/netdev/20250104161622.7b82dfdf@kmaincent-XPS-13-7390/T/#t

Hello,

Is there hope this will be merged before the merge window?

Regards,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

On Fri, Jan 17, 2025 at 01:09:36PM +0100, Kory Maincent wrote:
> On Wed, 15 Jan 2025 15:41:56 +0100

> > In preparation for future support of PSE budget evaluation strategy and
> > power management, we need the power budget value of the power supply.

> Is there hope this will be merged before the merge window?

Please don't send content free pings and please allow a reasonable time
for review.  People get busy, go on holiday, attend conferences and so 
on so unless there is some reason for urgency (like critical bug fixes)
please allow at least a couple of weeks for review.  If there have been
review comments then people may be waiting for those to be addressed.

Sending content free pings adds to the mail volume (if they are seen at
all) which is often the problem and since they can't be reviewed
directly if something has gone wrong you'll have to resend the patches
anyway, so sending again is generally a better approach though there are
some other maintainers who like them - if in doubt look at how patches
for the subsystem are normally handled.

On Fri, 17 Jan 2025 13:48:54 +0000
Mark Brown <broonie@kernel.org> wrote:

> On Fri, Jan 17, 2025 at 01:09:36PM +0100, Kory Maincent wrote:
> > On Wed, 15 Jan 2025 15:41:56 +0100  
> 
> > > In preparation for future support of PSE budget evaluation strategy and
> > > power management, we need the power budget value of the power supply.  
> 
> > Is there hope this will be merged before the merge window?  
> 
> Please don't send content free pings and please allow a reasonable time
> for review.  People get busy, go on holiday, attend conferences and so 
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review.  If there have been
> review comments then people may be waiting for those to be addressed.
> 
> Sending content free pings adds to the mail volume (if they are seen at
> all) which is often the problem and since they can't be reviewed
> directly if something has gone wrong you'll have to resend the patches
> anyway, so sending again is generally a better approach though there are
> some other maintainers who like them - if in doubt look at how patches
> for the subsystem are normally handled.

Ok, dully noted! Sorry for the noise!

Regards,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com