From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: "jonsmirl@gmail.com" <jonsmirl@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
zengzm.kernel@gmail.com, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: SGTL500 and its external MCLK
Date: Fri, 8 Aug 2014 13:29:20 +0800 [thread overview]
Message-ID: <20140808052901.GA6028@MrMyself> (raw)
In-Reply-To: <CAKON4OxRr-igCSZ2HwXcKGFT7O6sQjJUMP_aF19kSRP59ZxFew@mail.gmail.com>
On Thu, Aug 07, 2014 at 03:37:47PM -0400, jonsmirl@gmail.com wrote:
> Since the sgtl5000 driver has the handle to the clock, can't it just
> ask the clock for its rate? If it directly asked the clock for its
> rate it looks like this codec could be bound with simple-audio-card
> and not need a machine driver.
I think Simple Card should already have the capability to support
this without changing sgtl5000's code. It has two properties that
can make it call set_sysclk() for you during the init(). They are
'clocks' and 'system-clock-frequency'. Please refer to its binding
doc for details.
And the topic why not let sgtl5000 fully control the clock has been
discussed in this thread:
http://comments.gmane.org/gmane.linux.alsa.devel/109093
So I think the change can be done as well?
Best regards,
Nicolin
next prev parent reply other threads:[~2014-08-08 5:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 19:37 SGTL500 and its external MCLK jonsmirl
2014-08-08 5:29 ` Nicolin Chen [this message]
2014-08-08 17:07 ` jonsmirl
2014-08-09 16:42 ` jonsmirl
2014-08-11 5:50 ` Nicolin Chen
2014-08-11 12:29 ` jonsmirl
2014-08-13 20:39 ` 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=20140808052901.GA6028@MrMyself \
--to=guangyu.chen@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jonsmirl@gmail.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=zengzm.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.