linux-kernel - Re: [PATCH 2/2] regulators: max8973: initial DT support

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] [day] [month] [year] [list]

Date:	Tue, 25 Jun 2013 11:35:43 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
Cc:	linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
	Magnus Damm <magnus.damm@...il.com>, linux-sh@...r.kernel.org
Subject: Re: [PATCH 2/2] regulators: max8973: initial DT support

On Fri, Jun 21, 2013 at 04:52:28PM +0200, Guennadi Liakhovetski wrote:
> On Fri, 21 Jun 2013, Mark Brown wrote:

> > A common approach here is just to embed the platform data in the
> > driver data then copy actual platform data in there or parse the device
> > tree bindings (when added) into the structure.  This means that most of
> > the driver can just assume there's platform data which makes life a bit
> > simpler.

> But we can do this later, when we add DT support for those parameters, 
> right?

Sure, but it does make sense to structure the code that way from the
start since it provides simplification.

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