From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: broonie@kernel.org
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
lgirdwood@gmail.com, s.nawrocki@samsung.com
Subject: [PATCH RESEND 0/2] Arizona Clocking Improvements
Date: Fri, 21 Oct 2016 14:15:56 +0100 [thread overview]
Message-ID: <1477055758-11490-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)
Add support for requesting the input clocks for the CODEC through
the clock framework. This is some what of an intermediate step
until all the clocking itself in the CODEC can be brought under
the clock framework but as there are machine drivers that want
to be merged now with source clocks that require gating and
difficult to resolve issues between the SPI and clock framework
an intermediate solution seems warranted.
The first patch in the original sending of this series is now in
mainline through the MFD tree so these just need to go through
ASoC now.
Thanks,
Charles
Charles Keepax (2):
ASoC: arizona: Add gating for clock when used for direct MCLK
ASoC: arizona: Add gating for source clocks of the FLLs
sound/soc/codecs/arizona.c | 100 ++++++++++++++++++++++++++++++++++++++++++---
sound/soc/codecs/arizona.h | 2 +
sound/soc/codecs/cs47l24.c | 6 ++-
sound/soc/codecs/wm5102.c | 9 +++-
sound/soc/codecs/wm5110.c | 10 +++--
sound/soc/codecs/wm8997.c | 9 +++-
sound/soc/codecs/wm8998.c | 6 ++-
7 files changed, 125 insertions(+), 17 deletions(-)
--
2.1.4
next reply other threads:[~2016-10-21 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 13:15 Charles Keepax [this message]
2016-10-21 13:15 ` [PATCH RESEND 1/2] ASoC: arizona: Add gating for clock when used for direct MCLK Charles Keepax
2016-10-21 13:15 ` [PATCH RESEND 2/2] ASoC: arizona: Add gating for source clocks of the FLLs Charles Keepax
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=1477055758-11490-1-git-send-email-ckeepax@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=s.nawrocki@samsung.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).