From: Mark Brown <broonie@kernel.org>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
alsa-devel <alsa-devel@alsa-project.org>,
Stephen Boyd <sboyd@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jyri Sarha <jsarha@ti.com>, Liam Girdwood <lgirdwood@gmail.com>,
"Kristo, Tero" <t-kristo@ti.com>,
linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>
Subject: Re: [alsa-devel] [PATCH 4/4] ASoC: simple-card: Support for selecting system clocks by ID
Date: Mon, 22 Feb 2016 12:21:08 +0900 [thread overview]
Message-ID: <20160222032108.GU18327@sirena.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.02.1602171516260.10339@lnxricardw1.se.axis.com>
[-- Attachment #1: Type: text/plain, Size: 254 bytes --]
On Wed, Feb 17, 2016 at 03:18:57PM +0100, Ricard Wanderlof wrote:
> It makes sense to use an already existing clock framework, but I'm
> wondering, how do we model the clock select function? Using a clock mux?
Yes, that looks like a mux to me.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-02-22 3:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1455545495-20292-1-git-send-email-peter.ujfalusi@ti.com>
[not found] ` <1455545495-20292-5-git-send-email-peter.ujfalusi@ti.com>
[not found] ` <20160215152635.GN18988@sirena.org.uk>
2016-02-16 9:46 ` Peter Ujfalusi
2016-02-16 13:42 ` Mark Brown
2016-02-16 19:13 ` Michael Turquette
2016-02-17 8:13 ` Peter Ujfalusi
2016-02-17 12:07 ` Mark Brown
2016-02-17 19:52 ` Peter Ujfalusi
2016-04-18 15:50 ` [alsa-devel] " Peter Ujfalusi
2016-04-18 16:29 ` Mark Brown
2016-04-21 22:29 ` Stephen Boyd
2016-04-22 11:52 ` Peter Ujfalusi
2016-04-22 12:08 ` Tero Kristo
2016-02-17 11:31 ` Mark Brown
2016-02-17 14:18 ` [alsa-devel] " Ricard Wanderlof
2016-02-22 3:21 ` Mark Brown [this message]
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=20160222032108.GU18327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jsarha@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peter.ujfalusi@ti.com \
--cc=ricard.wanderlof@axis.com \
--cc=sboyd@codeaurora.org \
--cc=t-kristo@ti.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
all inboxes | Powered by JetHome®