From: Harry Austen <hpausten@protonmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Michal Simek <michal.simek@amd.com>,
Shubhrajyoti Datta <shubhrajyoti.datta@amd.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/7] dt-bindings: clock: xilinx: add description of user monitor interrupt
Date: Sat, 20 Jul 2024 20:00:45 +0000 [thread overview]
Message-ID: <D2UMTF78IDUQ.IWXPEKIF0MAU@protonmail.com> (raw)
In-Reply-To: <20240720143708.GA239850-robh@kernel.org>
On Sat Jul 20, 2024 at 3:37 PM BST, Rob Herring wrote:
> On Sat, Jul 20, 2024 at 12:01:48PM +0000, Harry Austen wrote:
> > This Xilinx clocking wizard IP core outputs this interrupt signal to
> > indicate when one of the four optional user clock inputs is either
> > stopped, overruns, underruns or glitches.
> >
> > This functionality was only added from version 6.0 onwards, so restrict
> > it to particular compatible strings.
> >
> > Signed-off-by: Harry Austen <hpausten@protonmail.com>
> > ---
> > .../bindings/clock/xlnx,clocking-wizard.yaml | 22 ++++++++++++++++++-
> > 1 file changed, 21 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/clock/xlnx,clocking-wizard.yaml b/Documentation/devicetree/bindings/clock/xlnx,clocking-wizard.yaml
> > index 9d5324dc1027a..4609bb56b06b5 100644
> > --- a/Documentation/devicetree/bindings/clock/xlnx,clocking-wizard.yaml
> > +++ b/Documentation/devicetree/bindings/clock/xlnx,clocking-wizard.yaml
> > @@ -62,17 +62,37 @@ required:
> > - xlnx,speed-grade
> > - xlnx,nr-outputs
> >
> > +allOf:
> > + - if:
> > + properties:
> > + compatible:
> > + enum:
> > + - xlnx,clocking-wizard-v6.0
> > + - xlnx,versal-clk-wizard
> > + then:
> > + properties:
> > + interrupts:
> > + items:
> > + - description: user clock monitor interrupt
> > +
> > + interrupt-names:
> > + items:
> > + - const: monitor
>
> Properties need to be defined at the top-level (outside the if/then
> schema), then restricted here.
Makes sense. Will do in v2.
Thanks for the review!
>
> > +
> > additionalProperties: false
> >
> > examples:
> > - |
> > + #include <dt-bindings/interrupt-controller/irq.h>
> > clock-controller@b0000000 {
> > - compatible = "xlnx,clocking-wizard";
> > + compatible = "xlnx,clocking-wizard-v6.0";
> > reg = <0xb0000000 0x10000>;
> > #clock-cells = <1>;
> > xlnx,speed-grade = <1>;
> > xlnx,nr-outputs = <6>;
> > clock-names = "clk_in1", "s_axi_aclk";
> > clocks = <&clkc 15>, <&clkc 15>;
> > + interrupts-extended = <&intc 52 IRQ_TYPE_EDGE_RISING>;
> > + interrupt-names = "monitor";
> > };
> > ...
> > --
> > 2.45.2
> >
> >
next prev parent reply other threads:[~2024-07-20 21:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 12:01 [PATCH 0/7] clk: clocking-wizard: add user clock monitor support Harry Austen
2024-07-20 12:01 ` [PATCH 1/7] clk: clocking-wizard: simplify probe/remove with devres helpers Harry Austen
2024-07-23 23:07 ` Stephen Boyd
2024-07-20 12:01 ` [PATCH 2/7] clk: clocking-wizard: use newer clk_hw API Harry Austen
2024-07-23 23:14 ` Stephen Boyd
2024-07-25 17:57 ` Harry Austen
2024-07-20 12:01 ` [PATCH 3/7] clk: clocking-wizard: move clock registration to separate function Harry Austen
2024-07-20 12:01 ` [PATCH 4/7] dt-bindings: clock: xilinx: add description of user monitor interrupt Harry Austen
2024-07-20 14:30 ` Rob Herring (Arm)
2024-07-20 14:37 ` Rob Herring
2024-07-20 20:00 ` Harry Austen [this message]
2024-07-20 12:01 ` [PATCH 5/7] clk: clocking-wizard: add user clock monitor support Harry Austen
2024-07-23 23:29 ` Stephen Boyd
2024-07-25 18:05 ` Harry Austen
2024-07-20 12:01 ` [PATCH 6/7] dt-bindings: clock: xilinx: describe whether dynamic reconfig is enabled Harry Austen
2024-07-22 17:13 ` Conor Dooley
2024-07-25 17:53 ` Harry Austen
2024-07-20 12:02 ` [PATCH 7/7] clk: clocking-wizard: move dynamic reconfig setup behind flag Harry Austen
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=D2UMTF78IDUQ.IWXPEKIF0MAU@protonmail.com \
--to=hpausten@protonmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=shubhrajyoti.datta@amd.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;
as well as URLs for NNTP newsgroup(s).