From: "Urs Fässler" <urs.fassler@bytesatwork.ch>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, perex@perex.cz, tiwai@suse.de
Cc: lgirdwood@gmail.com, broonie@kernel.org, jsarha@ti.com,
misael.lopez@ti.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: davinci-mcasp: extension to use AHCLKX pin as external clock source
Date: Tue, 10 Feb 2015 15:17:30 +0100 [thread overview]
Message-ID: <54DA12FA.4090402@bytesatwork.ch> (raw)
In-Reply-To: <54D4AA7D.6050108@ti.com>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On 06.02.2015 12:50, Peter Ujfalusi wrote:
> On 02/06/2015 11:22 AM, Urs Fässler wrote:
>> The AHCLKX pin seems not to be supported as external source. The first
>> patch is a general fix to allow external clock. The second allows you to
>> select the AHCLKX pin as clock source.
>>
>> Patch built against v3.19-rc7
>>
>
> I don't think this series is correct. You can just issue:
> snd_soc_dai_set_sysclk(cpu_dai, 0, sysclk, SND_SOC_CLOCK_IN);
>
> from the machine driver to select AHCLKX as input.
>
I checked everything and the source of the problem is, that on our
hardware the bit clock of the codec is connected to AHCLKX. According to
the datasheet, AHCLKX is for the master clock only. On the other hand,
it is possible to route a bitclock from AHCLKX to the subsystem (what I
did with my patches).
Now my question is, if it is even worth trying to bring such an option
for the driver (use AHCLKX as bit clock in) upstream?
Thanks
Urs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-10 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 9:22 davinci-mcasp: extension to use AHCLKX pin as external clock source Urs Fässler
2015-02-06 11:50 ` Peter Ujfalusi
2015-02-10 14:17 ` Urs Fässler [this message]
2015-02-12 8:09 ` Peter Ujfalusi
2015-02-12 14:24 ` Urs Fässler
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=54DA12FA.4090402@bytesatwork.ch \
--to=urs.fassler@bytesatwork.ch \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jsarha@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=misael.lopez@ti.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@ti.com \
--cc=tiwai@suse.de \
/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