lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 29 Jul 2013 14:05:52 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Mark Brown <broonie@...nel.org>
Cc:	Felipe Tonello <eu@...ipetonello.com>, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org,
	David Henningsson <david.henningsson@...onical.com>,
	Wang Xingchao <xingchao.wang@...ux.intel.com>,
	Jaroslav Kysela <perex@...ex.cz>
Subject: Re: [PATCH 1/4] ALSA: Added jack detection kcontrol support

At Sat, 27 Jul 2013 13:25:24 +0100,
Mark Brown wrote:
> 
> On Fri, Jul 26, 2013 at 04:13:40PM -0700, Felipe Tonello wrote:
> > On Fri, Jul 26, 2013 at 3:48 PM, Mark Brown <broonie@...nel.org> wrote:
> 
> > >> > What I'd expect to happen here is that for multi function jacks we
> > >> > create a control per function if the controls are valid.
> 
> > Ok, so the idea is just to change the control to type integer instead
> > of boolean, right?
> > Because as you say, the user will be able to check the type of jack
> > based on the status value, right?
> 
> It might be more idiomatic and more compatible with userspace to create
> multiple controls for the jack, there was some discussion of this in the
> past I think but I can't remember the result.

I also forget the end result :)

Another option would be to make an enum control, but multiple boolean
controls are easier in the end.  The headset controls of HD-audio are
represented in that way, too (because HD-audio specification can't
tell better).


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