All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Longerbeam <steve_longerbeam@mentor.com>
To: DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: of_parse_phandle: "could not find phandle"
Date: Sun, 5 Apr 2015 16:14:36 -0700	[thread overview]
Message-ID: <5521C1DC.3020304@mentor.com> (raw)

Hi all,

If --strip-disabled option is passed to dtc, of_parse_phandle() emits
this error message for disabled nodes.

For example, imx_drm_platform_probe() will generate the messages
when it walks the list of endpoints to display bridge nodes that have
been left disabled for a particular target.

Given that there can now be missing phandles in a dtb due to --strip-disabled
option, and the use of the option would be the only reason there would be a
missing phandle in a successfully compiled dtb AFAIK, should this error
message be converted to pr_debug()?

Thanks,
Steve

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-04-05 23:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05 23:14 Steve Longerbeam [this message]
2015-04-06 17:10 ` of_parse_phandle: "could not find phandle" Steve Longerbeam
  -- strict thread matches above, loose matches on Subject: below --
2015-04-05 22:47 Steve Longerbeam

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=5521C1DC.3020304@mentor.com \
    --to=steve_longerbeam@mentor.com \
    --cc=dri-devel@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.