From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Shuah Khan <shuah@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: "Saravana Kannan" <saravanak@google.com>,
"Rob Herring" <robh+dt@kernel.org>,
kernelci@lists.linux.dev, "David Gow" <davidgow@google.com>,
"Guenter Roeck" <groeck@chromium.org>,
linux-kselftest@vger.kernel.org, linux-usb@vger.kernel.org,
kernel@collabora.com, "Dan Carpenter" <dan.carpenter@linaro.org>,
"Tim Bird" <Tim.Bird@sony.com>,
linux-pci@vger.kernel.org,
"Doug Anderson" <dianders@chromium.org>,
devicetree@vger.kernel.org,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH v2 2/2] kselftest: devices: Add sample board file for google,spherion
Date: Mon, 27 Nov 2023 18:34:07 -0500 [thread overview]
Message-ID: <20231127233558.868365-3-nfraprado@collabora.com> (raw)
In-Reply-To: <20231127233558.868365-1-nfraprado@collabora.com>
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.
Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
---
(no changes since v1)
.../testing/selftests/devices/boards/google,spherion | 12 ++++++++++++
1 file changed, 12 insertions(+)
create mode 100644 tools/testing/selftests/devices/boards/google,spherion
diff --git a/tools/testing/selftests/devices/boards/google,spherion b/tools/testing/selftests/devices/boards/google,spherion
new file mode 100644
index 000000000000..db9a17cccd03
--- /dev/null
+++ b/tools/testing/selftests/devices/boards/google,spherion
@@ -0,0 +1,12 @@
+# Example test definition for Google Spherion Chromebook
+#
+# Format:
+# usb|pci test_name number_of_matches field=value [ field=value ... ]
+#
+# The available match fields vary by bus. The field-value match pairs for a
+# device can be retrieved from the device's modalias attribute in sysfs. A
+# subset of the fields may be used to make the match more generic so it can work
+# with the different hardware variants of a device on the machine.
+usb camera 1 ic=0e isc=01 ip=00
+usb bluetooth 1 ic=e0 isc=01 ip=01 in=00
+pci wifi 1 v=14c3 d=7961
--
2.42.1
next prev parent reply other threads:[~2023-11-27 23:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 23:34 [RFC PATCH v2 0/2] Add test to verify probe of devices from discoverable busses Nícolas F. R. A. Prado
2023-11-27 23:34 ` [RFC PATCH v2 1/2] kselftest: " Nícolas F. R. A. Prado
2023-11-27 23:34 ` Nícolas F. R. A. Prado [this message]
2023-11-28 0:10 ` [RFC PATCH v2 2/2] kselftest: devices: Add sample board file for google,spherion Bird, Tim
2023-11-28 14:10 ` Mark Brown
2023-11-28 14:43 ` Nícolas F. R. A. Prado
2023-11-28 17:54 ` Bird, Tim
2023-11-28 19:52 ` Nícolas F. R. A. Prado
2023-11-28 17:59 ` Christopher Obbard
2023-11-28 18:33 ` Bird, Tim
2023-11-28 21:05 ` 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=20231127233558.868365-3-nfraprado@collabora.com \
--to=nfraprado@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=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