GPIO on envy24ht M-Audio 192

GPIO on envy24ht M-Audio 192

[Cruise X Overide]

Ok, i got the wiring between between the vt1724 and the 3 dacs (AKMs)
how do i code this into the driver, 
is there any example, i looked at juli.c and i couldnt understand the 

/* GPIO Pins */

i was told that i only need to implement add_controls and init for this
card?


-------------------------------------------------------------------------
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

Re: GPIO on envy24ht M-Audio 192

[Takashi Iwai]

At Mon, 31 Jul 2006 20:06:13 -0400,
Cruise X Overide wrote:
> 
> Ok, i got the wiring between between the vt1724 and the 3 dacs (AKMs)
> how do i code this into the driver, 
> is there any example, i looked at juli.c and i couldnt understand the 
> 
> /* GPIO Pins */
> 
> i was told that i only need to implement add_controls and init for this
> card?

There are different implementations with vt1724.
revo.c, aureon.c, pontis.c, prodigy192.c and phase.c are vt1724-based
boards using I2S transfer.  vt1720_mobo.c is for vt1724 with
ac97-codec.

The GPIO is usually controlled via snd_ice1712_gpio_write_bits() and
snd_ice1712_gpio_read().  See ice1712.h.

For AK codecs, there are some helper functions.  See
snd_ak4xxx_private in ice1712.h, too.


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

Re: GPIO on envy24ht M-Audio 192

[Cruise X Overide]

On Tue, 2006-08-01 at 18:08 +0200, Takashi Iwai wrote:
> At Mon, 31 Jul 2006 20:06:13 -0400,
> Cruise X Overide wrote:
> > 
> > Ok, i got the wiring between between the vt1724 and the 3 dacs (AKMs)
> > how do i code this into the driver, 
> > is there any example, i looked at juli.c and i couldnt understand the 
> > 
> > /* GPIO Pins */
> > 
> > i was told that i only need to implement add_controls and init for this
> > card?
> 
> There are different implementations with vt1724.
> revo.c, aureon.c, pontis.c, prodigy192.c and phase.c are vt1724-based
> boards using I2S transfer.  vt1720_mobo.c is for vt1724 with
> ac97-codec.
> 
> The GPIO is usually controlled via snd_ice1712_gpio_write_bits() and
> snd_ice1712_gpio_read().  See ice1712.h.
> 
> For AK codecs, there are some helper functions.  See
> snd_ak4xxx_private in ice1712.h, too.
> 
> 
> Takashi

after looking at the juli.c, raymond has explained to me the meaning of
the values under the /* GPIO Pins */


#define GPIO_ANAIN_MONITOR      (1<<13) 

i wanted to know wat the 13 means, and ray said it was the gpio pin.
where do i find a table of gpio description (eg. AMAIN_MONITOR) and
available definitions on the vt1724.



-------------------------------------------------------------------------
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

Re: GPIO on envy24ht M-Audio 192

[Takashi Iwai]

At Tue, 01 Aug 2006 13:45:36 -0400,
Cruise X Overide wrote:
> 
> On Tue, 2006-08-01 at 18:08 +0200, Takashi Iwai wrote:
> > At Mon, 31 Jul 2006 20:06:13 -0400,
> > Cruise X Overide wrote:
> > > 
> > > Ok, i got the wiring between between the vt1724 and the 3 dacs (AKMs)
> > > how do i code this into the driver, 
> > > is there any example, i looked at juli.c and i couldnt understand the 
> > > 
> > > /* GPIO Pins */
> > > 
> > > i was told that i only need to implement add_controls and init for this
> > > card?
> > 
> > There are different implementations with vt1724.
> > revo.c, aureon.c, pontis.c, prodigy192.c and phase.c are vt1724-based
> > boards using I2S transfer.  vt1720_mobo.c is for vt1724 with
> > ac97-codec.
> > 
> > The GPIO is usually controlled via snd_ice1712_gpio_write_bits() and
> > snd_ice1712_gpio_read().  See ice1712.h.
> > 
> > For AK codecs, there are some helper functions.  See
> > snd_ak4xxx_private in ice1712.h, too.
> > 
> > 
> > Takashi
> 
> after looking at the juli.c, raymond has explained to me the meaning of
> the values under the /* GPIO Pins */
> 
> 
> #define GPIO_ANAIN_MONITOR      (1<<13) 
> 
> i wanted to know wat the 13 means, and ray said it was the gpio pin.
> where do i find a table of gpio description (eg. AMAIN_MONITOR) and
> available definitions on the vt1724.

The GPIO pin assignment is the board specific implementation, so it's
nowhere described in VT1724 database, of course.  (If you have a
board, you can even trace the connection with loupe :)


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

Re: GPIO on envy24ht M-Audio 192

[Cruise X Overide]

On Wed, 2006-08-02 at 18:30 +0200, Takashi Iwai wrote:
> At Tue, 01 Aug 2006 13:45:36 -0400,
> Cruise X Overide wrote:
> > 
> > On Tue, 2006-08-01 at 18:08 +0200, Takashi Iwai wrote:
> > > At Mon, 31 Jul 2006 20:06:13 -0400,
> > > Cruise X Overide wrote:
> > > > 
> > > > Ok, i got the wiring between between the vt1724 and the 3 dacs (AKMs)
> > > > how do i code this into the driver, 
> > > > is there any example, i looked at juli.c and i couldnt understand the 
> > > > 
> > > > /* GPIO Pins */
> > > > 
> > > > i was told that i only need to implement add_controls and init for this
> > > > card?
> > > 
> > > There are different implementations with vt1724.
> > > revo.c, aureon.c, pontis.c, prodigy192.c and phase.c are vt1724-based
> > > boards using I2S transfer.  vt1720_mobo.c is for vt1724 with
> > > ac97-codec.
> > > 
> > > The GPIO is usually controlled via snd_ice1712_gpio_write_bits() and
> > > snd_ice1712_gpio_read().  See ice1712.h.
> > > 
> > > For AK codecs, there are some helper functions.  See
> > > snd_ak4xxx_private in ice1712.h, too.
> > > 
> > > 
> > > Takashi
> > 
> > after looking at the juli.c, raymond has explained to me the meaning of
> > the values under the /* GPIO Pins */
> > 
> > 
> > #define GPIO_ANAIN_MONITOR      (1<<13) 
> > 
> > i wanted to know wat the 13 means, and ray said it was the gpio pin.
> > where do i find a table of gpio description (eg. AMAIN_MONITOR) and
> > available definitions on the vt1724.
> 
> The GPIO pin assignment is the board specific implementation, so it's
> nowhere described in VT1724 database, of course.  (If you have a
> board, you can even trace the connection with loupe :)
> 
> 
> Takashi

im completely new to driver development.
how do i tell my (/linux/sound/pci/ice1712/ap192k.c) driver which gpio
pins connect to wat? i have all the wiring from ak4385 and ak4114 to the
envy24ht, as well as the data sheets, can someone point me in the
direction i have to take to get this driver working? and please for god
sake dont tell me to go and read, if u know the answer, dont be shy,


-------------------------------------------------------------------------
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

Re: GPIO on envy24ht M-Audio 192

[Takashi Iwai]

At Wed, 02 Aug 2006 12:33:40 -0400,
Cruise X Overide wrote:
> 
> On Wed, 2006-08-02 at 18:30 +0200, Takashi Iwai wrote:
> > At Tue, 01 Aug 2006 13:45:36 -0400,
> > Cruise X Overide wrote:
> > > 
> > > On Tue, 2006-08-01 at 18:08 +0200, Takashi Iwai wrote:
> > > > At Mon, 31 Jul 2006 20:06:13 -0400,
> > > > Cruise X Overide wrote:
> > > > > 
> > > > > Ok, i got the wiring between between the vt1724 and the 3 dacs (AKMs)
> > > > > how do i code this into the driver, 
> > > > > is there any example, i looked at juli.c and i couldnt understand the 
> > > > > 
> > > > > /* GPIO Pins */
> > > > > 
> > > > > i was told that i only need to implement add_controls and init for this
> > > > > card?
> > > > 
> > > > There are different implementations with vt1724.
> > > > revo.c, aureon.c, pontis.c, prodigy192.c and phase.c are vt1724-based
> > > > boards using I2S transfer.  vt1720_mobo.c is for vt1724 with
> > > > ac97-codec.
> > > > 
> > > > The GPIO is usually controlled via snd_ice1712_gpio_write_bits() and
> > > > snd_ice1712_gpio_read().  See ice1712.h.
> > > > 
> > > > For AK codecs, there are some helper functions.  See
> > > > snd_ak4xxx_private in ice1712.h, too.
> > > > 
> > > > 
> > > > Takashi
> > > 
> > > after looking at the juli.c, raymond has explained to me the meaning of
> > > the values under the /* GPIO Pins */
> > > 
> > > 
> > > #define GPIO_ANAIN_MONITOR      (1<<13) 
> > > 
> > > i wanted to know wat the 13 means, and ray said it was the gpio pin.
> > > where do i find a table of gpio description (eg. AMAIN_MONITOR) and
> > > available definitions on the vt1724.
> > 
> > The GPIO pin assignment is the board specific implementation, so it's
> > nowhere described in VT1724 database, of course.  (If you have a
> > board, you can even trace the connection with loupe :)
> > 
> > 
> > Takashi
> 
> im completely new to driver development.
> how do i tell my (/linux/sound/pci/ice1712/ap192k.c) driver which gpio
> pins connect to wat? i have all the wiring from ak4385 and ak4114 to the
> envy24ht, as well as the data sheets, can someone point me in the
> direction i have to take to get this driver working? and please for god
> sake dont tell me to go and read, if u know the answer, dont be shy,

One of the following ways:

1. Get a datasheet of your board (not vt1724) from the hardware
   vendor.  There must be a diagram or a table of pin connection
   there.

2. Look close the board design and trace the pin connections between
   vt1724 and codec chips.  The pin numbers are found in datasheet of
   vt1724 and each codec chip.

3. Trial-and-error the different pin numbers, assuming that the board
   is almost compatible with other models.

But, before going there, you have to know what kind of data transfer
is used - whether the normal i2c connection (via snd_vt1724_write_i2c)
or over own transfer protocol with GPIO.  In the latter case, then
you'd need to know which transfer mode, SPI or I2C, and whether
CIF-mode is not, etc.

So, it's basically not how well you are skilled about driver
programming but how well you know about the board implementation.


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

Re: GPIO on envy24ht M-Audio 192

[Cruise X Overide]

On Wed, 2006-08-02 at 18:46 +0200, Takashi Iwai wrote:
> At Wed, 02 Aug 2006 12:33:40 -0400,
> Cruise X Overide wrote:
> > 
> > On Wed, 2006-08-02 at 18:30 +0200, Takashi Iwai wrote:
> > > At Tue, 01 Aug 2006 13:45:36 -0400,
> > > Cruise X Overide wrote:
> > > > 
> > > > On Tue, 2006-08-01 at 18:08 +0200, Takashi Iwai wrote:
> > > > > At Mon, 31 Jul 2006 20:06:13 -0400,
> > > > > Cruise X Overide wrote:
> > > > > > 
> > > > > > Ok, i got the wiring between between the vt1724 and the 3 dacs (AKMs)
> > > > > > how do i code this into the driver, 
> > > > > > is there any example, i looked at juli.c and i couldnt understand the 
> > > > > > 
> > > > > > /* GPIO Pins */
> > > > > > 
> > > > > > i was told that i only need to implement add_controls and init for this
> > > > > > card?
> > > > > 
> > > > > There are different implementations with vt1724.
> > > > > revo.c, aureon.c, pontis.c, prodigy192.c and phase.c are vt1724-based
> > > > > boards using I2S transfer.  vt1720_mobo.c is for vt1724 with
> > > > > ac97-codec.
> > > > > 
> > > > > The GPIO is usually controlled via snd_ice1712_gpio_write_bits() and
> > > > > snd_ice1712_gpio_read().  See ice1712.h.
> > > > > 
> > > > > For AK codecs, there are some helper functions.  See
> > > > > snd_ak4xxx_private in ice1712.h, too.
> > > > > 
> > > > > 
> > > > > Takashi
> > > > 
> > > > after looking at the juli.c, raymond has explained to me the meaning of
> > > > the values under the /* GPIO Pins */
> > > > 
> > > > 
> > > > #define GPIO_ANAIN_MONITOR      (1<<13) 
> > > > 
> > > > i wanted to know wat the 13 means, and ray said it was the gpio pin.
> > > > where do i find a table of gpio description (eg. AMAIN_MONITOR) and
> > > > available definitions on the vt1724.
> > > 
> > > The GPIO pin assignment is the board specific implementation, so it's
> > > nowhere described in VT1724 database, of course.  (If you have a
> > > board, you can even trace the connection with loupe :)
> > > 
> > > 
> > > Takashi
> > 
> > im completely new to driver development.
> > how do i tell my (/linux/sound/pci/ice1712/ap192k.c) driver which gpio
> > pins connect to wat? i have all the wiring from ak4385 and ak4114 to the
> > envy24ht, as well as the data sheets, can someone point me in the
> > direction i have to take to get this driver working? and please for god
> > sake dont tell me to go and read, if u know the answer, dont be shy,
> 
> One of the following ways:
> 
> 1. Get a datasheet of your board (not vt1724) from the hardware
>    vendor.  There must be a diagram or a table of pin connection
>    there.
> 
> 2. Look close the board design and trace the pin connections between
>    vt1724 and codec chips.  The pin numbers are found in datasheet of
>    vt1724 and each codec chip.
> 
> 3. Trial-and-error the different pin numbers, assuming that the board
>    is almost compatible with other models.
> 
> But, before going there, you have to know what kind of data transfer
> is used - whether the normal i2c connection (via snd_vt1724_write_i2c)
> or over own transfer protocol with GPIO.  In the latter case, then
> you'd need to know which transfer mode, SPI or I2C, and whether
> CIF-mode is not, etc.
> 
> So, it's basically not how well you are skilled about driver
> programming but how well you know about the board implementation.
> 
> 
> Takashi

1,2,3 done, 
we're using i2c.


i have 
envy24ht->ak4358
envy24ht->ak4114

all gpio stuff on the envy have been mapped onto the aks

now wat



-------------------------------------------------------------------------
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

Re: GPIO on envy24ht M-Audio 192

[Takashi Iwai]

At Wed, 02 Aug 2006 13:29:39 -0400,
Cruise X Overide wrote:
> 
> On Wed, 2006-08-02 at 18:46 +0200, Takashi Iwai wrote:
> > At Wed, 02 Aug 2006 12:33:40 -0400,
> > Cruise X Overide wrote:
> > > 
> > > On Wed, 2006-08-02 at 18:30 +0200, Takashi Iwai wrote:
> > > > At Tue, 01 Aug 2006 13:45:36 -0400,
> > > > Cruise X Overide wrote:
> > > > > 
> > > > > On Tue, 2006-08-01 at 18:08 +0200, Takashi Iwai wrote:
> > > > > > At Mon, 31 Jul 2006 20:06:13 -0400,
> > > > > > Cruise X Overide wrote:
> > > > > > > 
> > > > > > > Ok, i got the wiring between between the vt1724 and the 3 dacs (AKMs)
> > > > > > > how do i code this into the driver, 
> > > > > > > is there any example, i looked at juli.c and i couldnt understand the 
> > > > > > > 
> > > > > > > /* GPIO Pins */
> > > > > > > 
> > > > > > > i was told that i only need to implement add_controls and init for this
> > > > > > > card?
> > > > > > 
> > > > > > There are different implementations with vt1724.
> > > > > > revo.c, aureon.c, pontis.c, prodigy192.c and phase.c are vt1724-based
> > > > > > boards using I2S transfer.  vt1720_mobo.c is for vt1724 with
> > > > > > ac97-codec.
> > > > > > 
> > > > > > The GPIO is usually controlled via snd_ice1712_gpio_write_bits() and
> > > > > > snd_ice1712_gpio_read().  See ice1712.h.
> > > > > > 
> > > > > > For AK codecs, there are some helper functions.  See
> > > > > > snd_ak4xxx_private in ice1712.h, too.
> > > > > > 
> > > > > > 
> > > > > > Takashi
> > > > > 
> > > > > after looking at the juli.c, raymond has explained to me the meaning of
> > > > > the values under the /* GPIO Pins */
> > > > > 
> > > > > 
> > > > > #define GPIO_ANAIN_MONITOR      (1<<13) 
> > > > > 
> > > > > i wanted to know wat the 13 means, and ray said it was the gpio pin.
> > > > > where do i find a table of gpio description (eg. AMAIN_MONITOR) and
> > > > > available definitions on the vt1724.
> > > > 
> > > > The GPIO pin assignment is the board specific implementation, so it's
> > > > nowhere described in VT1724 database, of course.  (If you have a
> > > > board, you can even trace the connection with loupe :)
> > > > 
> > > > 
> > > > Takashi
> > > 
> > > im completely new to driver development.
> > > how do i tell my (/linux/sound/pci/ice1712/ap192k.c) driver which gpio
> > > pins connect to wat? i have all the wiring from ak4385 and ak4114 to the
> > > envy24ht, as well as the data sheets, can someone point me in the
> > > direction i have to take to get this driver working? and please for god
> > > sake dont tell me to go and read, if u know the answer, dont be shy,
> > 
> > One of the following ways:
> > 
> > 1. Get a datasheet of your board (not vt1724) from the hardware
> >    vendor.  There must be a diagram or a table of pin connection
> >    there.
> > 
> > 2. Look close the board design and trace the pin connections between
> >    vt1724 and codec chips.  The pin numbers are found in datasheet of
> >    vt1724 and each codec chip.
> > 
> > 3. Trial-and-error the different pin numbers, assuming that the board
> >    is almost compatible with other models.
> > 
> > But, before going there, you have to know what kind of data transfer
> > is used - whether the normal i2c connection (via snd_vt1724_write_i2c)
> > or over own transfer protocol with GPIO.  In the latter case, then
> > you'd need to know which transfer mode, SPI or I2C, and whether
> > CIF-mode is not, etc.
> > 
> > So, it's basically not how well you are skilled about driver
> > programming but how well you know about the board implementation.
> > 
> > 
> > Takashi
> 
> 1,2,3 done, 
> we're using i2c.
> 
> 
> i have 
> envy24ht->ak4358
> envy24ht->ak4114
> 
> all gpio stuff on the envy have been mapped onto the aks
> 
> now wat

Wat?


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

Re: GPIO on envy24ht M-Audio 192

[Lee Revell]

On Wed, 2006-08-02 at 19:39 +0200, Takashi Iwai wrote:
> > now wat
> 
> Wat? 

I think he means "Now what?"

Lee


-------------------------------------------------------------------------
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

Re: GPIO on envy24ht M-Audio 192

[Takashi Iwai]

At Wed, 02 Aug 2006 13:45:02 -0400,
Lee Revell wrote:
> 
> On Wed, 2006-08-02 at 19:39 +0200, Takashi Iwai wrote:
> > > now wat
> > 
> > Wat? 
> 
> I think he means "Now what?"

then figure out i2c address of each codec chip


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

Re: GPIO on envy24ht M-Audio 192

[Cruise X Overide]

On Wed, 2006-08-02 at 19:39 +0200, Takashi Iwai wrote:
> At Wed, 02 Aug 2006 13:29:39 -0400,
> Cruise X Overide wrote:
> > 
> > On Wed, 2006-08-02 at 18:46 +0200, Takashi Iwai wrote:
> > > At Wed, 02 Aug 2006 12:33:40 -0400,
> > > Cruise X Overide wrote:
> > > > 
> > > > On Wed, 2006-08-02 at 18:30 +0200, Takashi Iwai wrote:
> > > > > At Tue, 01 Aug 2006 13:45:36 -0400,
> > > > > Cruise X Overide wrote:
> > > > > > 
> > > > > > On Tue, 2006-08-01 at 18:08 +0200, Takashi Iwai wrote:
> > > > > > > At Mon, 31 Jul 2006 20:06:13 -0400,
> > > > > > > Cruise X Overide wrote:
> > > > > > > > 
> > > > > > > > Ok, i got the wiring between between the vt1724 and the 3 dacs (AKMs)
> > > > > > > > how do i code this into the driver, 
> > > > > > > > is there any example, i looked at juli.c and i couldnt understand the 
> > > > > > > > 
> > > > > > > > /* GPIO Pins */
> > > > > > > > 
> > > > > > > > i was told that i only need to implement add_controls and init for this
> > > > > > > > card?
> > > > > > > 
> > > > > > > There are different implementations with vt1724.
> > > > > > > revo.c, aureon.c, pontis.c, prodigy192.c and phase.c are vt1724-based
> > > > > > > boards using I2S transfer.  vt1720_mobo.c is for vt1724 with
> > > > > > > ac97-codec.
> > > > > > > 
> > > > > > > The GPIO is usually controlled via snd_ice1712_gpio_write_bits() and
> > > > > > > snd_ice1712_gpio_read().  See ice1712.h.
> > > > > > > 
> > > > > > > For AK codecs, there are some helper functions.  See
> > > > > > > snd_ak4xxx_private in ice1712.h, too.
> > > > > > > 
> > > > > > > 
> > > > > > > Takashi
> > > > > > 
> > > > > > after looking at the juli.c, raymond has explained to me the meaning of
> > > > > > the values under the /* GPIO Pins */
> > > > > > 
> > > > > > 
> > > > > > #define GPIO_ANAIN_MONITOR      (1<<13) 
> > > > > > 
> > > > > > i wanted to know wat the 13 means, and ray said it was the gpio pin.
> > > > > > where do i find a table of gpio description (eg. AMAIN_MONITOR) and
> > > > > > available definitions on the vt1724.
> > > > > 
> > > > > The GPIO pin assignment is the board specific implementation, so it's
> > > > > nowhere described in VT1724 database, of course.  (If you have a
> > > > > board, you can even trace the connection with loupe :)
> > > > > 
> > > > > 
> > > > > Takashi
> > > > 
> > > > im completely new to driver development.
> > > > how do i tell my (/linux/sound/pci/ice1712/ap192k.c) driver which gpio
> > > > pins connect to wat? i have all the wiring from ak4385 and ak4114 to the
> > > > envy24ht, as well as the data sheets, can someone point me in the
> > > > direction i have to take to get this driver working? and please for god
> > > > sake dont tell me to go and read, if u know the answer, dont be shy,
> > > 
> > > One of the following ways:
> > > 
> > > 1. Get a datasheet of your board (not vt1724) from the hardware
> > >    vendor.  There must be a diagram or a table of pin connection
> > >    there.
> > > 
> > > 2. Look close the board design and trace the pin connections between
> > >    vt1724 and codec chips.  The pin numbers are found in datasheet of
> > >    vt1724 and each codec chip.
> > > 
> > > 3. Trial-and-error the different pin numbers, assuming that the board
> > >    is almost compatible with other models.
> > > 
> > > But, before going there, you have to know what kind of data transfer
> > > is used - whether the normal i2c connection (via snd_vt1724_write_i2c)
> > > or over own transfer protocol with GPIO.  In the latter case, then
> > > you'd need to know which transfer mode, SPI or I2C, and whether
> > > CIF-mode is not, etc.
> > > 
> > > So, it's basically not how well you are skilled about driver
> > > programming but how well you know about the board implementation.
> > > 
> > > 
> > > Takashi
> > 
> > 1,2,3 done, 
> > we're using i2c.
> > 
> > 
> > i have 
> > envy24ht->ak4358
> > envy24ht->ak4114
> > 
> > all gpio stuff on the envy have been mapped onto the aks
> > 
> > now wat
> 
> Wat?
> 
> 
> Takashi

