From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Svyatoslav Ryhel <clamor95@gmail.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Alessandro Zummo <a.zummo@towertech.it>,
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 09:49:53 +0100 [thread overview]
Message-ID: <df35ed19-74d3-5eea-8efb-588417a417f2@linaro.org> (raw)
In-Reply-To: <CAPVz0n2XErDOCERV+XO3ek4_15hiwTasy4agLZLijqx2z67UnA@mail.gmail.com>
On 08/03/2023 09:46, Svyatoslav Ryhel wrote:
> ср, 8 бер. 2023 р. о 10:44 Alexandre Belloni
> <alexandre.belloni@bootlin.com> пише:
>>
>> Hello,
>>
>> the subject is not correct, please use the subsystem style
>>
>> On 08/03/2023 10:37:59+0200, Svyatoslav Ryhel wrote:
>>> MAX77663 PMIC can have RTC on both 0x63 i2c address (like grouper)
>>> which is main address but on some devices RTC is located on 0x48
>>> i2c address (like p880 and p895 from LG). Lets add property to be
>>> able to use alternative address if needed without breaking existing
>>> bindings.
>>>
>>> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
>>> ---
>>> drivers/rtc/rtc-max77686.c | 8 +++++++-
>>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/rtc/rtc-max77686.c b/drivers/rtc/rtc-max77686.c
>>> index b0250d91fb00..218177375531 100644
>>> --- a/drivers/rtc/rtc-max77686.c
>>> +++ b/drivers/rtc/rtc-max77686.c
>>> @@ -691,6 +691,7 @@ static int max77686_init_rtc_regmap(struct max77686_rtc_info *info)
>>> {
>>> struct device *parent = info->dev->parent;
>>> struct i2c_client *parent_i2c = to_i2c_client(parent);
>>> + int rtc_i2c_addr;
>>> int ret;
>>>
>>> if (info->drv_data->rtc_irq_from_platform) {
>>> @@ -714,8 +715,13 @@ static int max77686_init_rtc_regmap(struct max77686_rtc_info *info)
>>> goto add_rtc_irq;
>>> }
>>>
>>> + ret = device_property_read_u32(parent, "maxim,rtc-i2c-address",
>>> + &rtc_i2c_addr);
>>
>> This property needs to be documented
>>
>
> max776xx pmic has no yaml to document
Of course it has, otherwise on what did I work?
git grep max77686
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-08 8:50 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 [this message]
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
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=df35ed19-74d3-5eea-8efb-588417a417f2@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