linux-kernel - Re: [PATCH] clock: max77686: Add driver for Maxim 77686 32KHz crystal oscillator

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: <201206020250.21967.arnd@arndb.de>
Date:	Sat, 2 Jun 2012 02:50:21 +0000
From:	Arnd Bergmann <arnd@...db.de>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Jonghwa Lee <jonghwa3.lee@...sung.com>,
	linux-kernel@...r.kernel.org,
	Mike Turquette <mturquette@...aro.org>,
	H Hartley Sweeten <hsweetn@...ionengravers.com>,
	MyungJoo Ham <myungjoo.ham@...sung.com>,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: [PATCH] clock: max77686: Add driver for Maxim 77686 32KHz crystal oscillator

On Friday 01 June 2012, Mark Brown wrote:
> On Fri, Jun 01, 2012 at 04:13:33PM +0000, Arnd Bergmann wrote:
> 
> > You should also have an of_device_id table so you can match this driver from
> > device tree definitions.
> 
> There has been...  some discussion on the value of doing this for MFD
> cells where the MFD cell has no reuse capability (eg, when the driver
> has very little abstraction from the top level chip binding) since we
> don't really get anything from the abstraction if the driver can't be
> reused and may limit ourselves (and others) in future.

Ok, makes sense.

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