From: Tomko <tomko@avantwave.com>
To: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: question : crash between kernel i2c and alsa i2c
Date: Tue, 14 Jun 2005 09:34:09 +0800 [thread overview]
Message-ID: <42AE3411.9040709@avantwave.com> (raw)
In-Reply-To: <s5hslzme9sk.wl@alsa2.suse.de>
Takashi Iwai wrote:
>At Mon, 13 Jun 2005 17:48:32 +0800,
>Tomko wrote:
>
>
>>Hi everyone,
>>
>>I know that there is a tiny i2c subsystem inside alsa , i would like to
>>know is there any control betwen the kernel i2c subsystem and the alsa
>>i2c ? Will there any crashes if two i2c access the bus togethre ?
>>
>>
>
>No, they have no relevence between them at all.
>If you try to access the same hardware, of course it would be a
>problem. But ALSA's i2c usually accesses only the chip-connection in
>the sound card, which is quite unlikely accessed from kernel i2c.
>
>
>
No, what i mean is what if they are accessing different device ? for
example kernel access it's own i2c device but alsa access it's i2c audio
device , but there is only ONE pair of i2c bus in hardware, just like
when the alsa's i2c just initiate a "START" and throw out the hardware
address but kernel's i2c want to initiate a "START" also and throw out
another hardware address . How's this situation be avoided if there is
no control between two i2c subsystem?
TOM
>Takashi
>
>
-------------------------------------------------------
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-14 1:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 9:48 question : crash between kernel i2c and alsa i2c Tomko
2005-06-13 12:06 ` Jaroslav Kysela
2005-06-13 12:11 ` Takashi Iwai
2005-06-14 1:34 ` Tomko [this message]
2005-06-14 8:35 ` Takashi Iwai
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=42AE3411.9040709@avantwave.com \
--to=tomko@avantwave.com \
--cc=alsa-devel@alsa-project.org \
--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 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.