From: Joseph Jang <jjang@nvidia.com>
To: <shuah@kernel.org>, <alexandre.belloni@bootlin.com>,
<avagin@google.com>, <jjang@nvidia.com>, <amir73il@gmail.com>,
<brauner@kernel.org>, <mochs@nvidia.com>,
<linux-kernel@vger.kernel.org>, <linux-rtc@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>
Cc: <sdonthineni@nvidia.com>, <treding@nvidia.com>,
<linux-tegra@vger.kernel.org>
Subject: [PATCH 0/1] selftest: rtc: Add support rtc alarm content check
Date: Thu, 2 May 2024 18:41:01 -0700 [thread overview]
Message-ID: <20240503014102.3568130-1-jjang@nvidia.com> (raw)
In order to make sure SET/GET WAKEUP services as optional patch has been
integrated correctly, we have created a shell script to validate
/proc/driver/rtc when it is not empty and then check the absence of alarm
content in RTC metadata according to the rtc wakealarm is supported or not.
Joseph Jang (1):
selftest: rtc: Add support rtc alarm content check
tools/testing/selftests/Makefile | 1 +
tools/testing/selftests/rtc/property/Makefile | 5 ++++
.../selftests/rtc/property/rtc-alarm-test.sh | 27 +++++++++++++++++++
3 files changed, 33 insertions(+)
create mode 100644 tools/testing/selftests/rtc/property/Makefile
create mode 100755 tools/testing/selftests/rtc/property/rtc-alarm-test.sh
--
2.34.1
next reply other threads:[~2024-05-03 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 1:41 Joseph Jang [this message]
2024-05-03 1:41 ` [PATCH 1/1] selftest: rtc: Add support rtc alarm content check Joseph Jang
2024-05-03 6:49 ` Alexandre Belloni
2024-05-03 10:47 ` Joseph Jang
2024-05-03 11:21 ` Joseph Jang
[not found] ` <IA0PR12MB83745321F32B6FA0DE041D10C01F2@IA0PR12MB8374.namprd12.prod.outlook.com>
2024-05-03 12:23 ` Joseph Jang
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=20240503014102.3568130-1-jjang@nvidia.com \
--to=jjang@nvidia.com \
--cc=alexandre.belloni@bootlin.com \
--cc=amir73il@gmail.com \
--cc=avagin@google.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mochs@nvidia.com \
--cc=sdonthineni@nvidia.com \
--cc=shuah@kernel.org \
--cc=treding@nvidia.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).