Path: blob/master/tools/testing/selftests/devices/probe/boards/google,spherion.yaml
26292 views
# SPDX-License-Identifier: GPL-2.01#2# This is the device definition for the Google Spherion Chromebook.3# The filename "google,spherion" comes from the Devicetree compatible, so this4# file will be automatically used when the test is run on that machine.5#6# The top-level is a list of controllers, either for USB or PCI(e).7# Every controller needs to have a 'type' key set to either 'usb-controller' or8# 'pci-controller'.9# Every controller needs to be uniquely identified on the platform. To achieve10# this, several optional keys can be used:11# - dt-mmio: identify the MMIO address of the controller as defined in the12# Devicetree.13# - of-fullname-regex: regular expression to match against the OF_FULLNAME14# property. Useful when the controller's address is not unique across other15# sibling controllers. In this case, dt-mmio can't be used, and this property16# allows the matching to include parent nodes as well to make it unique.17# - usb-version: for USB controllers to differentiate between USB3 and USB218# buses sharing the same controller.19# - acpi-uid: _UID property of the controller as supplied by the ACPI. Useful to20# distinguish between multiple PCI host controllers.21#22# The 'devices' key defines a list of devices that are accessible under that23# controller. A device might be a leaf device or another controller (see24# 'Dell Inc.,XPS 13 9300.yaml').25#26# The 'path' key is needed for every child device (that is, not top-level) to27# define how to reach this device from the parent controller. For USB devices it28# follows the format \d(.\d)* and denotes the port in the hub at each level in29# the USB topology. For PCI devices it follows the format \d.\d(/\d.\d)*30# denoting the device (identified by device-function pair) at each level in the31# PCI topology.32#33# The 'name' key is used in the leaf devices to name the device for clarity in34# the test output.35#36# For USB leaf devices, the 'interfaces' key should contain a list of the37# interfaces in that device that should be bound to a driver.38#39- type: usb-controller40dt-mmio: 1120000041usb-version: 242devices:43- path: 1.4.144interfaces: [0, 1]45name: camera46- path: 1.4.247interfaces: [0, 1]48name: bluetooth49- type: pci-controller50dt-mmio: 1123000051devices:52- path: 0.0/0.053name: wifi545556