From: Clemens Ladisch <clemens@ladisch.de>
To: Ian Dawes <madeallup.gen@gmail.com>
Cc: alsa-devel@alsa-project.org, patch@alsa-project.org
Subject: Re: [PATCH - Preliminary support for Xonar Xense (resubmitAdded support for Xonar Xense. Only speaker out and mic in working.
Date: Mon, 29 Jul 2013 21:58:33 +0200 [thread overview]
Message-ID: <51F6C969.7050504@ladisch.de> (raw)
In-Reply-To: <1375119909-24454-1-git-send-email-madeallup.gen@gmail.com>
Ian Dawes wrote:
>
> Signed-off-by: Ian Dawes <madeallup.gen@gmail.com>
The commit message was squashed into the subject line. There's probably
an empty line missing between them.
> +++ b/sound/pci/oxygen/xonar_pcm179x.c
> +static void xonar_xense_init(struct oxygen *chip)
> +{
> + struct xonar_pcm179x *data = chip->model_data;
> +
> + data->generic.ext_power_reg = OXYGEN_GPI_DATA;
> + data->generic.ext_power_int_reg = OXYGEN_GPI_INTERRUPT_MASK;
> + data->generic.ext_power_bit = GPI_EXT_POWER;
> + xonar_init_ext_power(chip);
> + xonar_st_init(chip);
> +}
How much of this is guesswork? :-)
Shouldn't you rather use xonar_stx_init(), which does not try to
configure the nonexistent CS2000 chip?
> + case 0x8428:
> + chip->model = model_xonar_st;
> + chip->model.shortname = "Xonar Xense";
> + chip->model.chip = "AV100";
> + chip->model.init = xonar_xense_init;
> + chip->model.dac_channels_pcm = 8;
> + chip->model.dac_channels_mixer = 8;
When only two channels work, why declaring more?
Regards,
Clemens
next prev parent reply other threads:[~2013-07-29 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 17:45 [PATCH - Preliminary support for Xonar Xense (resubmitAdded support for Xonar Xense. Only speaker out and mic in working Ian Dawes
2013-07-29 19:58 ` Clemens Ladisch [this message]
[not found] ` <20130729212503.04107489@mainbox>
[not found] ` <51F6D131.8040106@ladisch.de>
[not found] ` <20130729214039.6d673367@mainbox>
2013-07-30 6:36 ` Clemens Ladisch
2013-07-30 16:41 ` Ian Dawes
2013-07-30 17:23 ` Clemens Ladisch
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=51F6C969.7050504@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=madeallup.gen@gmail.com \
--cc=patch@alsa-project.org \
/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.