From: Troy Kisky <troy.kisky@boundarydevices.com>
To: Arun KS <arunks@mistralsolutions.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/5] [RFC] ALSA ASoC Support for TLVaic23b audio codec
Date: Mon, 29 Sep 2008 09:47:10 -0700 [thread overview]
Message-ID: <48E1068E.7020908@boundarydevices.com> (raw)
In-Reply-To: <dfeb90390809290241h2219ef57q2a7401aebf47efe5@mail.gmail.com>
Arun KS wrote:
> Hi all,
>
> The following patches adds ASOC driver for TLVaic23b audio codec.
>
> Tested playback and capture on omap 5912osk board with some hacks in the
> omap platform and machine driver.
>
> Thanks,
> Arun
> --
Great. I just finished the same thing for davinci but using spi.
I was waiting until the adc issue I mentioned yesterday was resolved before posting it.
I'm glad I won't have to now. But my board also has I2c, just not with this
codec. Can the I2c code be moved into the board directory? I have my spi code
in the board directory and just pass the write function pointer. i.e.
codec->hw_write = setup_data->hw_write;
Can you email me some data captured by from your mic input?
I'm interested in seeing if you have the same trouble in dsp_a
mode.
Thanks,
Troy
next prev parent reply other threads:[~2008-09-29 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 9:41 [PATCH 0/5] [RFC] ALSA ASoC Support for TLVaic23b audio codec Arun KS
2008-09-29 16:47 ` Troy Kisky [this message]
2008-09-29 16:54 ` Mark Brown
2008-09-29 17:05 ` Troy Kisky
2008-09-29 17:32 ` Mark Brown
2008-09-29 17:27 ` Troy Kisky
2008-09-29 17:39 ` Mark Brown
2008-09-29 17:58 ` Troy Kisky
2008-09-29 18:30 ` Mark Brown
2008-09-29 19:07 ` Troy Kisky
2008-09-29 19:50 ` Mark Brown
2008-09-29 21:15 ` Troy Kisky
-- strict thread matches above, loose matches on Subject: below --
2008-09-29 9:41 Arun KS
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=48E1068E.7020908@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=alsa-devel@alsa-project.org \
--cc=arunks@mistralsolutions.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.