fuchsia.driver.test

UNKNOWN

BOOT_DRIVERS

PACKAGE_DRIVERS

1

This is what DriverManager will see as its boot directory. Default: DriverTestRealm's package directory

2

The URL for the driver that will be bound to root. Default: fuchsia-boot:///dtr#meta/test-parent-sys.cm NOTE: The test parent driver is not included by default. This must be included in your package to work correctly.

3

If this is true, then DriverManager will load DFv2 drivers. Default: false

4

If this is true, then DriverManager will enable the unit tests for each driver that is loaded. Default: false

5

If this is true, then DriverManager will enable the unit tests for each driver in this vector. Default: empty

6

If this is true, then DriverManager will disable the unit tests for each driver in this vector. This overrides both a specific request for enabling a test and the 'driver_tests_enable_all' parameter. Default: empty

7

Set a log level for the specific driver. Default: Log levels are set to INFO

8

Disable specific drivers. These drivers will not be bound or loaded. Default: empty

9

Specify drivers to bind 'eagerly'. This turns a driver that normally binds as a fallback driver into a driver that will be bound normally. Default: empty

10

Specify the board name that drivers are aware of. Default: driver-integration-test

11

DEPRECATED: Use dtr_offers. Specify additional offers from the test to a driver collection Default: empty

12

DEPRECATED: Use dtr_exposes. Specify services to expose from the test to a driver collection Default: empty

13

DEPRECATED: Use test_component to provide resolved test component. The driver test realm can load drivers packaged with the test suite through this directory. Note that this directory must be readable and executable.

This can be used if the test suite needs to use some drivers packaged with the DriverTestRealm in addition to drivers packaged with the test suite. In that case, the user can leave RealmArgs::boot unset and use RealmArgs::pkg and RealmArgs::driver_urls.

Drivers in this directory can be registered using the driver_urls argument below.

Default: DriverTestRealm's package directory.

14

Specify offers from the test to the driver test realm. The driver test realm will forward these to the driver collections. Default: empty

15

Specify exposes from the driver test realm to the test. The driver test realm will forward these from the driver collections. Default: empty

16

The resolved component information of the test component that is starting the driver test realm. This will be used to discover drivers that the test wants to provide to the driver test realm. Drivers can be both in the test component package, or a subpackage of the test component package. By default all drivers discovered that don't also exist in the |boot| directory will be considered to be base drivers. Use |boot_driver_components| to provide a list of drivers that should be boot drivers. Default: empty

17

How long the driver index waits idle before it saves state, escrows its handles with the component framework, and shuts down. Default: never shuts down

18

A list of software only devices that should be created. Typically this is used to create fake hardware for tests. Devices will be spawned as platform devices under the platform bus. Note that the platform bus must be the root driver for this to do anything meaningful.

19

The list of driver component names that should be considered as boot drivers. Boot drivers are started in the boot-drivers collection which has more capabilities available to it. Entries should be the component name (eg: "my_driver_component.cm"). Default: empty

20

Devicetree blob that should be handed to the board driver.

21

Platform Vendor ID which should be specified to the platform bus driver.

22

Platform ID which should be specified to the platform bus driver.

1

2

1

2

1

2

1

2

1

2

1

2

3

A driver name is the name defined in ZIRCON_DRIVER_BEGIN begin macro for a specific driver.