From: Mark Brown <broonie@sirena.org.uk>
To: Joonyoung Shim <jy0922.shim@samsung.com>
Cc: alsa-devel@alsa-project.org, peter.ujfalusi@nokia.com,
kyungmin.park@samsung.com, bhmin@samsung.com
Subject: Re: [PATCH 1/1] ASoC: TWL4030: Add support Voice DAI
Date: Fri, 10 Apr 2009 11:22:41 +0100 [thread overview]
Message-ID: <20090410102240.GA6882@sirena.org.uk> (raw)
In-Reply-To: <49DEA8FE.8010700@samsung.com>
On Fri, Apr 10, 2009 at 11:03:42AM +0900, Joonyoung Shim wrote:
> On 4/9/2009 11:06 PM, Mark Brown wrote:
> >> + if (infreq != TWL4030_APLL_INFREQ_26000KHZ)
> >> + return -EPERM;
> > It's probably worth a comment here telling users that they'll need to
> > call set_sysclk() in their init() function rather than hw_params() -
> > otherwise this might get called before the clock is set up.
> It seems better that i remove startup function and add set_sysclk function,
> and inform supporting only 26MHz system master clock through comment.
> i think it is not important where set_sysclk() is called, the voice PCM
> interface needs just 26MHz system master clock.
It does feel right to have some sort of check for a valid sysclk so that
there's some software level documentation for the requirement since it's
easy to set up an ASoC driver without reading the datasheet for the part
so it's helpful if the driver can flag up broken configurations to them.
The reason for worrying about where set_sysclk() is called from is that
if you are going to have a check like that the user needs to call
set_sysclk() before the check is performed to ensure that the correct
configuration has been applied.
next prev parent reply other threads:[~2009-04-10 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 13:54 [PATCH 1/1] ASoC: TWL4030: Add support Voice DAI Joonyoung Shim
2009-04-09 14:06 ` Mark Brown
2009-04-10 2:03 ` Joonyoung Shim
2009-04-10 10:22 ` Mark Brown [this message]
2009-04-14 7:09 ` Peter Ujfalusi
2009-04-14 7:07 ` Peter Ujfalusi
2009-04-20 5:31 ` Joonyoung Shim
2009-04-20 6:35 ` Peter Ujfalusi
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=20090410102240.GA6882@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=bhmin@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=peter.ujfalusi@nokia.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