From: Matej Vasilevski <matej.vasilevski@seznam.cz>
To: Pavel Pisa <pisa@cmp.felk.cvut.cz>,
Ondrej Ille <ondrej.ille@gmail.com>,
Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org,
Matej Vasilevski <matej.vasilevski@seznam.cz>
Subject: [PATCH v4 1/3] dt-bindings: can: ctucanfd: add another clock for HW timestamping
Date: Thu, 15 Sep 2022 01:39:42 +0200 [thread overview]
Message-ID: <20220914233944.598298-2-matej.vasilevski@seznam.cz> (raw)
In-Reply-To: <20220914233944.598298-1-matej.vasilevski@seznam.cz>
Add second clock phandle to specify the timestamping clock.
Signed-off-by: Matej Vasilevski <matej.vasilevski@seznam.cz>
---
.../bindings/net/can/ctu,ctucanfd.yaml | 19 +++++++++++++++----
1 file changed, 15 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/can/ctu,ctucanfd.yaml b/Documentation/devicetree/bindings/net/can/ctu,ctucanfd.yaml
index 4635cb96fc64..432f0e3ed828 100644
--- a/Documentation/devicetree/bindings/net/can/ctu,ctucanfd.yaml
+++ b/Documentation/devicetree/bindings/net/can/ctu,ctucanfd.yaml
@@ -44,9 +44,19 @@ properties:
clocks:
description: |
- phandle of reference clock (100 MHz is appropriate
- for FPGA implementation on Zynq-7000 system).
- maxItems: 1
+ Phandle of reference clock (100 MHz is appropriate for FPGA
+ implementation on Zynq-7000 system). Optionally add a phandle to
+ the timestamping clock connected to timestamping counter, if used.
+ minItems: 1
+ items:
+ - description: core clock
+ - description: timestamping clock
+
+ clock-names:
+ minItems: 1
+ items:
+ - const: core-clk
+ - const: ts-clk
required:
- compatible
@@ -61,6 +71,7 @@ examples:
ctu_can_fd_0: can@43c30000 {
compatible = "ctu,ctucanfd";
interrupts = <0 30 4>;
- clocks = <&clkc 15>;
+ clocks = <&clkc 15>, <&clkc 16>;
+ clock-names = "core-clk", "ts-clk";
reg = <0x43c30000 0x10000>;
};
--
2.25.1
next prev parent reply other threads:[~2022-09-14 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 23:39 [PATCH v4 0/3] can: ctucanfd: hardware rx timestamps reporting Matej Vasilevski
2022-09-14 23:39 ` Matej Vasilevski [this message]
2022-09-16 19:30 ` [PATCH v4 1/3] dt-bindings: can: ctucanfd: add another clock for HW timestamping Rob Herring
2022-09-14 23:39 ` [PATCH v4 2/3] can: ctucanfd: add HW timestamps to RX and error CAN frames Matej Vasilevski
2022-09-15 10:50 ` Pavel Pisa
2022-09-18 22:00 ` Matej Vasilevski
2022-09-19 10:36 ` Marc Kleine-Budde
2022-09-28 20:40 ` Matej Vasilevski
2022-09-21 7:06 ` Marc Kleine-Budde
2022-09-14 23:39 ` [PATCH v4 3/3] doc: ctucanfd: RX frames timestamping for platform devices Matej Vasilevski
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=20220914233944.598298-2-matej.vasilevski@seznam.cz \
--to=matej.vasilevski@seznam.cz \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=ondrej.ille@gmail.com \
--cc=pabeni@redhat.com \
--cc=pisa@cmp.felk.cvut.cz \
--cc=robh+dt@kernel.org \
--cc=wg@grandegger.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).