xref: /linux/tools/testing/selftests/devices/probe/boards/google,spherion.yaml (revision c532de5a67a70f8533d495f8f2aaa9a0491c3ad0)
1# SPDX-License-Identifier: GPL-2.0
2#
3# This is the device definition for the Google Spherion Chromebook.
4# The filename "google,spherion" comes from the Devicetree compatible, so this
5# file will be automatically used when the test is run on that machine.
6#
7# The top-level is a list of controllers, either for USB or PCI(e).
8# Every controller needs to have a 'type' key set to either 'usb-controller' or
9# 'pci-controller'.
10# Every controller needs to be uniquely identified on the platform. To achieve
11# this, several optional keys can be used:
12# - dt-mmio: identify the MMIO address of the controller as defined in the
13#   Devicetree.
14# - of-fullname-regex: regular expression to match against the OF_FULLNAME
15#   property. Useful when the controller's address is not unique across other
16#   sibling controllers. In this case, dt-mmio can't be used, and this property
17#   allows the matching to include parent nodes as well to make it unique.
18# - usb-version: for USB controllers to differentiate between USB3 and USB2
19#   buses sharing the same controller.
20# - acpi-uid: _UID property of the controller as supplied by the ACPI. Useful to
21#   distinguish between multiple PCI host controllers.
22#
23# The 'devices' key defines a list of devices that are accessible under that
24# controller. A device might be a leaf device or another controller (see
25# 'Dell Inc.,XPS 13 9300.yaml').
26#
27# The 'path' key is needed for every child device (that is, not top-level) to
28# define how to reach this device from the parent controller. For USB devices it
29# follows the format \d(.\d)* and denotes the port in the hub at each level in
30# the USB topology. For PCI devices it follows the format \d.\d(/\d.\d)*
31# denoting the device (identified by device-function pair) at each level in the
32# PCI topology.
33#
34# The 'name' key is used in the leaf devices to name the device for clarity in
35# the test output.
36#
37# For USB leaf devices, the 'interfaces' key should contain a list of the
38# interfaces in that device that should be bound to a driver.
39#
40- type: usb-controller
41  dt-mmio: 11200000
42  usb-version: 2
43  devices:
44    - path: 1.4.1
45      interfaces: [0, 1]
46      name: camera
47    - path: 1.4.2
48      interfaces: [0, 1]
49      name: bluetooth
50- type: pci-controller
51  dt-mmio: 11230000
52  devices:
53    - path: 0.0/0.0
54      name: wifi
55