From: Emanuele Ghidoli <ghidoliemanuele@gmail.com>
To: alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
linux-rtc@vger.kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org
Cc: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
jjang@nvidia.com, kobak@nvidia.com, mochs@nvidia.com
Subject: [PATCH v1 0/2] Fixes for RX8310 RTC Configuration and rtctest Alarm
Date: Mon, 24 Jun 2024 12:23:52 +0200 [thread overview]
Message-ID: <20240624102354.894871-1-ghidoliemanuele@gmail.com> (raw)
From: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
Hi,
I am submitting two patches related to the RX8310 RTC configuration:
1. **Correct RX8310 RTC Features Configuration:**
- Sets one-minute alarm resolution.
- Disables update IRQ.
Without this patch, if the interrupt is configured in the device tree, `hwclock` fails to read the RTC as it waits for the update IRQ.
2. **Avoid rtctest Alarm Test Failures:**
- Ensures rtctest alarm tests do not fail on hardware that only supports one-minute alarm resolution.
I know the second patch creates conflict with this one: https://lore.kernel.org/all/20240524013807.154338-1-jjang@nvidia.com/.
I think that series can reuse the rtc_get_features function I implemented.
Best regards,
Emanuele Ghidoli
Emanuele Ghidoli (2):
rtc: ds1307: set one-minute alarm resolution for rx_8130
selftests: rtc: rtctest: skip alarm test if alarm resolution is one
minute
drivers/rtc/rtc-ds1307.c | 14 +++++++++++--
tools/testing/selftests/rtc/rtctest.c | 30 +++++++++++++++++++++++++++
2 files changed, 42 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2024-06-24 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 10:23 Emanuele Ghidoli [this message]
2024-06-24 10:23 ` [PATCH v1 1/2] rtc: ds1307: set one-minute alarm resolution for rx_8130 Emanuele Ghidoli
2024-06-24 10:23 ` [PATCH v1 2/2] selftests: rtc: rtctest: skip alarm test if alarm resolution is one minute Emanuele Ghidoli
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=20240624102354.894871-1-ghidoliemanuele@gmail.com \
--to=ghidoliemanuele@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=jjang@nvidia.com \
--cc=kobak@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mochs@nvidia.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