mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-29 13:53:33 +00:00
kselftest: devices: Add sample board file for google,spherion
Add a sample board file describing the file's format and with the list of devices expected to be probed on the google,spherion machine as an example. Test output: TAP version 13 Using board file: boards/google,spherion.yaml 1..8 ok 1 /usb2-controller@11200000/1.4.1/camera.device ok 2 /usb2-controller@11200000/1.4.1/camera.0.driver ok 3 /usb2-controller@11200000/1.4.1/camera.1.driver ok 4 /usb2-controller@11200000/1.4.2/bluetooth.device ok 5 /usb2-controller@11200000/1.4.2/bluetooth.0.driver ok 6 /usb2-controller@11200000/1.4.2/bluetooth.1.driver ok 7 /pci-controller@11230000/0.0/0.0/wifi.device ok 8 /pci-controller@11230000/0.0/0.0/wifi.driver Totals: pass:8 fail:0 xfail:0 xpass:0 skip:0 error:0 Signed-off-by: "Nícolas F. R. A. Prado" <nfraprado@collabora.com> Link: https://lore.kernel.org/r/20240122-discoverable-devs-ksft-v4-2-d602e1df4aa2@collabora.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
dacf1d7a78
commit
a1d086db92
1 changed files with 50 additions and 0 deletions
50
tools/testing/selftests/devices/boards/google,spherion.yaml
Normal file
50
tools/testing/selftests/devices/boards/google,spherion.yaml
Normal file
|
@ -0,0 +1,50 @@
|
|||
# SPDX-License-Identifier: GPL-2.0
|
||||
#
|
||||
# This is the device definition for the Google Spherion Chromebook.
|
||||
# The filename "google,spherion" comes from the Devicetree compatible, so this
|
||||
# file will be automatically used when the test is run on that machine.
|
||||
#
|
||||
# The top-level is a list of controllers, either for USB or PCI(e).
|
||||
# Every controller needs to have a 'type' key set to either 'usb-controller' or
|
||||
# 'pci-controller'.
|
||||
# Every controller needs to be uniquely identified on the platform. To achieve
|
||||
# this, several optional keys can be used:
|
||||
# - dt-mmio: identify the MMIO address of the controller as defined in the
|
||||
# Devicetree.
|
||||
# - usb-version: for USB controllers to differentiate between USB3 and USB2
|
||||
# buses sharing the same controller.
|
||||
# - acpi-uid: _UID property of the controller as supplied by the ACPI. Useful to
|
||||
# distinguish between multiple PCI host controllers.
|
||||
#
|
||||
# The 'devices' key defines a list of devices that are accessible under that
|
||||
# controller. A device might be a leaf device or another controller (see
|
||||
# 'Dell Inc.,XPS 13 9300.yaml').
|
||||
#
|
||||
# The 'path' key is needed for every child device (that is, not top-level) to
|
||||
# define how to reach this device from the parent controller. For USB devices it
|
||||
# follows the format \d(.\d)* and denotes the port in the hub at each level in
|
||||
# the USB topology. For PCI devices it follows the format \d.\d(/\d.\d)*
|
||||
# denoting the device (identified by device-function pair) at each level in the
|
||||
# PCI topology.
|
||||
#
|
||||
# The 'name' key is used in the leaf devices to name the device for clarity in
|
||||
# the test output.
|
||||
#
|
||||
# For USB leaf devices, the 'interfaces' key should contain a list of the
|
||||
# interfaces in that device that should be bound to a driver.
|
||||
#
|
||||
- type: usb-controller
|
||||
dt-mmio: 11200000
|
||||
usb-version: 2
|
||||
devices:
|
||||
- path: 1.4.1
|
||||
interfaces: [0, 1]
|
||||
name: camera
|
||||
- path: 1.4.2
|
||||
interfaces: [0, 1]
|
||||
name: bluetooth
|
||||
- type: pci-controller
|
||||
dt-mmio: 11230000
|
||||
devices:
|
||||
- path: 0.0/0.0
|
||||
name: wifi
|
Loading…
Reference in a new issue