From: Stuart Yoder <b08248-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Kevin Wilson <wkevils-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: Displaying procs device tree properties
Date: Fri, 11 May 2012 15:15:04 -0500 [thread overview]
Message-ID: <CALRxmdAdj-0rdMoMYv_8z0bAhr8TVsThpPGosW7Z0sAsQcUk5w@mail.gmail.com> (raw)
In-Reply-To: <CAGXs5wXYwBAVjcUE8c8m7L0URR_CXNFQnHPWpzRPug_an0ij1g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, May 8, 2012 at 10:32 AM, Kevin Wilson <wkevils-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Hi,
> I have added some device tree properties for testing device tree in a
> kernel module.
> Some are with regular, generic device tree names (like "interrupts", "reg")
> and some are with my unique names which are not inherent to generic device tree.
> I do have success with reading the correct values for my entries with OF
> (OpenFirmware) API. (like with of of_get_property() and of_find_property() and
> the other of_... methods.
>
> I had set CONFIG_PROC_DEVICETREE to y.
>
> When I try to print properties from under the folder that was
> generated by my dts, from under /proc/device-tree/mysoc..., (by "cat" command).
> some of them are shown and some are not. There are cases in which I see garbage.
>
> The permission of **all** properties under
> proc/device-tree/mysoc... is
> -r--r--r--
>
> It **does** show "compatible" properties
> It **does** show "device_type" properties
> It **does** show "name" properties
> It **does not** show "interrupts" properties.
> It **does not** show other properties
> there are cases it shows garbage , like "reg" properties
>
> Is there a way to enable that it will display all properties which I
> added ?
Try using dtc:
dtc -I fs -O dts /proc/device-tree
The "garbage" is there because what you are seeing is the actual
binary values, not the ascii values.
Stuart
prev parent reply other threads:[~2012-05-11 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 15:32 Displaying procs device tree properties Kevin Wilson
[not found] ` <CAGXs5wXYwBAVjcUE8c8m7L0URR_CXNFQnHPWpzRPug_an0ij1g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-05-11 20:15 ` Stuart Yoder [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=CALRxmdAdj-0rdMoMYv_8z0bAhr8TVsThpPGosW7Z0sAsQcUk5w@mail.gmail.com \
--to=b08248-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=wkevils-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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).