All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Pingenot <trelane@digitasaru.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vanilla 2.6.0-test11 and CS4236 card
Date: Tue, 2 Dec 2003 15:04:43 -0600	[thread overview]
Message-ID: <20031202210441.GF5475@digitasaru.net> (raw)
In-Reply-To: <s5hsmk3ceia.wl@alsa2.suse.de>

An update.  I've traced the problems down into snd_cs4231_probe().
After adding diagnostic printk statements, I get the following:
     *vcs4231_inb() returned 0xff
     *val is now 0x80
     *cs4231_inb & CS4231_INIT returned TRUE
     cs4231: port = 0x530, id = 0x0
     id is incorrect (id=0x00, but should be 0x0a)
    err in call to snd_cs4231_probe
err in call to snd_cs4231_create!
err running snd_cs4236_create!
CS4236+ soundcard not found or device busy
[all but the last line are mine].  the stuff prefixed by "*" comes from
  here in snd_cs4231_probe:

	for (i = 0; i < 50; i++) {
		mb();
		val = cs4231_inb(chip, CS4231P(REGSEL));
		printk("     *vcs4231_inb() returned 0x%0x\n", val);
		val &= CS4231_INIT;
		printk("     *val is now 0x%0x\n", val);
		/*if (cs4231_inb(chip, CS4231P(REGSEL)) & CS4231_INIT) {*/
		if (val) {
		  printk("     *cs4231_inb & CS4231_INIT returned TRUE\n");
			udelay(2000);
		} else {
			spin_lock_irqsave(&chip->reg_lock, flags);
			snd_cs4231_out(chip, CS4231_MISC_INFO, CS4231_MODE2);
			id = snd_cs4231_in(chip, CS4231_MISC_INFO) & 0x0f;
			printk("     *detecting id: id=%02x\n", id);
			spin_unlock_irqrestore(&chip->reg_lock, flags);
			if (id == 0x0a)
				break;	/* this is valid value */
		}
	}

Anyone know what the io port here does, and what the different return
  values are?  Pointers to documentation is more than welcome!  :)

Thanks!

-Joseph
-- 
trelane@digitasaru.net--------------------------------------------------
"We continue to live in a world where all our know-how is locked into
 binary files in an unknown format. If our documents are our corporate
 memory, Microsoft still has us all condemned to Alzheimer's."
    --Simon Phipps, http://theregister.com/content/4/30410.html





  parent reply	other threads:[~2003-12-02 21:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-02 17:06 vanilla 2.6.0-test11 and CS4236 card Joseph Pingenot
2003-12-02 17:31 ` Takashi Iwai
2003-12-02 17:52   ` Joseph Pingenot
2003-12-02 21:04   ` Joseph Pingenot [this message]
2003-12-02 23:44   ` Adam Belay
2003-12-03 11:22     ` Takashi Iwai
2003-12-03 15:00       ` wes schreiner
2003-12-03 15:16         ` Joseph Pingenot
2003-12-03  3:17   ` Joseph Pingenot
2003-12-03 11:29     ` Takashi Iwai
2003-12-03 14:09       ` Joseph Pingenot
2003-12-04 20:31   ` Joseph Pingenot

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=20031202210441.GF5475@digitasaru.net \
    --to=trelane@digitasaru.net \
    --cc=linux-kernel@vger.kernel.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.