Lines Matching refs:property
30 4) Note about node and property names and character set
48 1) interrupts property
49 2) interrupt-parent property
53 VIII - Specifying device power management information (sleep property)
81 "name" property is now automatically
87 property data to 4 bytes. Since tokens are
89 required alignment between property size
90 and property data. The old style variable
456 should match the content of the "reg" property of the CPU node in
520 nodes, each node having two or more named properties. A property can
527 property of type "name" in the node property list whose value is a
537 The unit name doesn't exist as a property per-se but is included in
553 a name property either if you are using version 3 or earlier of the
560 is) is also required to have a "compatible" property indicating the
564 Finally, every node that can be referenced from a property in another
566 property. Real Open Firmware implementations provide a unique
574 The "phandle" property is a 32-bit value that uniquely
577 requirement is that every node for which you provide that property has
632 The /cpus/PowerPC,970@0/64-bit property is an example of a
633 property without a value. All other properties have a value. The
655 * for each property:
657 * 32-bit value of property value size in bytes (or 0 if no
659 * 32-bit value of offset in string block of property name
660 * property value data if any
669 NOTE: The above definition requires that all property definitions for
679 In order to save space, property names, which are generally redundant,
681 whole bunch of zero terminated strings for all property names
682 concatenated together. The device-tree property definitions in the
741 then, to provide a separate "assigned-addresses" property that
752 The "reg" property only defines addresses and sizes (if #size-cells is
755 addresses), all buses must contain a "ranges" property. If the
756 "ranges" property is missing at a given level, it's assumed that
758 parent bus. The format of the "ranges" property for a bus is a list
777 Alternatively, the "ranges" property may be empty, indicating that the
786 node. The format of a "compatible" property is a list of concatenated
796 to use the actual device name for the "name" property, it's nowadays
799 controllers are named "ethernet", an additional "model" property
800 defining precisely the chip type/model, and "compatible" property
803 restriction on the "name" property; it is simply considered good
807 Note also that the new format version 16 makes the "name" property
813 4) Note about node and property names and character set
820 allow uppercase characters 'A' to 'Z' (property names should be
822 irrelevant here). Additionally, node and property names should always
826 The maximum number of characters for both nodes and property names
828 a unit name (the pure "name" property), it doesn't include the unit
850 compatible property followed by an entry that represents the SoC
855 thing. It is recommended that if you add any "custom" property whose
881 property to identify the specific cpu core.
913 in Hz. A new property will be defined for 64-bit values, but if
915 for the above, the common code doesn't use that property, but
923 You are welcome to add any property you find relevant to your board,
926 lines in there as a "soft-reset" property since they start secondary
934 node with all memory ranges in its reg property, or you can create
943 - reg : This property contains all the physical memory ranges of
949 have a "reg" property here that looks like:
984 (Note: a practice that is now obsolete was to include a property
1011 - reg : This property defines the address and size of the
1015 "reg" property should match the unit address of the SOC node.
1115 property1 = "string_value"; /* define a property containing a 0
1119 property2 = <0x1234abcd>; /* define a property containing a
1124 /* define a property containing 3
1129 /* define a property whose content is
1138 childprop = "hello\n"; /* define a property "childprop" of
1155 you can point to a property content and change it easily from whatever
1219 address property represents the address offset for this device's
1221 address space is defined by the "ranges" property in the top-level soc
1222 node. The "reg" property for each node that exists directly under the
1263 1) interrupts property
1271 property. The interrupt property value is an arbitrary number of
1278 its #interrupt-cells property the number of 32-bit cells
1286 property.
1291 2) interrupt-parent property
1294 The interrupt-parent property is specified to define an explicit
1299 If the interrupt-parent property is not defined for a node, its
1334 VIII - Specifying Device Power Management Information (sleep property)
1339 this information is more complicated than a cell-index property can
1341 may contain a "sleep" property which describes these connections.
1343 The sleep property consists of one or more sleep resources, each of
1360 property. If the clock domain is shared among devices that cannot be
1375 and DMA addresses. The "dma-ranges" property is intended to be used
1379 coherent DMA operations. The "dma-coherent" property is intended to be used
1383 Optional property:
1387 The dma-ranges property is used to describe the direct memory access (DMA)
1395 Optional property: