[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <170982370249.2592194.17824798576485392440.robh@kernel.org>
Date: Thu, 7 Mar 2024 09:01:43 -0600
From: Rob Herring <robh@...nel.org>
To: Michal Simek <michal.simek@....com>
Cc: "open list:REAL TIME CLOCK (RTC) SUBSYSTEM" <linux-rtc@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>, git@...inx.com, monstr@...str.eu,
linux-kernel@...r.kernel.org, Conor Dooley <conor+dt@...nel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" <devicetree@...r.kernel.org>,
michal.simek@...inx.com,
"moderated list:ARM/ZYNQ ARCHITECTURE" <linux-arm-kernel@...ts.infradead.org>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Subject: Re: [PATCH v3] dt-bindings: rtc: zynqmp: Add support for
Versal/Versal NET SoCs
On Thu, 07 Mar 2024 10:43:46 +0100, Michal Simek wrote:
> Add support for Versal and Versal NET SoCs. Both of them should use the
> same IP core but differences can be in integration part that's why create
> separate compatible strings.
>
> Also describe optional power-domains property. It is optional because power
> domain doesn't need to be onwed by non secure firmware hence no access to
> control it via any driver.
>
> Signed-off-by: Michal Simek <michal.simek@....com>
> ---
>
> Changes in v3:
> - make versal/versal-net fallback to zynqmp
>
> Changes in v2:
> - Change subject
> - Add compatible string for versal and versal NET
> - Update commit message to reflect why power domain is optional.
>
> .../devicetree/bindings/rtc/xlnx,zynqmp-rtc.yaml | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
Reviewed-by: Rob Herring <robh@...nel.org>
Powered by blists - more mailing lists