From: "Pedro I. Sanchez" <psanchez@fosstel.com>
To: alsa-devel@alsa-project.org
Subject: Re: ASoC: at91sam9260-PCM1808/TAS5709-based board driver
Date: Tue, 11 Aug 2009 14:41:57 -0400 [thread overview]
Message-ID: <4A81BB75.3070405@fosstel.com> (raw)
In-Reply-To: <9e4733910908090637g4b9eaf19ud1b46de354664df2@mail.gmail.com>
Thank you John for the sample code. It's going to be very useful
specially when I get to the TAS5709 part and the I2C interface.
My next question is with regards to clocking on the SSC interface. The
PCM1808 in my board has a pretty straight forward connection as follows:
SSC-I/F PCM1808 Comment
RF ----> LRCK Frame clock
RK ----> BCK Bit clock
RD <---- DOUT Digital data
The PCM1808 is hardwired to be in slave mode. The two clock lines are
expected to be provided by the SoC's SSC interface.
I have the following code in my machine driver to request the SSC
interface and bind the PCM1808 to it:
/*
* Request SSC device
*/
ssc = ssc_request(0);
if (IS_ERR(ssc)) {
printk(KERN_ERR "ASoC: Failed to request SSC 0\n");
ret = PTR_ERR(ssc);
ssc = NULL;
goto err_ssc;
}
ssc_p->ssc = ssc;
What I need to do now is to set the SSC's clock divider to feed the
PCM1808 with the proper clocking. So these are my next questions:
1. How do I specify in the machine driver that my pcm1808 is hardwired
to slave mode and that I need bit/frame clocks to be provided by the SSC
interface?
2. How do I set the SSC's clock divider to provide the right clock signals?
Thanks again,
--
Pedro
Jon Smirl wrote:
> On Sun, Aug 9, 2009 at 9:35 AM, Jon Smirl<jonsmirl@gmail.com> wrote:
>> On Sat, Aug 8, 2009 at 1:39 PM, Pedro Sanchez<psanchez@fosstel.com> wrote:
>>> Hello,
>>>
>>> I have to develop a driver for a custom board based on the at91sam9260 with
>>> a PCM1808/TAS5709 chipset combo. I am addressing the PCM1808 first because
>>> it is a simpler device. Since I'm new to ASoC I'm looking for some help in
>>> this list on how to go about writing this driver.
>> I attached a PCM1690 driver I'm currently working on.
>
> The attached fabric driver show how to use it.
>
>>
>>> So far I have identified two files that I need to work on (other than the
>>> needed kconfig modifications). First is the codec driver at
>>> sound/soc/codecs/PCM1808.[c|h] which is based on the existent pcm3008
>>> driver; I believe I'm fine with this.
>>>
>>> The second file is the machine driver at sound/soc/atmel/myBoard.c. I'm
>>> using sam9g20_wm8731.c as reference, on which I believe I found a typo which
>>> I reported in a separated e-mail.
>>>
>>> So my first question is, is this two-files step the right approach? am I in
>>> the right track? I'm using the 2.6.30 kernel.
>>>
>>> Other questions will come and I hope I will get some cycles from you to help
>>> me direct my work. Of course I'll be glad to submit my driver work for
>>> inclusion in the kernel if it proves useful.
>>>
>>> Regards,
>>>
>>> --
>>> Pedro
>>>
>>>
>>> _______________________________________________
>>> Alsa-devel mailing list
>>> Alsa-devel@alsa-project.org
>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>>
>>>
>>
>>
>> --
>> Jon Smirl
>> jonsmirl@gmail.com
>>
>
>
>
next prev parent reply other threads:[~2009-08-11 18:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 17:39 ASoC: at91sam9260-PCM1808/TAS5709-based board driver Pedro Sanchez
2009-08-09 10:36 ` Mark Brown
2009-08-09 13:35 ` Jon Smirl
2009-08-09 13:37 ` Jon Smirl
2009-08-11 18:41 ` Pedro I. Sanchez [this message]
2009-08-11 18:51 ` Jon Smirl
2009-08-11 22:41 ` Mark Brown
2009-08-25 17:31 ` Pedro I. Sanchez
2009-08-25 18:29 ` Mark Brown
2009-08-25 19:46 ` Pedro I. Sanchez
2009-08-26 11:44 ` Mark Brown
2009-08-27 19:11 ` Pedro I. Sanchez
2009-08-28 12:15 ` Mark Brown
2009-08-28 21:24 ` Pedro I. Sanchez
2009-08-28 21:52 ` Pedro I. Sanchez
2009-08-29 9:18 ` Mark Brown
2009-08-29 16:01 ` Pedro I. Sanchez
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=4A81BB75.3070405@fosstel.com \
--to=psanchez@fosstel.com \
--cc=alsa-devel@alsa-project.org \
/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