From: Shawn Guo <shawnguo@kernel.org>
To: Stephen Boyd <sboyd@codeaurora.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: Jun Nie <jun.nie@linaro.org>, Baoyou Xie <xie.baoyou@zte.com.cn>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawnguo@kernel.org>, Shawn Guo <shawn.guo@linaro.org>
Subject: [PATCH v2 0/3] Add audio clocks support for ZTE ZX296718
Date: Fri, 16 Dec 2016 15:26:44 +0800 [thread overview]
Message-ID: <1481873207-22929-1-git-send-email-shawnguo@kernel.org> (raw)
From: Shawn Guo <shawn.guo@linaro.org>
It adds missing audio related clocks for ZTE SoC ZX296718. With these
clocks added, we can get HDMI audio work through SPDIF interface.
Changes for v2:
- Add a patch to clean up existing driver code.
- Clean up unused divider configuration lookup table.
- Use uintptr_t instead of u64 to cast 'reg_base' for summation.
- Instead of panic, give an error message and return error code when
of_clk_add_hw_provider() call fails.
- Drop unnecessary ulong type cast.
- Use pr_debug instead of pr_info to avoid noisy messages
Jun Nie (1):
clk: zte: add audio clocks for zx296718
Shawn Guo (2):
clk: zx296718: do not panic on failure
dt-bindings: zx296718-clk: add compatible for audio clock controller
.../devicetree/bindings/clock/zx296718-clk.txt | 3 +
drivers/clk/zte/clk-zx296718.c | 154 +++++++++++++++++++--
drivers/clk/zte/clk.c | 127 +++++++++++++++++
drivers/clk/zte/clk.h | 21 +++
4 files changed, 296 insertions(+), 9 deletions(-)
--
1.9.1
next reply other threads:[~2016-12-16 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 7:26 Shawn Guo [this message]
2016-12-16 7:26 ` [PATCH v2 1/3] clk: zx296718: do not panic on failure Shawn Guo
2016-12-21 23:33 ` Stephen Boyd
2016-12-16 7:26 ` [PATCH v2 2/3] dt-bindings: zx296718-clk: add compatible for audio clock controller Shawn Guo
2016-12-21 23:34 ` Stephen Boyd
2016-12-16 7:26 ` [PATCH v2 3/3] clk: zte: add audio clocks for zx296718 Shawn Guo
2016-12-21 23:34 ` Stephen Boyd
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=1481873207-22929-1-git-send-email-shawnguo@kernel.org \
--to=shawnguo@kernel.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=shawn.guo@linaro.org \
--cc=xie.baoyou@zte.com.cn \
/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