From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: pcm512x driver: Mixer control naming issue Date: Mon, 16 Mar 2015 12:59:14 +0100 Message-ID: References: <5500DE5B.2020401@hmbedded.co.uk> <5502DAE1.30609@hmbedded.co.uk> <20150313182729.GE28806@sirena.org.uk> <55060771.7060200@hmbedded.co.uk> <20150316113845.GM28806@sirena.org.uk> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id D03F22605D3 for ; Mon, 16 Mar 2015 12:59:14 +0100 (CET) In-Reply-To: <20150316113845.GM28806@sirena.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: Mark Brown Cc: alsa-devel@alsa-project.org, Howard Mitchell , Gordon Garrity List-Id: alsa-devel@alsa-project.org At Mon, 16 Mar 2015 11:38:45 +0000, Mark Brown wrote: > > > default for "Analogue Playback Volume" may well be added to "alsactl > > restore" and then we end up back in the same situation. How about defining a > > prefix that is documented as saying that a default should not be used if > > there's nothing in asound.state for that control? > > Really the problem here is using asound.state - it's far too dumb a > means of controlling random cards, and attempting to change it is most > likely going to break something else. alsactl tries to initialize some common controls, and the question is how common is common. > Any attempt to introduce a > default for analogue control will inevitably result in problems on cards > that currently work fine with digital/default control unless those are > changed which would then cause problems for things without the analogue > control. It's why I raised an item about standard control names every year in the audio meeting :) Takashi