From: Marek Vasut <marex@denx.de>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: devicetree@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Alessandro Zummo <a.zummo@towertech.it>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-rtc@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: rtc: m41t80: Mark the clock: subnode as deprecated
Date: Fri, 16 Dec 2022 21:31:09 +0100 [thread overview]
Message-ID: <781e3e0f-bcfd-4165-d65a-08d4eb6ddeb7@denx.de> (raw)
In-Reply-To: <Y5ybrlxIH4zYpaWZ@mail.local>
On 12/16/22 17:24, Alexandre Belloni wrote:
> On 16/12/2022 16:05:48+0100, Sebastian Reichel wrote:
>>>> IIRC On i.MX6 referencing the I2C connected RTC results in boot
>>>> hanging forever when trying to get the ckil clock in
>>>> imx6q_clocks_init. At least it used to be the case when I was
>>>> working on this - I no longer have access to the boards. Of course
>>>> properly referencing the RTC clock was the first route I tried.
>>>
>>> Hmmmmm, what shall we do, un-deprecate the clock sub-node?
>>
>> Depends on the exact meaning of "deprecate: true". I think we all
>> agree, that it's better to avoid the sub-node and only use it when
>> it's really required. But having a deprecation warning for an
>> in-tree user without a clear path forward also seems to be annoying.
>> I think it makes sense for the DT binding maintainers (Rob/Krzysztof)
>> to comment on this.
>>
>
> I dropped the commit from the PR I'm going to send Linus later today
That works, thank you !
next prev parent reply other threads:[~2022-12-16 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 20:51 [PATCH v3 1/2] dt-bindings: rtc: m41t80: Convert text schema to YAML one Marek Vasut
2022-12-11 20:51 ` [PATCH v3 2/2] dt-bindings: rtc: m41t80: Mark the clock: subnode as deprecated Marek Vasut
2022-12-15 18:06 ` Sebastian Reichel
2022-12-15 19:39 ` Marek Vasut
2022-12-16 14:24 ` Sebastian Reichel
2022-12-16 14:36 ` Marek Vasut
2022-12-16 15:05 ` Sebastian Reichel
2022-12-16 16:24 ` Alexandre Belloni
2022-12-16 20:31 ` Marek Vasut [this message]
2022-12-12 8:57 ` [PATCH v3 1/2] dt-bindings: rtc: m41t80: Convert text schema to YAML one Krzysztof Kozlowski
2022-12-12 9:25 ` Alexandre Belloni
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=781e3e0f-bcfd-4165-d65a-08d4eb6ddeb7@denx.de \
--to=marex@denx.de \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-rtc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sebastian.reichel@collabora.com \
/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