From: Mark Brown <broonie@kernel.org>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/2] regulators: max8973: initial DT support
Date: Tue, 25 Jun 2013 11:35:43 +0100 [thread overview]
Message-ID: <20130625103543.GC27646@sirena.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1306211651120.27277@axis700.grange>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-25 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 6:30 [PATCH 1/2] regulators: max8973: fix multiple instance support Guennadi Liakhovetski
2013-06-21 6:30 ` [PATCH 2/2] regulators: max8973: initial DT support Guennadi Liakhovetski
2013-06-21 14:44 ` Mark Brown
2013-06-21 14:52 ` Guennadi Liakhovetski
2013-06-25 10:35 ` Mark Brown [this message]
2013-06-21 10:01 ` [PATCH 1/2] regulators: max8973: fix multiple instance support Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130625103543.GC27646@sirena.org.uk \
--to=broonie@kernel.org \
--cc=g.liakhovetski@gmx.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®