From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Shuah Khan" <shuah@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Bjorn Helgaas" <bhelgaas@google.com>
Cc: kernelci@lists.linux.dev, kernel@collabora.com,
Tim Bird <Tim.Bird@sony.com>,
linux-pci@vger.kernel.org, David Gow <davidgow@google.com>,
linux-kselftest@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Doug Anderson <dianders@chromium.org>,
linux-usb@vger.kernel.org, Saravana Kannan <saravanak@google.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Guenter Roeck <groeck@chromium.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/3] kselftest: devices: Add sample board file for XPS 13 9300
Date: Tue, 23 Jan 2024 12:08:22 +0100 [thread overview]
Message-ID: <7aa0df3d-ae9d-414d-ad7f-ed7588e70f3e@collabora.com> (raw)
In-Reply-To: <20240122-discoverable-devs-ksft-v4-3-d602e1df4aa2@collabora.com>
Il 22/01/24 19:53, Nícolas F. R. A. Prado ha scritto:
> Add a sample board file describing the file's format and with the list
> of devices expected to be probed on the XPS 13 9300 machine as an
> example x86 platform.
>
> Test output:
>
> TAP version 13
> Using board file: boards/Dell Inc.,XPS 13 9300.yaml
> 1..22
> ok 1 /pci-controller/14.0/usb2-controller/9/camera.device
> ok 2 /pci-controller/14.0/usb2-controller/9/camera.0.driver
> ok 3 /pci-controller/14.0/usb2-controller/9/camera.1.driver
> ok 4 /pci-controller/14.0/usb2-controller/9/camera.2.driver
> ok 5 /pci-controller/14.0/usb2-controller/9/camera.3.driver
> ok 6 /pci-controller/14.0/usb2-controller/10/bluetooth.device
> ok 7 /pci-controller/14.0/usb2-controller/10/bluetooth.0.driver
> ok 8 /pci-controller/14.0/usb2-controller/10/bluetooth.1.driver
> ok 9 /pci-controller/2.0/gpu.device
> ok 10 /pci-controller/2.0/gpu.driver
> ok 11 /pci-controller/4.0/thermal.device
> ok 12 /pci-controller/4.0/thermal.driver
> ok 13 /pci-controller/12.0/sensors.device
> ok 14 /pci-controller/12.0/sensors.driver
> ok 15 /pci-controller/14.3/wifi.device
> ok 16 /pci-controller/14.3/wifi.driver
> ok 17 /pci-controller/1d.0/0.0/ssd.device
> ok 18 /pci-controller/1d.0/0.0/ssd.driver
> ok 19 /pci-controller/1d.7/0.0/sdcard-reader.device
> ok 20 /pci-controller/1d.7/0.0/sdcard-reader.driver
> ok 21 /pci-controller/1f.3/audio.device
> ok 22 /pci-controller/1f.3/audio.driver
> Totals: pass:22 fail:0 xfail:0 xpass:0 skip:0 error:0
>
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> ---
> .../devices/boards/Dell Inc.,XPS 13 9300.yaml | 40 ++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
>
> diff --git a/tools/testing/selftests/devices/boards/Dell Inc.,XPS 13 9300.yaml b/tools/testing/selftests/devices/boards/Dell Inc.,XPS 13 9300.yaml
> new file mode 100644
> index 000000000000..ff932eb19f0b
> --- /dev/null
> +++ b/tools/testing/selftests/devices/boards/Dell Inc.,XPS 13 9300.yaml
> @@ -0,0 +1,40 @@
> +# SPDX-License-Identifier: GPL-2.0
> +#
> +# This is the device definition for the XPS 13 9300.
> +# The filename "Dell Inc.,XPS 13 9300" was chosen following the format
> +# "Vendor,Product", where Vendor comes from
> +# /sys/devices/virtual/dmi/id/sys_vendor, and Product comes from
> +# /sys/devices/virtual/dmi/id/product_name.
> +#
> +# See google,spherion.yaml for more information.
What if - instead of taking google,spherion.yaml as an example - you create a new
file named something like
"example,device.yaml"
that would be a fantasy device, bringing examples for all .. or most of .. the
currently supported types/devices?
You would also move the nice documentation that you wrote in spherion.yaml to the
new example,device.yaml and ask to refer to that instead in all of the real device
specific definitions.
# SPDX-License-Identifier: GPL-2.0 <--- (GPL-2.0 OR MIT) like device trees perhaps?
#
# This is the device definition for the Example Device
# The filename "Example Device" was chosen following the format
# "Vendor,Product", where:
# - Vendor is "Example" and comes from /sys/devices/virtual/dmi/id/sys_vendor
# - Product is "Device" and comes from /sys/devices/virtual/dmi/id/product_name
#
# ....the rest of the blurb goes here
#
- type : .... this that the other
devices:
- the least amount of device descriptions that you can use for documenting how
to write this stuff :-)
Anything against that?
Cheers,
Angelo
> +#
> +- type: pci-controller
> + # This machine has a single PCI host controller so it's valid to not have any
> + # key to identify the controller. If it had more than one controller, the UID
> + # of the controller from ACPI could be used to distinguish as follows:
> + #acpi-uid: 0
> + devices:
> + - path: 14.0
> + type: usb-controller
> + usb-version: 2
> + devices:
> + - path: 9
> + name: camera
> + interfaces: [0, 1, 2, 3]
> + - path: 10
> + name: bluetooth
> + interfaces: [0, 1]
> + - path: 2.0
> + name: gpu
> + - path: 4.0
> + name: thermal
> + - path: 12.0
> + name: sensors
> + - path: 14.3
> + name: wifi
> + - path: 1d.0/0.0
> + name: ssd
> + - path: 1d.7/0.0
> + name: sdcard-reader
> + - path: 1f.3
> + name: audio
>
next prev parent reply other threads:[~2024-01-23 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 18:53 [PATCH v4 0/3] Add test to verify probe of devices from discoverable buses Nícolas F. R. A. Prado
2024-01-22 18:53 ` [PATCH v4 1/3] kselftest: " Nícolas F. R. A. Prado
2024-01-22 18:53 ` [PATCH v4 2/3] kselftest: devices: Add sample board file for google,spherion Nícolas F. R. A. Prado
2024-01-22 18:53 ` [PATCH v4 3/3] kselftest: devices: Add sample board file for XPS 13 9300 Nícolas F. R. A. Prado
2024-01-23 11:08 ` AngeloGioacchino Del Regno [this message]
2024-01-23 14:50 ` Nícolas F. R. A. Prado
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7aa0df3d-ae9d-414d-ad7f-ed7588e70f3e@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Tim.Bird@sony.com \
--cc=bhelgaas@google.com \
--cc=dan.carpenter@linaro.org \
--cc=davidgow@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=kernel@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nfraprado@collabora.com \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).