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]
Date:	Tue, 8 Feb 2011 13:08:23 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Lars-Peter Clausen <lars@...afoo.de>
Cc:	Liam Girdwood <lrg@...mlogic.co.uk>, alsa-devel@...a-project.org,
	linux-kernel@...r.kernel.org, Marcel Holtmann <marcel@...tmann.org>
Subject: Re: Adding bluetooth PCM interface support to ASoC (Was: Re:
 [PATCH 6/7] ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration)

On Mon, Feb 07, 2011 at 11:55:22PM +0100, Lars-Peter Clausen wrote:

> I did some research on the topic and it seems that this is a pretty common
> setup in embedded devices.

Yes, this is a totally vanilla setup except that for modern hardware the
baseband is connected digitally also.

> But the bluetooth audio support seems to be entirely written in userspace. The
> in-kernel bluetooth drivers in general seem only to provide a common interface
> to the underlying hardware and all of the higher level functionality seems to
> be implemented in userspace.
> So right now I have no idea where to start if one wanted to add a ASoC driver
> which did the bt-dai configuration.

The obvious starting point would seem to be to provide a driver which
allows userspace to tell the kernel about configuration changes - that's
what we're doing at the minute for the trivial case where the hardware
doesn't change configuration.  We could then look at pushing more of the
code into the kernel if that made sense.
--
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