From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Jay Bhukhanwala <jaybhukhanwala-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Use cases for fdt_nop_* functions
Date: Wed, 10 Sep 2014 09:12:54 +1000 [thread overview]
Message-ID: <20140909231254.GA19190@voom.redhat.com> (raw)
In-Reply-To: <CAB8QsTBno6L2MFE_JWbkpAH=iBhNzcEQroe0_yyBfYWRG8eCiA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Tue, Sep 09, 2014 at 03:52:51PM -0700, Jay Bhukhanwala wrote:
> What are the use cases for the below functions?
> fdt_nop_property
> fdt_nop_node
>
> How would the fdt_nop_node be any different from setting the status
> property to "disabled" ?
>
> I am suspecting the fdt_nop_node, basically makes the node
> undiscoverable in DT, but I need someone to please confirm the
> assumption.
That's correct. fdt_nop_node and fdt_nop_property are functionally
equivalent to deleting the node or property entirely, however unlike
fdt_del_node() or fdt_del_property() they don't move any other
existing nodes or properties around in the blob.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-09-09 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 22:52 Use cases for fdt_nop_* functions Jay Bhukhanwala
[not found] ` <CAB8QsTBno6L2MFE_JWbkpAH=iBhNzcEQroe0_yyBfYWRG8eCiA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-09 23:12 ` David Gibson [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=20140909231254.GA19190@voom.redhat.com \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jaybhukhanwala-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 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.