devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>, Benoit Cousson <b-cousson@ti.com>,
	linux-kernel@vger.kernel.org,
	devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH] Input: twl6040-vibra: Update for device tree support
Date: Wed, 16 May 2012 12:35:46 -0700	[thread overview]
Message-ID: <20120516193546.GA15920@core.coreip.homeip.net> (raw)
In-Reply-To: <1337167186-8535-1-git-send-email-peter.ujfalusi@ti.com>

Hi Peter,

On Wed, May 16, 2012 at 02:19:46PM +0300, Peter Ujfalusi wrote:
> The twl6040 DT support implementation has been changed from the originally
> planned.
> None of the child devices going to have compatible_of property which means
> that the child devices of twl6040 will be created as traditional MFD devices.
> The mfd core driver will decide (based on the DT blob) to create a device
> for the twl6040-vibra or not. If the DT blob has 'vibra' section the device
> will be created without pdata.
> In this case the vibra driver will reach up to the parent node to get the
> needed properties.

So in this case why don't you have parent parse all DT data and
construct instance of pdata for vibra driver to consume?

Thanks.

-- 
Dmitry

  reply	other threads:[~2012-05-16 19:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16 11:19 [PATCH] Input: twl6040-vibra: Update for device tree support Peter Ujfalusi
2012-05-16 19:35 ` Dmitry Torokhov [this message]
2012-05-16 19:55   ` Ujfalusi, Peter
2012-05-17  0:59     ` Dmitry Torokhov
     [not found]     ` <CAPo=G1zf1XJcoKgCxMn3X09T0LOUG-9aw3iopqC7OPqcuc5hcQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-21  5:32       ` Dmitry Torokhov
     [not found]         ` <20120521053159.GA30285-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2012-05-21  9:45           ` Ujfalusi, Peter

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=20120516193546.GA15920@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=b-cousson@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=peter.ujfalusi@ti.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;
as well as URLs for NNTP newsgroup(s).