[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260211184941.6756-1-clamor95@gmail.com>
Date: Wed, 11 Feb 2026 20:49:39 +0200
From: Svyatoslav Ryhel <clamor95@...il.com>
To: Chanwoo Choi <cw00.choi@...sung.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
Lee Jones <lee@...nel.org>,
Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org,
linux-rtc@...r.kernel.org
Subject: [PATCH v1 0/2] 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.
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.
Svyatoslav Ryhel (2):
dt-bindings: mfd: maxim,max77686: document optional RTC address
rtc: max77686: convert to i2c_new_ancillary_device
.../devicetree/bindings/mfd/maxim,max77686.yaml | 15 +++++++++++++--
drivers/rtc/rtc-max77686.c | 14 ++++++++++++--
2 files changed, 25 insertions(+), 4 deletions(-)
--
2.51.0
Powered by blists - more mailing lists