Macros§
- Pattern that matches an unknown
CompositeNodeSpecErrormember. - Pattern that matches an unknown
DriverPackageTypemember. - Pattern that matches an unknown
NodeErrormember. - Pattern that matches an unknown
NodePropertyValuemember. - Pattern that matches an unknown
Offermember.
Structs§
- Represents a bind rule in a parent specification.
- Information for a composite driver.
- Information for a composite driver that has matched with a composite.
- Information for a composite that is defined by a composite node spec.
- A Stream of incoming requests for fuchsia.driver.framework/CompositeNodeManager.
- Struct that represents a composite node specification.
- A parent to a composite that is defined by a composite node spec.
- Device categories as provided in the driver’s component manifest.
- General information for a driver, used with both composite and normal drivers.
- Arguments for starting a driver.
- Arguments for adding a node.
- A Stream of incoming requests for fuchsia.driver.framework/NodeController.
- Definition of a property for a node. A property is commonly used to match a node to a driver for driver binding.
- Contains the node properties that belong to a node.
- A Stream of incoming requests for fuchsia.driver.framework/Node.
- Definition of a symbol provided by a driver for a node. A symbol is local to a driver host.
- Specification for a node that parents the composite node created from the composite node specification.
Enums§
- Protocol through which board drivers can create composite node specs.
- Error codes for the CompositeNodeManager protocol.
- Represents a bind rule condition.
- The type of Fuchsia package that a driver component is inside of. More details about the various package categories are available at: https://fuchsia.dev/fuchsia-src/concepts/packages/package#types_of_packages
- Protocol through which a parent node controls one of its children.
- Error codes for the Node protocol.
- Protocol through which a driver manages a node that it is bound to. Drivers should maintain their client connection to the node. Dropping the client connection while the driver is running will cause the driver framework to remove the driver and node from the topology. If the driver has set
host_restart_on_crashto “true” in their component manifest, dropping the connection will initiate a restart of the driver host and driver.