linux-kernel - Re: Recommendations for a new MFD device driver?

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: <20150206135226.GA29018@finisterre.sirena.org.uk>
Date:	Fri, 6 Feb 2015 14:52:26 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Yingjoe Chen <yingjoe.chen@...iatek.com>
Cc:	Sascha Hauer <s.hauer@...gutronix.de>, eddie.huang@...iatek.com,
	Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: Recommendations for a new MFD device driver?

On Fri, Feb 06, 2015 at 08:55:12PM +0800, Yingjoe Chen wrote:

> I think we should create a dtsi file, say mt6397.dtsi, the regulator
> device nodes are already too much to duplicate into every board using
> mt6397.

Please bear in mind that the regulator bindings are all about what is
being done to connect the PMIC to the rest of the system on a given
board; this means that it is almost always a bad idea to have a generic
include file for the PMIC since while many boards may be similar other
boards may differ and it's potentially unsafe to try to handle things
generally.  

It can be a good idea to have a .dsti file for the common elements of a
widely used reference design but that's a different thing.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)