From: Krzysztof Kozlowski <krzk@kernel.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>,
Chanwoo Choi <cw00.choi@samsung.com>, Lee Jones <lee@kernel.org>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v1 1/2] dt-bindings: mfd: maxim,max77686: document optional RTC address
Date: Thu, 12 Feb 2026 12:27:12 +0100 [thread overview]
Message-ID: <794f643f-6b8e-4d9f-a76e-0124f9845d82@kernel.org> (raw)
In-Reply-To: <8E149750-19F1-4274-BD24-B13ED47D1D51@gmail.com>
On 12/02/2026 09:08, Svyatoslav Ryhel wrote:
>
>
> 12 лютого 2026 р. 09:26:33 GMT+02:00, Krzysztof Kozlowski <krzk@kernel.org> пише:
>> On 11/02/2026 19:49, Svyatoslav Ryhel wrote:
>>> Document an optional second I2C address for the PMIC's RTC device, to be
>>> used if the RTC is located at a non-default I2C address
>>
>> MAX77686 did not allow changing the I2C address and there are no other
>> devices in the bindings.
>>
>
> That is true, MAX77663 RTC does this, should I adjust Documentation/devicetree/bindings/mfd/max77620.txt instead?
I don't know which binding you should update instead, but I know that it
must not be max77686. Please update the binding for the device you are
actually changing, not some other devices.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-12 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 18:49 [PATCH v1 0/2] rtc: max77686: convert to i2c_new_ancillary_device Svyatoslav Ryhel
2026-02-11 18:49 ` [PATCH v1 1/2] dt-bindings: mfd: maxim,max77686: document optional RTC address Svyatoslav Ryhel
2026-02-12 7:26 ` Krzysztof Kozlowski
2026-02-12 8:08 ` Svyatoslav Ryhel
2026-02-12 11:27 ` Krzysztof Kozlowski [this message]
2026-02-11 18:49 ` [PATCH v1 2/2] rtc: max77686: convert to i2c_new_ancillary_device Svyatoslav Ryhel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=794f643f-6b8e-4d9f-a76e-0124f9845d82@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox