linux-kernel - Re: [PATCH] Add SoundCard driver for OKI SEMICONDUCTOR ML7213 IOH

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110709013441.GB25165@sirena.org.uk>
Date:	Sat, 9 Jul 2011 02:34:41 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	Toshiharu Okada <toshiharu-linux@....okisemi.com>, perex@...ex.cz,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
	qi.wang@...el.com, yong.y.wang@...el.com, joel.clark@...el.com,
	kok.howg.ewe@...el.com, tomoya-linux@....okisemi.com
Subject: Re: [PATCH] Add SoundCard driver for OKI SEMICONDUCTOR ML7213 IOH

On Thu, Jul 07, 2011 at 06:38:33PM +0200, Takashi Iwai wrote:

> It's not clear what you mean exactly as "unfixed", but in general, the
> decision rather depends on the usage of the device.  If it's designed
> for a use as a desktop PC component (such as a PCI card or
> onboard-audio on PC), it'd make sense to implement as a stand-alone,
> self-contained driver.

> OTOH, if it's targeted mainly for embedded area, ASoC is the right
> answer.  It's more modularized, and can be more flexibly configured in
> the end.

I'd say it depends rather more on the physical system design.  If there
are a bunch of separate chips which are interacted with separately by
software then ASoC makes sense, if the card is one logical object to
hardware a vanilla ALSA driver probably does.
--
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/