From: John Keeping <john@metanate.com>
To: linux-kernel@vger.kernel.org
Cc: John Keeping <john@metanate.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH 1/2] clk: rockchip: add I2S internal clock IDs for rk3288
Date: Wed, 7 Sep 2016 17:53:29 +0100 [thread overview]
Message-ID: <20160907165330.14607-1-john@metanate.com> (raw)
To minimize jitter on the I2S clocks, it is important that the
denominator in the fractional divider is much greater than the
numerator. Add identifiers for these internal clocks so that the
specific clock topology and rates can be specified in the device tree.
Signed-off-by: John Keeping <john@metanate.com>
---
include/dt-bindings/clock/rk3288-cru.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/dt-bindings/clock/rk3288-cru.h b/include/dt-bindings/clock/rk3288-cru.h
index 9a586e2d9c91..9526653383d9 100644
--- a/include/dt-bindings/clock/rk3288-cru.h
+++ b/include/dt-bindings/clock/rk3288-cru.h
@@ -88,6 +88,9 @@
#define SCLK_PVTM_GPU 124
#define SCLK_CRYPTO 125
#define SCLK_MIPIDSI_24M 126
+#define SCLK_I2S_PRE 127
+#define SCLK_I2S_SRC 128
+#define SCLK_I2S_FRAC 129
#define SCLK_MAC 151
#define SCLK_MACREF_OUT 152
--
2.9.3.728.g30b24b4.dirty
next reply other threads:[~2016-09-07 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 16:53 John Keeping [this message]
2016-09-07 16:53 ` [PATCH 2/2] clk: rockchip: use identifiers for rk3288 I2S clocks John Keeping
[not found] ` <20160907165330.14607-1-john-HooS5bfzL4hWk0Htik3J/w@public.gmane.org>
2016-09-07 17:58 ` [PATCH 1/2] clk: rockchip: add I2S internal clock IDs for rk3288 Heiko Stuebner
2016-09-07 18:18 ` John Keeping
2016-09-25 21:50 ` Heiko Stuebner
2016-09-26 17:04 ` John Keeping
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=20160907165330.14607-1-john@metanate.com \
--to=john@metanate.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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).