Lines Matching full:use

24 - DO use node names matching the class of the device. Many standard names are
34 - DON'T treat device node names as a stable ABI, but instead use phandles or
38 - DON'T use 'syscon' alone without a specific compatible string. A 'syscon'
42 - DON'T use 'simple-mfd' compatible for non-trivial devices, where children
53    - DON'T use wildcards or device-family names in compatible strings.
55    - DO use fallback compatibles when devices are the same as or a superset of
60    - DO use a SoC-specific compatible for all SoC devices, followed by a
64    - DON'T use bus suffixes to encode the type of interface device is using.
68 - DO use a vendor prefix on device-specific property names. Consider if
78 - DO use common property unit suffixes for properties with scientific units.
105 - If schema includes other schema (e.g. /schemas/i2c/i2c-controller.yaml) use
106   "unevaluatedProperties:false". In other cases, usually use
109 - For sub-blocks/components of bigger device (e.g. SoC blocks) use rather
112   For example use "vendor,soc1234-i2c" instead of "vendor,i2c-v2".
114 - "syscon" is not a generic property. Use vendor and type, e.g.
119   compatibles.  If such devices use some other device in a different way, e.g.
120   they program the phy differently, use cell/phandle arguments.
123   of multiple compatibles in the binding, use one of the fallbacks or a more
131 - DO use non-empty 'ranges' to limit the size of child buses/devices. 64-bit