From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Greg Knight <g.knight@symetrica.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org
Subject: Re: Patches to bind the SGTL5000 chip to AM33XX McASP
Date: Thu, 19 Mar 2015 14:56:35 +0200 [thread overview]
Message-ID: <550AC783.8040304@ti.com> (raw)
In-Reply-To: <1426741659.10003.9.camel@midgaarde>
On 03/19/2015 07:07 AM, Greg Knight wrote:
> Hi, Mark, Jaroslav,
>
> I've attached a couple patches to provide support for the Freescale
> SGTL5000 chip when using the McASP on the AM3359.
It is more correct to say that this is needed in a custom hardware which uses
McASP and SGTL5000 codec.
> This adds an optional hack, "clock-to-talk" to the McASP subsystem which
> can start AHCLKX/AHCLKR prior to initializing the codec. This is needed
> on the SGTL5000, which depends on AHCLKX for its master clock.
SO is it so that the codec's MCLK is coming from McASP AHCLKX (or R) and this
clock need to be present all the time? W/o the MCLK the registers are not
accessible?
> These patches are based off of 3.14.31-ti-r49. What is the process for
> getting these merged?
First off, please send the patches with git send-email so people can comment
on them.
This will not work in mainline kernel. The McASP is turned off when it is not
in use (no audio activity) so the AHCLKX/R is not going to be there on the
ball output.
How do you configure the frequency of the AHCLKX/R, this hack only enables it,
so you are going to have _some_ clock going out.
You should be using set_clkdiv and set_sysclk calls from the machine driver to
configure the AHCLKX (we do not have AHCLKR supported in the driver ATM).
--
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-19 12:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 5:07 Patches to bind the SGTL5000 chip to AM33XX McASP Greg Knight
2015-03-19 11:38 ` Mark Brown
2015-03-19 12:56 ` Peter Ujfalusi [this message]
2015-03-19 14:34 ` Greg Knight
2015-03-19 16:07 ` Peter Ujfalusi
2015-03-19 17:17 ` Greg Knight
2015-03-19 17:48 ` Greg Knight
2015-03-20 8:09 ` Peter Ujfalusi
2015-03-22 17:48 ` Mark Brown
2015-03-19 18:06 ` Nikolay Dimitrov
2015-03-20 8:05 ` Peter Ujfalusi
2015-03-20 15:51 ` [alsa-devel] " Nikolay Dimitrov
2015-03-22 17:58 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2015-03-18 19:36 Greg Knight
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=550AC783.8040304@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=g.knight@symetrica.com \
--cc=linux-omap@vger.kernel.org \
--cc=perex@perex.cz \
/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).