From: Mark Brown <broonie@kernel.org>
To: Damien Horsley <Damien.Horsley@imgtec.com>
Cc: alsa-devel@alsa-project.org, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
James Hartley <james.hartley@imgtec.com>
Subject: Re: [RFC V2 1/2] ASoC: img: Add binding document for Pistachio audio card
Date: Fri, 29 Jan 2016 00:25:33 +0100 [thread overview]
Message-ID: <20160128232533.GG4130@sirena.org.uk> (raw)
In-Reply-To: <56AA2301.9070604@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
On Thu, Jan 28, 2016 at 02:17:37PM +0000, Damien Horsley wrote:
> The i2s out controller also uses i2s_mclk, and calls clk_set_rate in
> hw_params at present. Would creating a set_sysclk callback for the i2s
> out controller, then calling snd_soc_dai_set_sysclk on the cpu dai in
> addition to the codec dais in the card driver be the correct way to
> manage this?
That'd be more normal, yes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-01-28 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1453818867-16322-1-git-send-email-Damien.Horsley@imgtec.com>
[not found] ` <1453818867-16322-2-git-send-email-Damien.Horsley@imgtec.com>
2016-01-27 14:57 ` [RFC V2 1/2] ASoC: img: Add binding document for Pistachio audio card Mark Brown
2016-01-27 15:18 ` Damien Horsley
2016-01-27 16:00 ` Mark Brown
2016-01-27 17:13 ` Damien Horsley
2016-01-27 20:14 ` Mark Brown
2016-01-28 14:17 ` Damien Horsley
2016-01-28 23:25 ` 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=20160128232533.GG4130@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Damien.Horsley@imgtec.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=james.hartley@imgtec.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=tiwai@suse.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