From: Thorsten Blum <blum@kernel.org>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Emmanuel Gil Peyrot <linkmauve@linkmauve.fr>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
Thorsten Blum <blum@kernel.org>
Subject: [PATCH 3/5] rtc: gamecube: Explain why fast_io is enabled
Date: Mon, 9 Nov 2026 23:39:05 +0100 [thread overview]
Message-ID: <20261109223902.84918-8-blum@kernel.org> (raw)
In-Reply-To: <20261109223902.84918-6-blum@kernel.org>
Replace the TODO with an explanation of why fast_io is enabled.
Signed-off-by: Thorsten Blum <blum@kernel.org>
---
drivers/rtc/rtc-gamecube.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-gamecube.c b/drivers/rtc/rtc-gamecube.c
index 25290f162cbc..4b45274effdf 100644
--- a/drivers/rtc/rtc-gamecube.c
+++ b/drivers/rtc/rtc-gamecube.c
@@ -152,7 +152,7 @@ static int exi_write(void *context, u32 reg, u32 data)
}
static const struct regmap_bus exi_bus = {
- /* TODO: is that true? Not that it matters here, but still. */
+ /* Transfers use MMIO and busy-wait for completion without sleeping. */
.fast_io = true,
.reg_read = exi_read,
.reg_write = exi_write,
next prev parent reply other threads:[~2026-11-09 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 22:39 [PATCH 1/5] rtc: gamecube: Propagate address translation error Thorsten Blum
2026-11-09 22:39 ` [PATCH 2/5] rtc: gamecube: Add missing newline to SRAM bias debug message Thorsten Blum
2026-11-09 22:41 ` sashiko-bot
2026-11-09 22:39 ` Thorsten Blum [this message]
2026-11-09 22:41 ` [PATCH 3/5] rtc: gamecube: Explain why fast_io is enabled sashiko-bot
2026-11-09 22:39 ` [PATCH 4/5] rtc: gamecube: Use unsigned int for control0 Thorsten Blum
2026-11-09 22:41 ` sashiko-bot
2026-11-09 22:39 ` [PATCH 5/5] rtc: gamecube: Use register definitions Thorsten Blum
2026-11-09 22:41 ` sashiko-bot
2026-11-09 22:41 ` [PATCH 1/5] rtc: gamecube: Propagate address translation error sashiko-bot
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=20261109223902.84918-8-blum@kernel.org \
--to=blum@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=linkmauve@linkmauve.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.