From: Lars-Peter Clausen <lars@metafoo.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org, Matt Flax <flatmax@flatmax.org>
Subject: Re: SPI PCM capture device examples please
Date: Thu, 14 Nov 2013 15:36:58 +0100 [thread overview]
Message-ID: <5284E00A.5080409@metafoo.de> (raw)
In-Reply-To: <5284DA3A.9030602@ladisch.de>
On 11/14/2013 03:12 PM, Clemens Ladisch wrote:
> Matt Flax wrote:
>>> Is it possible to write an ALSA driver for a device which already has an SPI driver ?
>
> Yes, this is possible.
>
> Audio codecs typcially do not use SPI, so no such driver has been
> written yet.
>
>> I guess that IIO support for ASLA is not on the cards ?
>
> Well, that depends on whether you are going to write that driver ...
There is already a IIO driver for this part. So if you really wanted to use
it using the ALSA userspace API the best solution would be to write a
generic IIO-to-ALSA bridge.
- Lars
prev parent reply other threads:[~2013-11-14 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 12:07 SPI PCM capture device examples please Matt Flax
2013-11-14 1:01 ` Matt Flax
2013-11-14 14:12 ` Clemens Ladisch
2013-11-14 14:36 ` Lars-Peter Clausen [this message]
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=5284E00A.5080409@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=flatmax@flatmax.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;
as well as URLs for NNTP newsgroup(s).