From: Tomko <tomko@avantwave.com>
To: Lee Revell <rlrevell@joe-job.com>, alsa-devel@alsa-project.org
Subject: Re: about the alsa i2c interface
Date: Thu, 09 Jun 2005 15:15:53 +0800 [thread overview]
Message-ID: <42A7ECA9.5020108@avantwave.com> (raw)
In-Reply-To: <1118299677.14638.1.camel@mindpipe>
Lee Revell wrote:
>On Thu, 2005-06-09 at 13:09 +1000, Tehn-Yit Chin wrote:
>
>
>>Hi,
>>
>>We are trying to provide support for the CS43L43 device under the ALSA
>>architecture on an embedded platform.
>>
>>During my early investigation, I noticed that ALSA has its own i2c code.
>>What is this required, and why doesn't it use the mainline i2c support?
>>On our platform, there are one other devices on the i2c bus, so I would
>>like to use the mainline i2c code.
>>
>>
>
>This is explained in "Writing an ALSA Driver" (you did read it,
>right?). Basically the kernel's i2c layer is overly complex, and ALSA
>only needs a small subset of it, so ALSA implements its own minimal i2c
>layer.
>
>
>
So will this cause losing control on the I2c device ? for example i have
4 device on the i2c bus , 3 of them are under the kernel's i2c which the
the sequence control that they can't access the bus at the same time and
one of them are under alsa's i2c , what will happen if the alsa's i2c
device and the kernel's i2c device access the bus together ?
Regards,
TOM
>Lee
>-------------------------------------------------------
>This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
>a projector? How fast can you ride your desk chair down the office luge track?
>If you want to score the big prize, get to know the little guy.
>Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
>_______________________________________________
>Alsa-devel mailing list
>Alsa-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/alsa-devel
>
>
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
next prev parent reply other threads:[~2005-06-09 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-09 3:09 about the alsa i2c interface Tehn-Yit Chin
2005-06-09 6:47 ` Lee Revell
2005-06-09 7:15 ` Tomko [this message]
2005-06-09 8:59 ` Jaroslav Kysela
-- strict thread matches above, loose matches on Subject: below --
2005-06-14 0:33 Tehn-Yit Chin
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=42A7ECA9.5020108@avantwave.com \
--to=tomko@avantwave.com \
--cc=alsa-devel@alsa-project.org \
--cc=rlrevell@joe-job.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.