From: Michal Simek <michal.simek@amd.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kernel@vger.kernel.org, monstr@monstr.eu,
michal.simek@xilinx.com, git@xilinx.com
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"moderated list:ARM/ZYNQ ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
<linux-rtc@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: rtc: zynqmp: Describe power-domains property
Date: Fri, 16 Feb 2024 10:42:29 +0100 [thread overview]
Message-ID: <ed59671f-6e0b-45a2-bae7-38f7b4b7e625@amd.com> (raw)
In-Reply-To: <5a81f16b-8ece-4263-b424-4dd6cd6e386f@linaro.org>
On 2/16/24 10:19, Krzysztof Kozlowski wrote:
> On 16/02/2024 09:51, Michal Simek wrote:
>> RTC has its own power domain on Xilinx Versal SOC that's why describe it as
>> optional property.
>>
>> Signed-off-by: Michal Simek <michal.simek@amd.com>
>> ---
>>
>> Documentation/devicetree/bindings/rtc/xlnx,zynqmp-rtc.yaml | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>
> But Versal is not described in this binding, is it? I see only one
> compatible.
It is the same IP only as is on zynqmp with own power rail.
Pretty much with different firmware interface on zynqmp you can describe it too
(and doesn't really matter if it is separated in HW or common for more IPs).
Thanks,
Michal
next prev parent reply other threads:[~2024-02-16 9:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 8:51 [PATCH] dt-bindings: rtc: zynqmp: Describe power-domains property Michal Simek
2024-02-16 9:19 ` Krzysztof Kozlowski
2024-02-16 9:42 ` Michal Simek [this message]
2024-02-17 8:26 ` Krzysztof Kozlowski
2024-02-19 13:11 ` Michal Simek
2024-02-19 13:19 ` Krzysztof Kozlowski
2024-02-19 13:21 ` Michal Simek
2024-02-19 20:19 ` Alexandre Belloni
2024-02-20 10:51 ` Buddhabhatti, Jay
2024-02-20 11:34 ` Michal Simek
2024-02-20 11:45 ` Buddhabhatti, Jay
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=ed59671f-6e0b-45a2-bae7-38f7b4b7e625@amd.com \
--to=michal.simek@amd.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--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