Is there a convention for mapping codec vendor's register::bit names to alsa control names?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Title: Is there a convention for mapping codec vendor's register::bit names to alsa control names?

I have some improvements to the VIA 1617a support submitted a few weeks ago by daniel jacobowitz (they are in 1.0.14rc2).

I have added 4 new controls, 3 of which are required to support enabling VIA's 'Smart51' for the 1617a:


static const struct snd_kcontrol_new snd_ac97_controls_vt1617a[] = {
  AC97_SINGLE("Center/LFE Exch",   0x5a,  8, 1, 0),
/* these bits form a matrix that allows for the limited configuration of
 * outputs and inputs to enable surround sound input
  AC97_SINGLE("Microphone Select", 0x20,  8, 1, 0),
  AC97_SINGLE("Smart 5.1 Switch",  0x7a, 15, 1, 0),
  AC97_SINGLE("Smart 5.1 Enable",  0x7a, 14, 1, 0)
};

These are the names that Uncle Via's hard working engineers have assigned to these bits in their released documentation but surfacing these names in the ui looks to me to be a usability nightmare :-(

To wit; enabling surround sound on a board that only has 3 jacks requires setting

   "Microphone Select" to 0
   "Smart 5.1 Switch"  to 1
   "Smart 5.1 Enable"  to 1

*and* one set the existing "Alternate Level to Surround Out" to 0


This is super-duper non obvious in alsamixer.

Hell, i'd just *coded* the damn thing and i had to poke alsamixer a few times to get it right.


So, what's the convention on things like this?

As a developer, i'd prefer that things match the chip docs so i can figure out what's going on in the code (thus my previous on-list gripes about register naming macros not matching the AC97 standard).

As a user, i'd prefer that it be easy to figure out what the hell i am supposed to do to get the hardware to do what i want?


What to do?

tnx!

johnu

As a user, i'd prefer that thing



However,

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-devel

[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux