From: Christopher Obbard <chris.obbard@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: 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, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 2/2] kselftest: devices: Add sample board file for google,spherion
Date: Tue, 28 Nov 2023 17:59:01 +0000 [thread overview]
Message-ID: <897e404e0097a0c422bdb1d0e2d6cbb996500e8e.camel@collabora.com> (raw)
In-Reply-To: <20231127233558.868365-3-nfraprado@collabora.com>
Hi Nícolas,
On Mon, 2023-11-27 at 18:34 -0500, Nícolas F. R. A. Prado wrote:
> 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.
Did you consider using some machine-readable & extensible format like yaml?
Surely we don't need to invent yet-another file-format? :-)
Chris
>
> 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
>
> _______________________________________________
> Kernel mailing list -- kernel@mailman.collabora.com
> To unsubscribe send an email to kernel-leave@mailman.collabora.com
next prev parent reply other threads:[~2023-11-28 17:59 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 ` [RFC PATCH v2 2/2] kselftest: devices: Add sample board file for google,spherion Nícolas F. R. A. Prado
2023-11-28 0:10 ` 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 [this message]
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=897e404e0097a0c422bdb1d0e2d6cbb996500e8e.camel@collabora.com \
--to=chris.obbard@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