From: Adam Ford <aford173@gmail.com>
To: linux-clk@vger.kernel.org
Cc: aford@beaconembedded.com, charles.stevens@logicpd.com,
Adam Ford <aford173@gmail.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Marek Vasut <marek.vasut@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] dt: Add bindings for IDT VersaClock 5P49V5925
Date: Sat, 4 Apr 2020 11:15:36 -0500 [thread overview]
Message-ID: <20200404161537.2312297-2-aford173@gmail.com> (raw)
In-Reply-To: <20200404161537.2312297-1-aford173@gmail.com>
IDT VersaClock 5 5P49V6965 has 5 clock outputs, 4 fractional dividers.
Signed-off-by: Adam Ford <aford173@gmail.com>
diff --git a/Documentation/devicetree/bindings/clock/idt,versaclock5.txt b/Documentation/devicetree/bindings/clock/idt,versaclock5.txt
index 05a245c9df08..bcff681a4bd0 100644
--- a/Documentation/devicetree/bindings/clock/idt,versaclock5.txt
+++ b/Documentation/devicetree/bindings/clock/idt,versaclock5.txt
@@ -12,6 +12,7 @@ Required properties:
"idt,5p49v5933"
"idt,5p49v5935"
"idt,5p49v6901"
+ "idt,5p49v6965"
- reg: i2c device address, shall be 0x68 or 0x6a.
- #clock-cells: from common clock binding; shall be set to 1.
- clocks: from common clock binding; list of parent clock handles,
--
2.25.1
next prev parent reply other threads:[~2020-04-04 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 16:15 [PATCH 1/2] clk: vc5: Add support for IDT VersaClock 5P49V6965 Adam Ford
2020-04-04 16:15 ` Adam Ford [this message]
2020-04-14 18:15 ` [PATCH 2/2] dt: Add bindings for IDT VersaClock 5P49V5925 Rob Herring
2020-05-29 4:05 ` Stephen Boyd
2020-05-02 10:53 ` [PATCH 1/2] clk: vc5: Add support for IDT VersaClock 5P49V6965 Adam Ford
2020-05-29 4:04 ` Stephen Boyd
-- strict thread matches above, loose matches on Subject: below --
2017-07-07 1:57 [PATCH 0/2] clk: vc5: Add IDT VersaClock 5P49V5925 Vladimir Barinov
2017-07-07 1:57 ` [PATCH 2/2] dt: Add bindings for " Vladimir Barinov
2017-07-09 13:31 ` Marek Vasut
2017-07-09 17:38 ` Vladimir Barinov
2017-07-09 17:42 ` Marek Vasut
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=20200404161537.2312297-2-aford173@gmail.com \
--to=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=charles.stevens@logicpd.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).