linux-kernel - Re: [alsa-devel] [PATCH] New ASoC Drivers for ADI AD1938 codec

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]

Message-ID: <200906201915.39935.rgetz@blackfin.uclinux.org>
Date:	Sat, 20 Jun 2009 19:15:39 -0400
From:	Robin Getz <rgetz@...ckfin.uclinux.org>
To:	alsa-devel@...a-project.org,
	"Mark Brown" <broonie@...nsource.wolfsonmicro.com>
CC:	"Mike Frysinger" <vapier.adi@...il.com>,
	"Barry Song" <21cnbao@...il.com>, linux-kernel@...r.kernel.org,
	lrg@...mlogic.co.uk
Subject: Re: [alsa-devel] [PATCH] New ASoC Drivers for ADI AD1938 codec

On Fri 19 Jun 2009 07:13, Mark Brown pondered:
> On 19 Jun 2009, at 12:05, Mike Frysinger <vapier.adi@...il.com> wrote:
> > On Fri, Jun 19, 2009 at 06:47, Mark Brown wrote:
> >> This will require that the arch code for any systems with the ad1938
> >> do the setup of the device.
> >
> > so should sound/soc/blackfin/bf5xx-ad1938.c even exist in the first  
> > place ?
> 
> Yes. It is needed in order to specify how things are hooked up on a  
> given board.

This has always kind of bugged me about ASOC - (or maybe it is just my 
ignorance about the architecture decisions that were made).

Any reason why platform/board specific things are in sound/soc/arch rather 
than arch/xxxx/boards - like the majority of drivers?

?

--
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/