public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Ondrej Zary <linux@rainbow-software.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH 3/4] Add Wolfson Microelectronics WM8776 codec ALSA driver
Date: Wed, 18 Apr 2012 08:52:04 +0200	[thread overview]
Message-ID: <4F8E6494.60206@ladisch.de> (raw)
In-Reply-To: <s5hr4vloa8g.wl%tiwai@suse.de>

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

  reply	other threads:[~2012-04-18  6:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 21:18 [RFC PATCH 0/4] snd-ice1712: Add Philips PSC724 Ultimate Edge Ondrej Zary
2012-04-16 21:18 ` [PATCH 1/4] snd-ice1712: add chip_exit callback Ondrej Zary
2012-04-16 21:18 ` [PATCH 2/4] Add Wolfson Microelectronics WM8766 codec ALSA driver Ondrej Zary
2012-04-17 14:59   ` Mark Brown
2012-04-17 16:35     ` Ondrej Zary
2012-04-17 16:54       ` Mark Brown
2012-04-16 21:18 ` [PATCH 3/4] Add Wolfson Microelectronics WM8776 " Ondrej Zary
2012-04-17 15:02   ` Mark Brown
2012-04-17 16:13     ` Ondrej Zary
2012-04-17 16:18       ` Mark Brown
2012-04-17 16:32         ` [alsa-devel] " Takashi Iwai
2012-04-17 16:50           ` Mark Brown
2012-04-17 16:52             ` Takashi Iwai
2012-04-17 17:04               ` Mark Brown
2012-04-17 18:06                 ` Takashi Iwai
2012-04-17 18:15                   ` Ondrej Zary
2012-04-17 18:22                     ` Mark Brown
2012-04-17 19:14                       ` Takashi Iwai
2012-04-17 19:43                         ` Mark Brown
2012-04-17 19:12                     ` Takashi Iwai
2012-04-17 21:07                       ` Ondrej Zary
2012-04-18  5:54                         ` Takashi Iwai
2012-04-18  6:52                           ` Clemens Ladisch [this message]
2012-04-16 21:18 ` [PATCH 4/4] snd-ice1712: Add Philips PSC724 Ultimate Edge Ondrej Zary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F8E6494.60206@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rainbow-software.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox