Use cases for fdt_nop_* functions

Use cases for fdt_nop_* functions

[Jay Bhukhanwala]

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.

Thanks,
Jay.
--
To unsubscribe from this list: send the line "unsubscribe devicetree-compiler" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Use cases for fdt_nop_* functions

[David Gibson]

[-- 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 --]