Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Washington <denisw@online.de>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/2] Make ASUS Xonar U3 S/PDIF channel	accessible
Date: Tue, 11 Dec 2012 19:24:55 +0100	[thread overview]
Message-ID: <50C77A77.7060805@online.de> (raw)
In-Reply-To: <s5hk3solstc.wl%tiwai@suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 2051 bytes --]

Am 11.12.2012 12:41, schrieb Takashi Iwai:
> At Tue, 11 Dec 2012 11:37:26 +0100,
> Denis Washington wrote:
>>
>> Hello,
>>
>> This is my first ALSA patch ever (in fact, also my first kernel patch
>> and my first e-mail to this mailing list); as such, I'm sorry when I did
>> something wrong and/or didn't follow the procedure properly. I hope you
>> can forgive me.
>>
>> I recently bought an ASUS Xonar U3 USB audio card. It general it works
>> well with Linux, but unfortunately, it's PCM output channel is unusable
>> for headphones because it allows virtually no volume control (maximum
>> loudness is already reach at a volume level of 2 or 3). The card does
>> also have a digital (S/PDIF) output channel, which however isn't
>> switched on by the Linux USB audio driver:
>>
>> http://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg28970.html
>>
>> When I boot into Windows (where the ASUS driver seemingly enables the
>> channel) and then reboot into Linux, I can use this channel and control
>> volume as expected. It's just this turning on of S/PDIF which is
>> missing, as suggested by the alsa-user thread linked to above.
>>
>> The patchset that follows enables S/PDIF on the Xonar U3 by using the
>> (seemingly compatible) mixer quirks code as for the U1, just as done and
>> tested by the initiator of the alsa-user thread, together with a very
>> minor cleanup (renaming internal xonar_u1_* identifiers to just
>> xonar_u_*). The change seems to work well (tested with the 3.7.0 Ubuntu
>> kernel as found in today' daily version).
>
> Thanks for patches.
>
> I think the rename of xonar_u1_* isn't needed.  What we need is rather
> giving more comments there, that it's for both U1 and U3.

Yes, that would be useful. I don't know if I'm qualified to write a 
useful comment for this, though.

> In anyway, could you resubmit with your sign-off?
> Put a line like
> 	Signed-of-by: Your Name <foo@bar.com>
> in the tail of the change log text.

OK, no problem.

Regards,
Denis


[-- Attachment #1.2: S/MIME Kryptografische Unterschrift --]
[-- Type: application/pkcs7-signature, Size: 4453 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2012-12-11 18:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 10:37 [PATCH 0/2] Make ASUS Xonar U3 S/PDIF channel accessible Denis Washington
2012-12-11 11:41 ` Takashi Iwai
2012-12-11 18:24   ` Denis Washington [this message]
2012-12-13  6:40     ` Denis Washington
2012-12-13  6:46       ` 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=50C77A77.7060805@online.de \
    --to=denisw@online.de \
    --cc=alsa-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox