From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org
Subject: Re: [PATCH v1] max77663-rtc: pass rtc address from device tree node if exists
Date: Wed, 8 Mar 2023 11:46:49 +0100 [thread overview]
Message-ID: <c686f36d-995b-394d-1745-f59e5ebdb1b2@linaro.org> (raw)
In-Reply-To: <CAPVz0n37tyi0ErjGJFGUviX0p4+ZuxHm=4K16FnfDoUztbtXTA@mail.gmail.com>
On 08/03/2023 10:29, Svyatoslav Ryhel wrote:
> ср, 8 бер. 2023 р. о 11:11 Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> пише:
>>
>> On 08/03/2023 09:58, Svyatoslav Ryhel wrote:
>>> I would love to, but max77663 uses max77686 rtc
>>> https://github.com/torvalds/linux/blob/master/drivers/mfd/max77620.c#L123
>>> how to handle this?
>>
>> Don't top post.
>>
>> Hm, so it seems max7763 is already documented via max77620. I missed
>> that. Add the new property to max77620, not to max77686 RTC. It does not
>> look like RTC's property, but the PMIC's.
>
> There is no max77620 yaml, only txt. Add property to txt?
If property was to accept, then unfortunately no, you need to convert first.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-03-08 10:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 8:37 [PATCH v1] max77663-rtc: pass rtc address from device tree node if exists Svyatoslav Ryhel
2023-03-08 8:44 ` Alexandre Belloni
2023-03-08 8:46 ` Svyatoslav Ryhel
2023-03-08 8:49 ` Krzysztof Kozlowski
2023-03-08 8:51 ` Svyatoslav Ryhel
2023-03-08 8:55 ` Krzysztof Kozlowski
2023-03-08 8:54 ` Krzysztof Kozlowski
2023-03-08 8:58 ` Svyatoslav Ryhel
2023-03-08 9:11 ` Krzysztof Kozlowski
2023-03-08 9:14 ` Krzysztof Kozlowski
2023-03-08 9:42 ` Alexandre Belloni
2023-03-08 10:49 ` Krzysztof Kozlowski
2023-03-08 9:29 ` Svyatoslav Ryhel
2023-03-08 10:46 ` Krzysztof Kozlowski [this message]
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=c686f36d-995b-394d-1745-f59e5ebdb1b2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=clamor95@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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