linux-kernel - Re: [PATCH v2] soc/sh: Fix I2C dependency for SND_FSI_AK4642 and SND_FSI

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: <20100616074947.GC29614@linux-sh.org>
Date:	Wed, 16 Jun 2010 16:49:48 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Peter Huewe <PeterHuewe@....de>,
	Liam Girdwood <lrg@...mlogic.co.uk>, linux-sh@...r.kernel.org,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
	Kuninori Morimoto <morimoto.kuninori@...esas.com>,
	Guennadi Liakhovetski <g.liakhovetski@....de>,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] soc/sh: Fix I2C dependency for SND_FSI_AK4642 and SND_FSI_DA7210

On Wed, Jun 16, 2010 at 08:43:33AM +0100, Mark Brown wrote:
> On 16 Jun 2010, at 04:54, Paul Mundt wrote:
> 
> > On Tue, Jun 15, 2010 at 05:38:55PM +0200, Peter Huewe wrote:
> >> The config option SND_FSI_AK4642 selects SND_SOC_AK4642 which in turn
> >> enables the compilation of ak4642.c - however this codec uses I2C to
> >> communicate with the HW.
> >> Same applies to DA7210.
> 
> > It uses I2C, but it doesn't matter which I2C master it's interfaced with.
> > A simple depends on I2C will suffice for this purpose just fine.
> 
> Since these are board specific drivers they know which I2C controller they are
> hooked up to and so can usefully depend on a specific controller - without the
> correct controller driver they will not function.

I don't really mind one way or the other. Having it depend on the
controller is fine, but it's not really much of a stretch to expect it to
show up on other boards with other controllers as well.

Very few SH CPUs use the same controller, so in this case it's really
more the exception than the norm. As soon as another board takes up one
of these blocks then we're forced to either switch to an I2C depends or
start making a dependency list for multiple controllers. It's the desire
to avoid the latter why I generally prefer the former, but again, I'm
fairly impartial regardless.
--
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/