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] [day] [month] [year] [list]
Message-ID: <4F8E6494.60206@ladisch.de>
Date:	Wed, 18 Apr 2012 08:52:04 +0200
From:	Clemens Ladisch <clemens@...isch.de>
To:	Takashi Iwai <tiwai@...e.de>
CC:	Ondrej Zary <linux@...nbow-software.org>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [alsa-devel] [PATCH 3/4] Add Wolfson Microelectronics WM8776
 codec ALSA driver

Takashi Iwai wrote:
> Ondrej Zary wrote:
>> On Tuesday 17 April 2012 21:12:33 you wrote:
>>> Ondrej Zary wrote:
>>>> Xonar (oxygen) has a private version of these drivers too. It could be
>>>> converted to use common code instead.
>>>
>>> Hm, only if the generated controls do match with your case,..
>>> It's case by case, especally if there is only one another candidate.
>>
>> Control names can be changed (and also disabled) by the driver. In fact,
>> psc724 does exactly this as is needs the WM8776 controls to be named
>> as "front" and WM8766 as "rear".
>> I don't see any problem if something needs to be changed for this code to be
>> used by Xonar (or some other driver).
>
> OK, it depends on Clemens, whether the shared code is preferred (and
> maintainable).

I've always planned to move the Xonar driver to the ASoC framework.
(I didn't at first because ASoC didn't support multiple codecs then.)
The only problem is finding time to do this ...

Sharing the code between ice1712 and xonar might be a first step.


Regards,
Clemens
--
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