From: "tip-bot2 for Frank Li" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Frank Li <Frank.Li@nxp.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: timers/clocksource] dt-bindings: timer: fsl,ftm-timer: use items for reg
Date: Wed, 23 Jul 2025 07:17:33 -0000 [thread overview]
Message-ID: <175325505307.1420.3943140957454469329.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20250523141437.533643-1-Frank.Li@nxp.com>
The following commit has been merged into the timers/clocksource branch of tip:
Commit-ID: 4532c1172869819d5b7e63d7ad12cf3f3e5f3946
Gitweb: https://git.kernel.org/tip/4532c1172869819d5b7e63d7ad12cf3f3e5f3946
Author: Frank Li <Frank.Li@nxp.com>
AuthorDate: Fri, 23 May 2025 10:14:37 -04:00
Committer: Daniel Lezcano <daniel.lezcano@linaro.org>
CommitterDate: Mon, 14 Jul 2025 18:14:42 +02:00
dt-bindings: timer: fsl,ftm-timer: use items for reg
The original txt binding doc is:
reg : Specifies base physical address and size of the register sets for
the clock event device and clock source device.
And existed dts provide two reg MMIO spaces. So change to use items to
descript reg property.
Update examples.
Fixes: 8fc30d8f8e86 ("dt-bindings: timer: fsl,ftm-timer: Convert to dtschema")
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Frank Li <Frank.Li@nxp.com>
Link: https://lore.kernel.org/r/20250523141437.533643-1-Frank.Li@nxp.com
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
---
Documentation/devicetree/bindings/timer/fsl,ftm-timer.yaml | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/timer/fsl,ftm-timer.yaml b/Documentation/devicetree/bindings/timer/fsl,ftm-timer.yaml
index 0e4a8dd..e3b61b6 100644
--- a/Documentation/devicetree/bindings/timer/fsl,ftm-timer.yaml
+++ b/Documentation/devicetree/bindings/timer/fsl,ftm-timer.yaml
@@ -14,7 +14,9 @@ properties:
const: fsl,ftm-timer
reg:
- maxItems: 1
+ items:
+ - description: clock event device
+ - description: clock source device
interrupts:
maxItems: 1
@@ -50,7 +52,8 @@ examples:
ftm@400b8000 {
compatible = "fsl,ftm-timer";
- reg = <0x400b8000 0x1000>;
+ reg = <0x400b8000 0x1000>,
+ <0x400b9000 0x1000>;
interrupts = <0 44 IRQ_TYPE_LEVEL_HIGH>;
clock-names = "ftm-evt", "ftm-src", "ftm-evt-counter-en", "ftm-src-counter-en";
clocks = <&clks VF610_CLK_FTM2>, <&clks VF610_CLK_FTM3>,
next prev parent reply other threads:[~2025-07-23 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 14:14 [PATCH v2 1/1] " Frank Li
2025-07-14 15:24 ` Frank Li
2025-07-14 16:04 ` Krzysztof Kozlowski
2025-07-14 16:12 ` Daniel Lezcano
2025-07-14 16:15 ` Daniel Lezcano
2025-07-23 7:17 ` tip-bot2 for Frank Li [this message]
2025-07-25 10:31 ` [tip: timers/clocksource] dt-bindings: timer: fsl,ftm-timer: Use 'items' for 'reg' tip-bot2 for Frank Li
2025-09-25 21:33 [tip: timers/clocksource] dt-bindings: timer: fsl,ftm-timer: use items for reg tip-bot2 for Frank Li
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=175325505307.1420.3943140957454469329.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=Frank.Li@nxp.com \
--cc=daniel.lezcano@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®