From: Cruise X Overide <cruiseoveride@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: GPIO on envy24ht M-Audio 192
Date: Sat, 05 Aug 2006 17:16:10 -0400 [thread overview]
Message-ID: <1154812570.15566.4.camel@server> (raw)
In-Reply-To: <s5hk65pww9l.wl%tiwai@suse.de>
Wiring Info for M-Audio Audiophile 192 (AP192K) Rev-E
--------------------------------------------------------
AK4358 <=> Envy24HT
--------------------------------------------------------
AK4358 pin 19 (CCLK/SCL) <-> Envy24HT pin 51 (GPIO1)
AK4358 pin 20 (CDTI/SDA) <-> Envy24HT pin 53 (GPIO3)
AK4358 pin 21 (CSN/CAD1) <-> Envy24HT pin 56 (GPIO4)
AK4114 <=> Envy24HT
-------------------------------------------------------
AK4114 pin 34 (CCLK) <-> Envy24HT pin 51 (GPIO1)
AK4114 pin 33 (CDTI) <-> Envy24HT pin 53 (GPIO3)
AK4114 pin 32 (CDTO) <-> Envy24HT pin 52 (GPIO2)
AK4114 pin 35 (CSN) <-> Envy24HT pin 59 (GPIO7)
AK5385A <=> Envy24HT
-------------------------------------------------------
AK5385 CKS0 does not appear to connect to Envy24HT
AK5385A DFS0 pin 18 <=> Envy24HT GPIO10 pin 77
AK5385A DFS1 pin 20 <=> either Envy24HT pin 78 or 79,
On Thu, 2006-08-03 at 19:43 +0200, Takashi Iwai wrote:
> At Thu, 03 Aug 2006 19:14:55 +0200,
> I wrote:
> >
> > At Thu, 03 Aug 2006 13:03:07 -0400,
> > Cruise X Overide wrote:
> > >
> > > how do i figure out the i2c address of each codec chip
> > > > is this in the datasheet of the aks?
> > > >
> > > > No. It should be in the datasheet of your M-Audio board (if any), but
> > > > not in the datasheet of controller or codec chips.
> > > >
> > > >
> > > > Takashi
> > >
> > > would have an idea where i could find such a datasheet?
> >
> > That's why I asked about the datasheet of the board (_not_ about
> > VT1724!) in the early reply...
> >
> > Only the board vendor (M-Audio) may provide such one. Ask them about
> > it.
>
> Well, actually, this is the most difficult part for writing a linux
> driver. Other things can get easier when you have more experiences.
>
> I forgot to mention that i2c address may be limited occasionally by
> the codec chip. In such a case, the amount of guess work would be
> much smaller. Check the datasheet of AK codecs precisely.
>
>
> Takashi
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-08-05 21:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 0:06 GPIO on envy24ht M-Audio 192 Cruise X Overide
2006-08-01 16:08 ` Takashi Iwai
2006-08-01 17:45 ` Cruise X Overide
2006-08-02 16:30 ` Takashi Iwai
2006-08-02 16:33 ` Cruise X Overide
2006-08-02 16:46 ` Takashi Iwai
2006-08-02 17:29 ` Cruise X Overide
2006-08-02 17:39 ` Takashi Iwai
2006-08-02 17:45 ` Lee Revell
2006-08-02 18:32 ` Takashi Iwai
2006-08-02 19:37 ` Cruise X Overide
2006-08-02 19:50 ` Liam Girdwood
2006-08-03 10:26 ` Takashi Iwai
2006-08-03 17:03 ` Cruise X Overide
2006-08-03 17:14 ` Takashi Iwai
2006-08-03 17:43 ` Takashi Iwai
2006-08-05 21:16 ` Cruise X Overide [this message]
2006-08-07 18:23 ` 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=1154812570.15566.4.camel@server \
--to=cruiseoveride@gmail.com \
--cc=alsa-devel@lists.sourceforge.net \
--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.