From: Tzung-Bi Shih <tzungbi@kernel.org>
To: bleung@chromium.org, groeck@chromium.org
Cc: chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
tzungbi@kernel.org, dianders@chromium.org
Subject: [PATCH 0/4] platform/chrome: cros_ec_proto: add initial Kunit tests
Date: Wed, 18 May 2022 17:18:10 +0800 [thread overview]
Message-ID: <20220518091814.2028579-1-tzungbi@kernel.org> (raw)
The series adds some early Kunit tests for ChromeOS EC protocol.
The 2nd patch is a refactor.
The 3rd patch updates code comment.
The 1st and 4th patches add Kunit tests.
Use the following example commands to run the Kunit tests:
$ ./tools/testing/kunit/kunit.py run \
--arch=x86_64 \
--kconfig_add CONFIG_CHROME_PLATFORMS=y \
--kconfig_add CONFIG_CROS_EC=y \
cros_ec*
$ ./tools/testing/kunit/kunit.py run \
--arch=arm64 --cross_compile aarch64-linux-gnu- \
--kconfig_add CONFIG_CHROME_PLATFORMS=y \
--kconfig_add CONFIG_CROS_EC=y \
cros_ec*
Tzung-Bi Shih (4):
platform/chrome: cros_ec_proto: add Kunit tests for
cros_ec_prepare_tx()
platform/chrome: cros_ec_proto: factor legacy out from
cros_ec_prepare_tx()
platform/chrome: cros_ec_proto: update cros_ec_check_result() comment
platform/chrome: cros_ec_proto: add Kunit tests for
cros_ec_check_result()
drivers/platform/chrome/Kconfig | 9 +
drivers/platform/chrome/Makefile | 3 +
drivers/platform/chrome/cros_ec_proto.c | 58 ++---
drivers/platform/chrome/cros_ec_proto_test.c | 214 +++++++++++++++++++
4 files changed, 259 insertions(+), 25 deletions(-)
create mode 100644 drivers/platform/chrome/cros_ec_proto_test.c
base-commit: a0e7d2f65fa706a106dae4b52a7cfe48e0ddfdff
--
2.36.0.550.gb090851708-goog
next reply other threads:[~2022-05-18 9:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 9:18 Tzung-Bi Shih [this message]
2022-05-18 9:18 ` [PATCH 1/4] platform/chrome: cros_ec_proto: add Kunit tests for cros_ec_prepare_tx() Tzung-Bi Shih
2022-05-18 16:23 ` Guenter Roeck
2022-05-18 9:18 ` [PATCH 2/4] platform/chrome: cros_ec_proto: factor legacy out from cros_ec_prepare_tx() Tzung-Bi Shih
2022-05-18 16:26 ` Guenter Roeck
2022-05-18 9:18 ` [PATCH 3/4] platform/chrome: cros_ec_proto: update cros_ec_check_result() comment Tzung-Bi Shih
2022-05-18 16:28 ` Guenter Roeck
2022-05-18 9:18 ` [PATCH 4/4] platform/chrome: cros_ec_proto: add Kunit tests for cros_ec_check_result() Tzung-Bi Shih
2022-05-18 16:31 ` Guenter Roeck
2022-05-19 1:50 ` [PATCH 0/4] platform/chrome: cros_ec_proto: add initial Kunit tests patchwork-bot+chrome-platform
2022-05-24 0:50 ` patchwork-bot+chrome-platform
2022-06-06 4:08 ` patchwork-bot+chrome-platform
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=20220518091814.2028579-1-tzungbi@kernel.org \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.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).