Bug 99631 - PCM512x driver uses non-standard control names - breaks apps
Summary: PCM512x driver uses non-standard control names - breaks apps
Status: RESOLVED WILL_NOT_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jaroslav Kysela
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-06-08 11:55 UTC by andrum99
Modified: 2015-06-08 12:05 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.18.11+, 4.x
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments

Description andrum99 2015-06-08 11:55:42 UTC
Recently there was a change to the PCM5122 driver that changed the mixer control names. The new control names are non-standard (per the documentation in the Linux kernel at https://www.kernel.org/doc/Documentation/sound/alsa/ControlNames.txt) and cause several applications problems, including mpd and Kodi. Applications are now unable to see the master volume control on PCM5122-based cards (for example the HifiBerry DAC+). The master volume control is now named 'Digital Playback Volume', which is on the deprecated list. It should be renamed 'PCM Playback Volume'. Also, there are two controls that have the source name as 'Analogue'. The word 'analogue' does not appear anyway in the documentation for control names. ('Analog' does but only in reference to loopback controls). These two controls also need to be renamed to something compliant with the standard.
Comment 1 Takashi Iwai 2015-06-08 12:05:04 UTC
The ASoC drivers tend to follow own rules about control names, and we don't force the standard control names.  And renaming again shall result in another regressions for applications that are using the current name.  So, the rename is no-go, sorry.

This has been discussed a couple of times in the last meetings, but no clear 
consensus met, so far.  The definition of the standard control names is more or less obsoleted nowadays.

For resolving the Master volume problem, user-space should use UCM if available.

Note You need to log in before you can comment on or make changes to this bug.