how do i figure out the i2c address of each codec chip
is this in the datasheet of the aks?


-------------------------------------------------------------------------
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

Re: GPIO on envy24ht M-Audio 192

[Liam Girdwood]

On Wed, 2006-08-02 at 15:37 -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?
> 
> 

Yes.

Codec's usually support a few i2c addresses. The address is usually set
by the level of another codec pin being held high or low at power on.
All this information is in the codec datasheet.

Liam


-------------------------------------------------------------------------
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

Re: GPIO on envy24ht M-Audio 192

[Takashi Iwai]

At Wed, 02 Aug 2006 15:37:43 -0400,
Cruise X Overide wrote:
> 
> On Wed, 2006-08-02 at 19:39 +0200, Takashi Iwai wrote:
> > At Wed, 02 Aug 2006 13:29:39 -0400,
> > Cruise X Overide wrote:
> > > 
> > > On Wed, 2006-08-02 at 18:46 +0200, Takashi Iwai wrote:
> > > > At Wed, 02 Aug 2006 12:33:40 -0400,
> > > > Cruise X Overide wrote:
> > > > > 
> > > > > On Wed, 2006-08-02 at 18:30 +0200, Takashi Iwai wrote:
> > > > > > At Tue, 01 Aug 2006 13:45:36 -0400,
> > > > > > Cruise X Overide wrote:
> > > > > > > 
> > > > > > > On Tue, 2006-08-01 at 18:08 +0200, Takashi Iwai wrote:
> > > > > > > > At Mon, 31 Jul 2006 20:06:13 -0400,
> > > > > > > > Cruise X Overide wrote:
> > > > > > > > > 
> > > > > > > > > Ok, i got the wiring between between the vt1724 and the 3 dacs (AKMs)
> > > > > > > > > how do i code this into the driver, 
> > > > > > > > > is there any example, i looked at juli.c and i couldnt understand the 
> > > > > > > > > 
> > > > > > > > > /* GPIO Pins */
> > > > > > > > > 
> > > > > > > > > i was told that i only need to implement add_controls and init for this
> > > > > > > > > card?
> > > > > > > > 
> > > > > > > > There are different implementations with vt1724.
> > > > > > > > revo.c, aureon.c, pontis.c, prodigy192.c and phase.c are vt1724-based
> > > > > > > > boards using I2S transfer.  vt1720_mobo.c is for vt1724 with
> > > > > > > > ac97-codec.
> > > > > > > > 
> > > > > > > > The GPIO is usually controlled via snd_ice1712_gpio_write_bits() and
> > > > > > > > snd_ice1712_gpio_read().  See ice1712.h.
> > > > > > > > 
> > > > > > > > For AK codecs, there are some helper functions.  See
> > > > > > > > snd_ak4xxx_private in ice1712.h, too.
> > > > > > > > 
> > > > > > > > 
> > > > > > > > Takashi
> > > > > > > 
> > > > > > > after looking at the juli.c, raymond has explained to me the meaning of
> > > > > > > the values under the /* GPIO Pins */
> > > > > > > 
> > > > > > > 
> > > > > > > #define GPIO_ANAIN_MONITOR      (1<<13) 
> > > > > > > 
> > > > > > > i wanted to know wat the 13 means, and ray said it was the gpio pin.
> > > > > > > where do i find a table of gpio description (eg. AMAIN_MONITOR) and
> > > > > > > available definitions on the vt1724.
> > > > > > 
> > > > > > The GPIO pin assignment is the board specific implementation, so it's
> > > > > > nowhere described in VT1724 database, of course.  (If you have a
> > > > > > board, you can even trace the connection with loupe :)
> > > > > > 
> > > > > > 
> > > > > > Takashi
> > > > > 
> > > > > im completely new to driver development.
> > > > > how do i tell my (/linux/sound/pci/ice1712/ap192k.c) driver which gpio
> > > > > pins connect to wat? i have all the wiring from ak4385 and ak4114 to the
> > > > > envy24ht, as well as the data sheets, can someone point me in the
> > > > > direction i have to take to get this driver working? and please for god
> > > > > sake dont tell me to go and read, if u know the answer, dont be shy,
> > > > 
> > > > One of the following ways:
> > > > 
> > > > 1. Get a datasheet of your board (not vt1724) from the hardware
> > > >    vendor.  There must be a diagram or a table of pin connection
> > > >    there.
> > > > 
> > > > 2. Look close the board design and trace the pin connections between
> > > >    vt1724 and codec chips.  The pin numbers are found in datasheet of
> > > >    vt1724 and each codec chip.
> > > > 
> > > > 3. Trial-and-error the different pin numbers, assuming that the board
> > > >    is almost compatible with other models.
> > > > 
> > > > But, before going there, you have to know what kind of data transfer
> > > > is used - whether the normal i2c connection (via snd_vt1724_write_i2c)
> > > > or over own transfer protocol with GPIO.  In the latter case, then
> > > > you'd need to know which transfer mode, SPI or I2C, and whether
> > > > CIF-mode is not, etc.
> > > > 
> > > > So, it's basically not how well you are skilled about driver
> > > > programming but how well you know about the board implementation.
> > > > 
> > > > 
> > > > Takashi
> > > 
> > > 1,2,3 done, 
> > > we're using i2c.
> > > 
> > > 
> > > i have 
> > > envy24ht->ak4358
> > > envy24ht->ak4114
> > > 
> > > all gpio stuff on the envy have been mapped onto the aks
> > > 
> > > now wat
> > 
> > Wat?
> > 
> > 
> > Takashi
> 
> how do i figure out the i2c address of each codec chip

Well, it's board specific, and it's what you need to know beforehand.
If you don't know, the driver can't be implemented.

> 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

-------------------------------------------------------------------------
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

Re: GPIO on envy24ht M-Audio 192

[Cruise X Overide]

 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?


-------------------------------------------------------------------------
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

Re: GPIO on envy24ht M-Audio 192

[Takashi Iwai]

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.


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

Re: GPIO on envy24ht M-Audio 192

[Takashi Iwai]

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

Re: GPIO on envy24ht M-Audio 192

[Cruise X Overide]

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

Re: GPIO on envy24ht M-Audio 192

[Takashi Iwai]

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@lists.sourceforge.net
> 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