[PATCH v3 0/4] regulator: dt-bindings: Tegra coupling DT conversions and cleanup

Bhargav Joshi posted 4 patches 6 days, 1 hour ago
There is a newer version of this series
.../devicetree/bindings/mfd/ti,tps65910.yaml       |  20 ++-
.../regulator/maxim,max77620-regulator.yaml        |   5 +-
.../regulator/nvidia,tegra-regulators-coupling.txt |  65 -------
.../nvidia,tegra-regulators-coupling.yaml          |  74 ++++++++
.../devicetree/bindings/regulator/ti,tps62360.yaml |   1 +
.../devicetree/bindings/regulator/ti,tps6586x.yaml | 196 +++++++++++++++++++++
.../devicetree/bindings/regulator/tps6586x.txt     | 135 --------------
7 files changed, 292 insertions(+), 204 deletions(-)
[PATCH v3 0/4] regulator: dt-bindings: Tegra coupling DT conversions and cleanup
Posted by Bhargav Joshi 6 days, 1 hour ago
This series adds a shared DT schema for Tegra regulator coupling, 
updates relevant PMICs to use it, and converts the TI TPS6586x 
bindings to DT schema.

Summary:
- Patch 1: Fixes existing TPS65910 validation warnings.
- Patch 2: Converts Tegra regulator coupling to DT schema.
- Patch 3: Updates Tegra-related PMICs to reference the new schema.
- Patch 4: Converts TI TPS6586x to DT schema.

Signed-off-by: Bhargav Joshi <j.bhargav.u@gmail.com>
---
Changes in v3:
- Patch 2: Add '>' to description
- Collect tags
- Link to v2: https://lore.kernel.org/r/20260916-ti-tps6586x-v2-0-f12cfdfb446c@gmail.com

Changes in v2:
- Add patch 1 to resolve warnings from TPS65910.
- Add patch 2 to convert nvidia,tegra-regulators-coupling to DT schema.
- Add patch 3 to $ref to shared schema.
- Patch 4: remove individual properties and add $ref to shared schema.
- Link to v1: https://lore.kernel.org/r/20260822-ti-tps6586x-v1-1-93cb46b32b27@gmail.com

---
Bhargav Joshi (4):
      dt-bindings: mfd: ti,tps65910: Add wakeup-source and GPIO hogs
      regulator: dt-bindings: nvidia,tegra-regulators-coupling: Convert to DT schema
      regulator: dt-bindings: Reference Tegra regulator coupling schema
      regulator: dt-bindings: ti,tps6586x: Convert to DT schema

 .../devicetree/bindings/mfd/ti,tps65910.yaml       |  20 ++-
 .../regulator/maxim,max77620-regulator.yaml        |   5 +-
 .../regulator/nvidia,tegra-regulators-coupling.txt |  65 -------
 .../nvidia,tegra-regulators-coupling.yaml          |  74 ++++++++
 .../devicetree/bindings/regulator/ti,tps62360.yaml |   1 +
 .../devicetree/bindings/regulator/ti,tps6586x.yaml | 196 +++++++++++++++++++++
 .../devicetree/bindings/regulator/tps6586x.txt     | 135 --------------
 7 files changed, 292 insertions(+), 204 deletions(-)
---
base-commit: 9f0346dcbea363787186c94ef94dd01aaa215afa
change-id: 20260821-ti-tps6586x-b54e7111917c

Best regards,
-- 
Bhargav
Re: (subset) [PATCH v3 0/4] regulator: dt-bindings: Tegra coupling DT conversions and cleanup
Posted by Mark Brown 1 day, 4 hours ago
On Sat, 19 Sep 2026 02:31:21 +0530, Bhargav Joshi wrote:
> regulator: dt-bindings: Tegra coupling DT conversions and cleanup
> 
> This series adds a shared DT schema for Tegra regulator coupling,
> updates relevant PMICs to use it, and converts the TI TPS6586x
> bindings to DT schema.
> 
> Summary:
> - Patch 1: Fixes existing TPS65910 validation warnings.
> - Patch 2: Converts Tegra regulator coupling to DT schema.
> - Patch 3: Updates Tegra-related PMICs to reference the new schema.
> - Patch 4: Converts TI TPS6586x to DT schema.
> 
> [...]

Applied to

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

Thanks!

[4/4] regulator: dt-bindings: ti,tps6586x: Convert to DT schema
      https://git.kernel.org/broonie/regulator/c/05a3330f490c

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