summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Wu <lekensteyn@gmail.com>2013-09-05 12:28:28 +0200
committerPeter Wu <lekensteyn@gmail.com>2013-09-05 12:32:42 +0200
commit18f25c05b2919f705ba0d251c8674b3e13f2c080 (patch)
treefc6710015ec070db3b2be59a435dddc4ba8a0225
parent1122d0b545e1cc46c58e27ecda0349e844126685 (diff)
downloadlinux-18f25c05b2919f705ba0d251c8674b3e13f2c080.tar.gz
HID: logitech-wtp: more verbose debugging message
Seeing many "wtp_input_mapping:" in the logs is useless, I actually want to know whether the function does anything useful or just returns -1. Signed-off-by: Peter Wu <lekensteyn@gmail.com>
-rw-r--r--drivers/hid/hid-logitech-wtp.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/hid/hid-logitech-wtp.c b/drivers/hid/hid-logitech-wtp.c
index a5d76589ff14..d46fa8afbd52 100644
--- a/drivers/hid/hid-logitech-wtp.c
+++ b/drivers/hid/hid-logitech-wtp.c
@@ -713,7 +713,7 @@ static int wtp_input_mapping(struct hid_device *hdev, struct hid_input *hi,
struct input_dev *input = hi->input;
int res_x_mm, res_y_mm;
- dbg_hid("%s:\n", __func__);
+ dbg_hid("%s: usage=0x%08x\n", __func__, usage->hid);
if ((usage->hid & HID_USAGE_PAGE) != HID_UP_BUTTON)
return -1;