From: Michal Simek <michal.simek@amd.com>
To: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
Sebastian Reichel <sre@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: git@amd.com
Subject: Re: [PATCH] dt-bindings: power: reset: xilinx: Make "interrupts" property optional
Date: Mon, 17 Feb 2025 12:09:06 +0100 [thread overview]
Message-ID: <01b80c04-1d64-4850-bd75-bcf73d42dd67@amd.com> (raw)
In-Reply-To: <20250217095226.12606-1-shubhrajyoti.datta@amd.com>
On 2/17/25 10:52, Shubhrajyoti Datta wrote:
> The "interrupts" property in the ZynqMP power/reset binding was previously
> marked as required. However, there are multiple mechanisms for
> handling power/reset events, including:
> -Event management registration,
> -Mailbox (mboxes),
> -Interrupts (interrupts).
>
> When event management support is available (default on Versal SoC), the
> "interrupts" property is not used hence not required.
>
> Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>
> ---
>
> .../devicetree/bindings/power/reset/xlnx,zynqmp-power.yaml | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/power/reset/xlnx,zynqmp-power.yaml b/Documentation/devicetree/bindings/power/reset/xlnx,zynqmp-power.yaml
> index 799831636194..079ad977b907 100644
> --- a/Documentation/devicetree/bindings/power/reset/xlnx,zynqmp-power.yaml
> +++ b/Documentation/devicetree/bindings/power/reset/xlnx,zynqmp-power.yaml
> @@ -46,7 +46,6 @@ properties:
>
> required:
> - compatible
> - - interrupts
>
> additionalProperties: false
>
Acked-by: Michal Simek <michal.simek@amd.com>
Thanks,
Michal
next prev parent reply other threads:[~2025-02-17 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 9:52 [PATCH] dt-bindings: power: reset: xilinx: Make "interrupts" property optional Shubhrajyoti Datta
2025-02-17 11:09 ` Michal Simek [this message]
2025-02-19 23:15 ` Rob Herring (Arm)
2025-02-20 11:16 ` Michal Simek
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=01b80c04-1d64-4850-bd75-bcf73d42dd67@amd.com \
--to=michal.simek@amd.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shubhrajyoti.datta@amd.com \
--cc=sre@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;
as well as URLs for NNTP newsgroup(s).