Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cruise X Overide <cruiseoveride@gmail.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: GPIO on envy24ht M-Audio 192
Date: Tue, 01 Aug 2006 13:45:36 -0400	[thread overview]
Message-ID: <1154454336.3383.8.camel@server> (raw)
In-Reply-To: <s5hd5bkbfrw.wl%tiwai@suse.de>

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

  reply	other threads:[~2006-08-01 17:45 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 [this message]
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
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=1154454336.3383.8.camel@server \
    --to=cruiseoveride@gmail.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox