From: kernel test robot <lkp@intel.com>
To: Stephen Boyd <swboyd@chromium.org>,
benjamin.tissoires@redhat.com,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jikos@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, Sean O'Brien <seobrien@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
Zhengqiao Xia <xiazhengqiao@huaqin.corp-partner.google.com>
Subject: Re: [PATCH 3/5] HID: Extract vivaldi hid feature mapping for use in hid-hammer
Date: Sat, 5 Feb 2022 08:15:59 +0800 [thread overview]
Message-ID: <202202050807.BvUyitVE-lkp@intel.com> (raw)
In-Reply-To: <20220204202021.895426-4-swboyd@chromium.org>
Hi Stephen,
I love your patch! Yet something to improve:
[auto build test ERROR on 26291c54e111ff6ba87a164d85d4a4e134b7315c]
url: https://github.com/0day-ci/linux/commits/Stephen-Boyd/Input-HID-Consolidate-ChromeOS-Vivaldi-keyboard-logic/20220205-042211
base: 26291c54e111ff6ba87a164d85d4a4e134b7315c
config: x86_64-randconfig-a004-20220131 (https://download.01.org/0day-ci/archive/20220205/202202050807.BvUyitVE-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/83759eb892fd16fd0bb7ff4bb0c4baa4e7a0283e
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Stephen-Boyd/Input-HID-Consolidate-ChromeOS-Vivaldi-keyboard-logic/20220205-042211
git checkout 83759eb892fd16fd0bb7ff4bb0c4baa4e7a0283e
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
vmlinux.o: warning: objtool: mce_start()+0x4e: call to clear_bit() leaves .noinstr.text section
vmlinux.o: warning: objtool: mce_read_aux()+0x41: call to mca_msr_reg() leaves .noinstr.text section
vmlinux.o: warning: objtool: do_machine_check()+0x39d: call to test_bit() leaves .noinstr.text section
vmlinux.o: warning: objtool: enter_from_user_mode()+0x4e: call to on_thread_stack() leaves .noinstr.text section
vmlinux.o: warning: objtool: syscall_enter_from_user_mode()+0x53: call to on_thread_stack() leaves .noinstr.text section
vmlinux.o: warning: objtool: syscall_enter_from_user_mode_prepare()+0x4e: call to on_thread_stack() leaves .noinstr.text section
vmlinux.o: warning: objtool: irqentry_enter_from_user_mode()+0x4e: call to on_thread_stack() leaves .noinstr.text section
ld: drivers/input/vivaldi-keymap.o: in function `vivaldi_hid_feature_mapping':
>> drivers/input/vivaldi-keymap.c:73: undefined reference to `hid_alloc_report_buf'
>> ld: drivers/input/vivaldi-keymap.c:90: undefined reference to `hid_hw_raw_request'
>> ld: drivers/input/vivaldi-keymap.c:108: undefined reference to `hid_report_raw_event'
vim +73 drivers/input/vivaldi-keymap.c
44
45 /**
46 * vivaldi_hid_feature_mapping - Fill out vivaldi keymap data exposed via HID
47 * @data: The vivaldi function keymap
48 * @hdev: HID device to parse
49 * @field: HID field to parse
50 * @usage: HID usage to parse
51 */
52 void vivaldi_hid_feature_mapping(struct vivaldi_data *data,
53 struct hid_device *hdev,
54 struct hid_field *field,
55 struct hid_usage *usage)
56 {
57 struct hid_report *report = field->report;
58 int fn_key;
59 int ret;
60 u32 report_len;
61 u8 *report_data, *buf;
62
63 if (field->logical != HID_USAGE_FN_ROW_PHYSMAP ||
64 (usage->hid & HID_USAGE_PAGE) != HID_UP_ORDINAL)
65 return;
66
67 fn_key = (usage->hid & HID_USAGE);
68 if (fn_key < VIVALDI_MIN_FN_ROW_KEY || fn_key > VIVALDI_MAX_FN_ROW_KEY)
69 return;
70 if (fn_key > data->num_function_row_keys)
71 data->num_function_row_keys = fn_key;
72
> 73 report_data = buf = hid_alloc_report_buf(report, GFP_KERNEL);
74 if (!report_data)
75 return;
76
77 report_len = hid_report_len(report);
78 if (!report->id) {
79 /*
80 * hid_hw_raw_request() will stuff report ID (which will be 0)
81 * into the first byte of the buffer even for unnumbered
82 * reports, so we need to account for this to avoid getting
83 * -EOVERFLOW in return.
84 * Note that hid_alloc_report_buf() adds 7 bytes to the size
85 * so we can safely say that we have space for an extra byte.
86 */
87 report_len++;
88 }
89
> 90 ret = hid_hw_raw_request(hdev, report->id, report_data,
91 report_len, HID_FEATURE_REPORT,
92 HID_REQ_GET_REPORT);
93 if (ret < 0) {
94 dev_warn(&hdev->dev, "failed to fetch feature %d\n",
95 field->report->id);
96 goto out;
97 }
98
99 if (!report->id) {
100 /*
101 * Undo the damage from hid_hw_raw_request() for unnumbered
102 * reports.
103 */
104 report_data++;
105 report_len--;
106 }
107
> 108 ret = hid_report_raw_event(hdev, HID_FEATURE_REPORT, report_data,
109 report_len, 0);
110 if (ret) {
111 dev_warn(&hdev->dev, "failed to report feature %d\n",
112 field->report->id);
113 goto out;
114 }
115
116 data->function_row_physmap[fn_key - VIVALDI_MIN_FN_ROW_KEY] =
117 field->value[usage->usage_index];
118
119 out:
120 kfree(buf);
121 }
122 EXPORT_SYMBOL_GPL(vivaldi_hid_feature_mapping);
123 #endif /* CONFIG_HID */
124
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2022-02-05 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 20:20 [PATCH 0/5] Input/HID: Consolidate ChromeOS Vivaldi keyboard logic Stephen Boyd
2022-02-04 20:20 ` [PATCH 1/5] Input: atkbd: Convert function_row_physmap to u16 array Stephen Boyd
2022-02-04 20:20 ` [PATCH 2/5] Input: Extract ChromeOS vivaldi physmap show function Stephen Boyd
2022-02-04 20:20 ` [PATCH 3/5] HID: Extract vivaldi hid feature mapping for use in hid-hammer Stephen Boyd
2022-02-05 0:15 ` kernel test robot [this message]
2022-02-05 2:19 ` Stephen Boyd
2022-02-05 3:19 ` kernel test robot
2022-02-04 20:20 ` [PATCH 4/5] HID: google: Add support for vivaldi to hid-hammer Stephen Boyd
2022-02-04 20:20 ` [PATCH 5/5] HID: google: modify HID device groups of eel Stephen Boyd
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=202202050807.BvUyitVE-lkp@intel.com \
--to=lkp@intel.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dianders@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seobrien@chromium.org \
--cc=swboyd@chromium.org \
--cc=xiazhengqiao@huaqin.corp-partner.google.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;
as well as URLs for NNTP newsgroup(s).