From: Takashi Iwai <tiwai@suse.de>
To: David Shust <dshust@bemail.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: YMF753 AC '97 Module Options
Date: Wed, 25 Sep 2002 13:20:47 +0200 [thread overview]
Message-ID: <s5h65wunwmo.wl@alsa2.suse.de> (raw)
In-Reply-To: <200209241744.g8OHiw010210@mail18.bigmailbox.com>
At Tue, 24 Sep 2002 10:44:58 -0700,
David Shust wrote:
>
> >Takashi Iwai wrote
> >the patch looks good except for the module options for spdif.
> >since ac97_codec is a generic module, it's better to avoid
> >such device specific options. isn't it detectable?
>
> If the Yamaha YMF753 spec provided a way to autodetect which pin was
> being used for S/PDIF ouput, I'd use it.
ok. then user must choose.
> The alternative to providing a module parameter via insmod would be
> to provide a mixer control, where one would have the choice of
> disabling S/PDIF output, or selecting pin 43 or 48. My instincts
> told me that it made more sense having this as a module parameter,
> as once one has determined which pin is being used, why would one
> ever change that value. I felt the same about the parameter for
> adding the delay after DAC startup in order to avoid missing
> audio. I could make both items mixer controls if both Jaroslav and
> Takashi feel it is better. Could you both please respond?
the problem is, as mentioned in my last mail, ac97-codec is a generic
module which is shared among drivers.
for example, what happens if you have two cards with the ymf753?
so, if this parameter is implemented as a module option, then it
should go into the card module and store the value in ac97 struct,
e.g. ac97->spec.ymf753.spdif_out_pin and spdif_delay.
or, as you wrote above, implement this as a control switch.
it's not too bad, because with this switch you can disable spdif
output on the fly, too.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
prev parent reply other threads:[~2002-09-25 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 17:44 YMF753 AC '97 Module Options David Shust
2002-09-25 11:20 ` Takashi Iwai [this message]
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=s5h65wunwmo.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dshust@bemail.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.