Re: GPIO on envy24ht M-Audio 192

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



At Sat, 05 Aug 2006 17:16:10 -0400,
Cruise X Overide wrote:
> 
> 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, 

Nice information.

So the CCLK and CDTI are shared between two chips, and selected via
CS...  It's not exactly the standard i2c transfer of vt1724 chip,
hence you cannot use you'd need to implement the SPI/I2C transfer by
yourself.


Takashi

> 
> 
> 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
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-devel

[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux