[PATCH v5 0/2] rtc: max77686: convert to i2c_new_ancillary_device

Svyatoslav Ryhel posted 2 patches 1 day, 8 hours ago
.../pinctrl/maxim,max77620-pinctrl.yaml       |  98 ++++++++
.../bindings/pinctrl/pinctrl-max77620.txt     | 127 ----------
.../regulator/maxim,max77620-regulator.yaml   |  99 ++++++++
.../bindings/regulator/regulator-max77620.txt | 222 ------------------
4 files changed, 197 insertions(+), 349 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pinctrl/maxim,max77620-pinctrl.yaml
delete mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-max77620.txt
create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77620-regulator.yaml
delete mode 100644 Documentation/devicetree/bindings/regulator/regulator-max77620.txt
[PATCH v5 0/2] rtc: max77686: convert to i2c_new_ancillary_device
Posted by Svyatoslav Ryhel 1 day, 8 hours ago
Convert RTC I2C device creation from devm_i2c_new_dummy_device() to
i2c_new_ancillary_device() to enable the use of a device tree-specified
RTC address instead of a hardcoded value. If the device tree does not
provide an address, use hardcoded values as a fallback.

This addresses an issue with the MAX77663 PMIC, which can have the RTC at
different I2C positions (either 0x48, like the MAX77714, or 0x68, like
the MAX77620). The MAX77620 value is used as the default. The I2C position
of the MAX77663 is factory-set and cannot be detected from the chip
itself.

I have tested this patch on LG Optimus Vu P895 with max77663 PMIC and
non-default RTC position. RTC is registered correctly.

---
Changes in v5
- fixed pincontrol schema
- dropped applied patches

Changes in v4
- adjusted pinconfig node naming
- changed interrupt in the example
- fixed indentation in the example
- corrected pinconfig node name in the example
- commit "dt-bindings: gpio: trivial-gpio: remove max77620 compatible"
  squashed with the converting patch for this compatible

Changes in v3
- max77620 files converted to DT schema.

Changes in v2
- dropped patch that changes max77686 and adjusted max77620 where max77663
  is described.
---

Svyatoslav Ryhel (2):
  regulator: dt-bindings: regulator-max77620: convert to DT schema
  dt-bindings: pinctrl: pinctrl-max77620: convert to DT schema

 .../pinctrl/maxim,max77620-pinctrl.yaml       |  98 ++++++++
 .../bindings/pinctrl/pinctrl-max77620.txt     | 127 ----------
 .../regulator/maxim,max77620-regulator.yaml   |  99 ++++++++
 .../bindings/regulator/regulator-max77620.txt | 222 ------------------
 4 files changed, 197 insertions(+), 349 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/pinctrl/maxim,max77620-pinctrl.yaml
 delete mode 100644 Documentation/devicetree/bindings/pinctrl/pinctrl-max77620.txt
 create mode 100644 Documentation/devicetree/bindings/regulator/maxim,max77620-regulator.yaml
 delete mode 100644 Documentation/devicetree/bindings/regulator/regulator-max77620.txt

-- 
2.51.0
Re: (subset) [PATCH v5 0/2] rtc: max77686: convert to i2c_new_ancillary_device
Posted by Mark Brown 1 day, 3 hours ago
On Mon, 06 Apr 2026 10:51:12 +0300, Svyatoslav Ryhel wrote:
> rtc: max77686: convert to i2c_new_ancillary_device
> 
> Convert RTC I2C device creation from devm_i2c_new_dummy_device() to
> i2c_new_ancillary_device() to enable the use of a device tree-specified
> RTC address instead of a hardcoded value. If the device tree does not
> provide an address, use hardcoded values as a fallback.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: regulator-max77620: convert to DT schema
      https://git.kernel.org/broonie/regulator/c/881dd6b2ff82

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