From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Frank Rowand <frowand.list@gmail.com>
Cc: Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] sysfs, device-tree: aid for debugging device tree boot problems
Date: Wed, 23 Apr 2014 16:45:01 -0700 [thread overview]
Message-ID: <20140423234501.GA17827@kroah.com> (raw)
In-Reply-To: <53584277.7000405@gmail.com>
On Wed, Apr 23, 2014 at 03:45:11PM -0700, Frank Rowand wrote:
> >> 3) To find list of device tree nodes with a bound driver:
> >>
> >> # output is: driver_name node_full_path
> >> #
> >> cd /proc/device-tree
> >> for k in `find . -name %driver_name` ; do
> >> echo `cat ${k}` `echo ${k} | sed -e 's|./||' -e 's|/%driver_name$||'`
> >> done | sort
> >
> > If we take this patch, these examples should be somewhere in the
> > documentation to make it easy for others.
>
> That is a good idea. I'll package up the equivalent shell code from
> Grant's email. Any suggestions on location?
>
> scripts/debug/devicetree/
> scripts/devicetree/debug/
> Documentation/devicetree/scripts/
tools/ is probably the best place for them, or in Documentation/, either
would work.
thanks,
greg k-h
prev parent reply other threads:[~2014-04-23 23:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 1:25 [PATCH] sysfs, device-tree: aid for debugging device tree boot problems Frank Rowand
2014-04-23 1:25 ` Frank Rowand
[not found] ` <53571685.5060403-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-04-23 3:20 ` Greg Kroah-Hartman
2014-04-23 3:20 ` Greg Kroah-Hartman
[not found] ` <20140423032044.GA26233-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2014-04-23 11:54 ` Grant Likely
2014-04-23 11:54 ` Grant Likely
2014-04-23 22:48 ` Frank Rowand
2014-04-28 15:09 ` Grant Likely
2014-04-23 22:45 ` Frank Rowand
2014-04-23 22:45 ` Frank Rowand
2014-04-23 23:45 ` Greg Kroah-Hartman [this message]
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=20140423234501.GA17827@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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.