From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: liam.r.girdwood@linux.intel.com, tiwai@suse.de,
alsa-devel@alsa-project.org,
"Dharageswari.R" <dharageswari.r@intel.com>,
patches.audio@intel.com
Subject: Re: [PATCH 4/7] ASoC: Intel: Skylake: Add MCLK configuration
Date: Tue, 9 Feb 2016 08:15:27 +0530 [thread overview]
Message-ID: <20160209024526.GB19598@localhost> (raw)
In-Reply-To: <20160208164304.GH7265@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 681 bytes --]
On Mon, Feb 08, 2016 at 04:43:04PM +0000, Mark Brown wrote:
> On Fri, Feb 05, 2016 at 12:19:07PM +0530, Vinod Koul wrote:
> > From: "Dharageswari.R" <dharageswari.r@intel.com>
> >
> > The SoC has MCLK output which is typically required by codecs.
> > The MCLK is controlled by DSP FW, so driver can configure that by
> > sending DMA_CONTROL IPC. The configuration for MCLK is present
> > in the endpoint blob.
>
> For integration with CODEC drivers this clock should really be exposed
> via the clock API too.
Ideally yes.
I think then the our driver should register as a clock provider too. I will
check and see how we can get this done
Thanks
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-02-09 2:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 6:49 [PATCH 0/7] ASoC: Intel: Skylake: Topology sequence changes Vinod Koul
2016-02-05 6:49 ` [PATCH 1/7] ASoC: Intel: Skylake: Update the delay check Vinod Koul
2016-02-08 18:01 ` Applied "ASoC: Intel: Skylake: Update the delay check" to the asoc tree Mark Brown
2016-02-05 6:49 ` [PATCH 2/7] ASoC: Intel: Skylake: Get node id using helper Vinod Koul
2016-02-08 18:01 ` Applied "ASoC: Intel: Skylake: Get node id using helper" to the asoc tree Mark Brown
2016-02-05 6:49 ` [PATCH 3/7] ASoC: Intel: Skylake: Add skl_tplg_be_get_cpr_module() helper Vinod Koul
2016-02-08 18:01 ` Applied "ASoC: Intel: Skylake: Add skl_tplg_be_get_cpr_module() helper" to the asoc tree Mark Brown
2016-02-05 6:49 ` [PATCH 4/7] ASoC: Intel: Skylake: Add MCLK configuration Vinod Koul
2016-02-08 16:43 ` Mark Brown
2016-02-09 2:45 ` Vinod Koul [this message]
2016-02-08 18:01 ` Applied "ASoC: Intel: Skylake: Add MCLK configuration" to the asoc tree Mark Brown
2016-02-05 6:49 ` [PATCH 5/7] ASoC: Intel: Skylake: Allow module parameter set after bind Vinod Koul
2016-02-08 18:01 ` Applied "ASoC: Intel: Skylake: Allow module parameter set after bind" to the asoc tree Mark Brown
2016-02-05 6:49 ` [PATCH 6/7] ASoC: Intel: Skylake: Add shutdown callback Vinod Koul
2016-02-08 18:01 ` Applied "ASoC: Intel: Skylake: Add shutdown callback" to the asoc tree Mark Brown
2016-02-05 6:49 ` [PATCH 7/7] ASoC: Intel: Skylake: Fill BE blob with default params Vinod Koul
2016-02-08 18:01 ` Applied "ASoC: Intel: Skylake: Fill BE blob with default params" to the asoc tree Mark Brown
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=20160209024526.GB19598@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dharageswari.r@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=tiwai@suse.de \
/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).