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

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

Message-Id: <B480F429-3819-4086-8576-F0A1B0FC093C@opensource.wolfsonmicro.com>
Date:	Wed, 16 Jun 2010 08:58:41 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Paul Mundt <lethal@...ux-sh.org>
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 16 Jun 2010, at 08:49, Paul Mundt wrote:
> On Wed, Jun 16, 2010 at 08:43:33AM +0100, Mark Brown wrote:

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

This is the driver for the board itself and its wiring - it's not a chip driver, it's
the driver that says how the chips on a given board are connected. For new
boards I'd expect you'd end up with a new driver.--
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/