From: Pavel Hofman <pavel.hofman@ivitera.com>
To: ALSA development <alsa-devel@alsa-project.org>
Subject: eeprom params for ice1724 module - recommendation?
Date: Wed, 04 Jan 2012 21:37:46 +0100 [thread overview]
Message-ID: <4F04B89A.1060801@ivitera.com> (raw)
Hi,
I have a generic ice1724 card ooAoo SQ210a (e.g.
http://forum.lowyat.net/topic/851912/all ). The card has identical PCI
identification with Chaintec AV710, no DAC controls (the DAC is
hardwired in pin-control mode with no GPIOs attached), no identification
string in eeprom and of course incorrect eeprom values.
Since the PCI ids overlap with the Chaintec, I cannot define correct
eeprom_data for this specific card in the driver. Furthermore I would
not be surprised if the other ooAoo cards with different setups shared
the same PCI ids.
I can skip the Chaintec config by specifying an unknown model in
snd-ice1724 param, e.g.
modprobe snd-ice1724 model=aooa
I would like to be able to specify correct eeprom values for the model
too. That would be simple by adding several new module params -
eeep2-sysconf, eeep2-aclink, eeep2-spdif etc.
However, I have another ice1724 card properly supported by the driver
(Infrasonic Quartet). I can use
modprobe snd-ice1724 model=quartet,aooa
and everything works correctly. But if I wanted to define eeep2-xxx
params for the aooa, I would have to define the same params for the
quartet too which I find superfluous since they are already correctly in
the driver.
Or I could use a string type instead of int and use something like
eeep2-sysconf=default,47
Or I could "encode" the eeep2 params into the model name, such as
modprobe snd-ice1724 model="quartet,aooa(eeep2-sysconf=47;eeep2-spdif=20)"
Please which version would you recommend (i.e. accept as a patch)?
Thank you for your expert advice.
Best regards,
Pavel.
next reply other threads:[~2012-01-04 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 20:37 Pavel Hofman [this message]
2012-01-04 22:30 ` eeprom params for ice1724 module - recommendation? Pavel Hofman
2012-01-05 20:58 ` eeprom params for ice1724 module Pavel Hofman
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=4F04B89A.1060801@ivitera.com \
--to=pavel.hofman@ivitera.com \
--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 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.