devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Rob Herring <robherring2@gmail.com>,
	"Cousson, Benoit" <b-cousson@ti.com>
Cc: linux-omap@vger.kernel.org, Balaji T K <balajitk@ti.com>,
	devicetree-discuss@lists.ozlabs.org, Chris Ball <cjb@laptop.org>,
	bigeasy@linutronix.de
Subject: Re: [RFC] dt: export of_have_populated_dt
Date: Tue, 10 Apr 2012 14:33:57 -0600	[thread overview]
Message-ID: <20120410203357.D86323E0D65@localhost> (raw)
In-Reply-To: <4F846BDB.8020805@gmail.com>

On Tue, 10 Apr 2012 12:20:27 -0500, Rob Herring <robherring2@gmail.com> wrote:
> On 04/10/2012 11:29 AM, Cousson, Benoit wrote:
> > Hi Chris,
> > 
> > On 4/10/2012 6:21 PM, Chris Ball wrote:
> >> Hi,
> >>
> >> On Tue, Apr 10 2012, Cousson, Benoit wrote:
> >>> Hi Balaji,
> >>>
> >>> On 4/10/2012 5:11 PM, Balaji T K wrote:
> >>>> If of_have_populated_dt is called from module, build fails with
> >>>> "allnodes"
> >>>> undefined error, so remove inline and export of_have_populated_dt.
> >>>
> >>> Is this function really called from the MMC driver?
> >>
> >> ~/git/linux % git grep of_have_populated_dt drivers/
> >> drivers/gpio/gpio-samsung.c:    if (!of_have_populated_dt())
> >> drivers/mmc/host/omap_hsmmc.c:  if (of_have_populated_dt()&&  !vdd)
> >> drivers/mmc/host/omap_hsmmc.c:                  
> >> (!of_have_populated_dt())) {
> > 
> > Gosh, twice... I should be in a wrong branch :-(
> > 
> > Then the next question to Rob...
> > 
> > Rob,
> > Does it make sense to use that in the driver? So far I was using that
> > only in the arch code to make the difference between the DT boot and the
> > non-DT boot.
> > 
> > I guess that a driver should rely on of_match_device or non-NULL
> > device_node to figure out that?
> > 
> 
> Agreed. of_match_device or device_node ptr check is the right approach.

Good; I can safely ignore this patch.  :-)

g.


  reply	other threads:[~2012-04-10 20:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 15:11 [RFC] dt: export of_have_populated_dt Balaji T K
2012-04-10 16:19 ` Cousson, Benoit
     [not found]   ` <4F845D99.7020705-l0cyMroinI0@public.gmane.org>
2012-04-10 16:21     ` Chris Ball
2012-04-10 16:29       ` Cousson, Benoit
2012-04-10 17:20         ` Rob Herring
2012-04-10 20:33           ` Grant Likely [this message]
2012-04-11  4:16           ` Rajendra Nayak
     [not found] ` <1334070672-11252-1-git-send-email-balajitk-l0cyMroinI0@public.gmane.org>
2012-04-10 17:36   ` Sebastian Andrzej Siewior
2012-04-11  4:18 ` Rajendra Nayak

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=20120410203357.D86323E0D65@localhost \
    --to=grant.likely@secretlab.ca \
    --cc=b-cousson@ti.com \
    --cc=balajitk@ti.com \
    --cc=bigeasy@linutronix.de \
    --cc=cjb@laptop.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robherring2@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;
as well as URLs for NNTP newsgroup(s).