From: Hex Lindqvist <hex@freenixos.com>
To: Andi Shyti <andi.shyti@kernel.org>, Ajay Gupta <ajayg@nvidia.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] i2c: nvidia-gpu: Log transfer timeouts at debug level
Date: Fri, 13 Nov 2026 17:32:35 -0800 [thread overview]
Message-ID: <20261114013235.1239905-1-hex@freenixos.com> (raw)
GPUs without a USB Type-C port, such as the GTX 1660 Ti, have no CCGx
controller behind the ccgx-ucsi client, so every transfer to it times
out and logs:
nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
The caller already gets -ETIMEDOUT and decides whether it matters. Log
the timeout at debug level.
Tested on an ASUS TUF Gaming A17 (FA706IU, GTX 1660 Ti): the error is
gone, and the timeout still shows up with dynamic debug.
Assisted by LLM.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=206653
Link: https://lore.kernel.org/all/20200921180840.GA18032@ninjato/
Signed-off-by: Hex Lindqvist <hex@freenixos.com>
---
The ucsi_ccg errors that follow are fixed by a separate patch to
linux-usb. Wolfram suggested dropping this message in 2020; debug level
keeps the status value.
drivers/i2c/busses/i2c-nvidia-gpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-nvidia-gpu.c b/drivers/i2c/busses/i2c-nvidia-gpu.c
index 14c059b03945..987dd3edb0bb 100644
--- a/drivers/i2c/busses/i2c-nvidia-gpu.c
+++ b/drivers/i2c/busses/i2c-nvidia-gpu.c
@@ -88,7 +88,7 @@ static int gpu_i2c_check_status(struct gpu_i2c_dev *i2cd)
500, 1000 * USEC_PER_MSEC);
if (ret) {
- dev_err(i2cd->dev, "i2c timeout error %x\n", val);
+ dev_dbg(i2cd->dev, "i2c timeout, status %#x\n", val);
return -ETIMEDOUT;
}
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.56.0
reply other threads:[~2026-11-14 1:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261114013235.1239905-1-hex@freenixos.com \
--to=hex@freenixos.com \
--cc=ajayg@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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