Thread (2 messages) 2 messages, 2 authors, 16d ago

Re: [PATCH] HID: i2c-hid: Fix "(null)" device name error logs in i2c_hid_parse

From: Mario Limonciello <superm1@kernel.org>
Date: 2026-07-06 13:15:13
Also in: lkml

On 7/6/26 07:29, Ai Chao wrote:
When i2c-hid fails to read the HID report descriptor during device
initialization, the error message prints as:

   hid (null): reading report descriptor failed

The HID device name is set in hid_add_device() after calling
hdev->ll_driver->parse(), so when i2c_hid_parse() fails and calls
hid_err(), the device name has not been set yet, resulting in "(null)"
output.

Use dev_err(&client->dev, ...) instead of hid_err(hid, ...) because
the I2C client device is fully initialized with a proper name, providing
meaningful error messages for debugging.

Before: hid (null): reading report descriptor failed
After:  i2c_hid i2c-TPD0001:00: reading report descriptor failed

Signed-off-by: Ai Chao <redacted>
I think it would be good to track down the Fixes tag that this goes with.
quoted hunk ↗ jump to hunk
---
  drivers/hid/i2c-hid/i2c-hid-core.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/i2c-hid/i2c-hid-core.c b/drivers/hid/i2c-hid/i2c-hid-core.c
index 3adb16366e93..0e725a0f0abe 100644
--- a/drivers/hid/i2c-hid/i2c-hid-core.c
+++ b/drivers/hid/i2c-hid/i2c-hid-core.c
@@ -792,7 +792,7 @@ static int i2c_hid_parse(struct hid_device *hid)
  					    ihid->hdesc.wReportDescRegister,
  					    rdesc, rsize);
  		if (ret) {
-			hid_err(hid, "reading report descriptor failed\n");
+			dev_err(&client->dev, "reading report descriptor failed\n");
  			goto out;
  		}
  	}
  
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help