From: Vlastimil Babka <vbabka@suse.cz>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"Pavel Machek" <pavel@ucw.cz>,
"Pali Rohár" <pali.rohar@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
rpurdie@rpsys.net,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 1/3] Input: export LEDs as class devices in sysfs
Date: Tue, 21 Jul 2015 13:14:39 +0200 [thread overview]
Message-ID: <55AE299F.3010002@suse.cz> (raw)
In-Reply-To: <20150609174211.GH6338@dtor-ws>
On 06/09/2015 07:42 PM, Dmitry Torokhov wrote:
> From: Samuel Thibault <samuel.thibault@ens-lyon.org>
>
> This change creates a new input handler called "leds" that exports LEDs on input
> devices as standard LED class devices in sysfs and allows controlling their
> ptate via sysfs or via any of the standard LED triggers. This allows to
> re-purpose and reassign LDEs on the keyboards to represent states other
> than the standard keyboard states (CapsLock, NumLock, etc).
>
> The old API of controlling input LEDs by writing into /dev/input/eventX
> devices is still present and will take precedence over acessing via LEDs
> subsystem (i.e. it may override state set by a trigger). If input device is
> "grabbed" then requests coming through LED subsystem will be ignored.
>
> Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
> + led_no = 0;
> + for_each_set_bit(led_code, dev->ledbit, LED_CNT) {
> + struct input_led *led = &leds->leds[led_no];
> +
> + led->handle = &leds->handle;
> + led->code = led_code;
> +
> + if (WARN_ON(!input_led_info[led_code].name))
> + continue;
> +
Hi,
I get several warnings on booting 4.2-rc2 here. Should I be worried?
[ 2.782432] ------------[ cut here ]------------
[ 2.782440] WARNING: CPU: 2 PID: 356 at ../drivers/input/input-leds.c:115 input_leds_connect+0x22b/0x260()
[ 2.782441] Modules linked in: btrfs xor raid6_pq crc32c_intel radeon i2c_algo_bit sr_mod cdrom drm_kms_helper ttm e1000e drm xhci_pci ptp pps_core xhci_hcd sg
[ 2.782453] CPU: 2 PID: 356 Comm: kworker/2:2 Not tainted 4.2.0-rc2-1.g288d56b-desktop #1
[ 2.782454] Hardware name: Dell Inc. OptiPlex 9010/0M9KCM, BIOS A13 03/27/2013
[ 2.782458] Workqueue: usb_hub_wq hub_event
[ 2.782459] ffffffff81a917b7 ffff880213ecf298 ffffffff8169f19d 0000000000000007
[ 2.782462] 0000000000000000 ffff880213ecf2d8 ffffffff810674f6 ffff880213ecf2f8
[ 2.782463] ffff8802132fb000 0000000000000003 000000000000000b ffff8800369ff000
[ 2.782465] Call Trace:
[ 2.782470] [<ffffffff8169f19d>] dump_stack+0x4c/0x6e
[ 2.782474] [<ffffffff810674f6>] warn_slowpath_common+0x86/0xc0
[ 2.782476] [<ffffffff810675ea>] warn_slowpath_null+0x1a/0x20
[ 2.782478] [<ffffffff8152ccdb>] input_leds_connect+0x22b/0x260
[ 2.782480] [<ffffffff815281b2>] input_attach_handler+0x1a2/0x1f0
[ 2.782483] [<ffffffff81528640>] input_register_device+0x440/0x4f0
[ 2.782486] [<ffffffff8156e494>] hidinput_connect+0x334/0x5d0
[ 2.782488] [<ffffffff815683d4>] hid_connect+0x324/0x400
[ 2.782490] [<ffffffff81578b7a>] ? usbhid_start+0x54a/0x780
[ 2.782492] [<ffffffff81569858>] hid_device_probe+0x118/0x140
[ 2.782495] [<ffffffff81482134>] driver_probe_device+0x1f4/0x460
[ 2.782497] [<ffffffff814824b9>] __device_attach_driver+0x79/0xa0
[ 2.782499] [<ffffffff81482440>] ? __driver_attach+0xa0/0xa0
[ 2.782501] [<ffffffff8147ff6b>] bus_for_each_drv+0x5b/0x90
[ 2.782502] [<ffffffff81481e58>] __device_attach+0xa8/0x120
[ 2.782504] [<ffffffff81482523>] device_initial_probe+0x13/0x20
[ 2.782506] [<ffffffff8148116a>] bus_probe_device+0x9a/0xb0
[ 2.782508] [<ffffffff8147edee>] device_add+0x3fe/0x670
[ 2.782511] [<ffffffff812bf9d3>] ? debugfs_create_file+0xd3/0x110
[ 2.782513] [<ffffffff8156956c>] hid_add_device+0xcc/0x2a0
[ 2.782515] [<ffffffff81578404>] usbhid_probe+0x2e4/0x410
[ 2.782518] [<ffffffff814fe0d2>] usb_probe_interface+0x1b2/0x2d0
[ 2.782519] [<ffffffff81482134>] driver_probe_device+0x1f4/0x460
[ 2.782521] [<ffffffff814824b9>] __device_attach_driver+0x79/0xa0
[ 2.782523] [<ffffffff81482440>] ? __driver_attach+0xa0/0xa0
[ 2.782525] [<ffffffff8147ff6b>] bus_for_each_drv+0x5b/0x90
[ 2.782526] [<ffffffff81481e58>] __device_attach+0xa8/0x120
[ 2.782528] [<ffffffff81482523>] device_initial_probe+0x13/0x20
[ 2.782530] [<ffffffff8148116a>] bus_probe_device+0x9a/0xb0
[ 2.782531] [<ffffffff8147edee>] device_add+0x3fe/0x670
[ 2.782533] [<ffffffff814fbfb1>] usb_set_configuration+0x501/0x8e0
[ 2.782535] [<ffffffff81253efe>] ? kernfs_add_one+0xee/0x140
[ 2.782537] [<ffffffff8150656e>] generic_probe+0x2e/0x80
[ 2.782539] [<ffffffff814fdee2>] usb_probe_device+0x32/0x70
[ 2.782541] [<ffffffff81482134>] driver_probe_device+0x1f4/0x460
[ 2.782542] [<ffffffff814824b9>] __device_attach_driver+0x79/0xa0
[ 2.782544] [<ffffffff81482440>] ? __driver_attach+0xa0/0xa0
[ 2.782546] [<ffffffff8147ff6b>] bus_for_each_drv+0x5b/0x90
[ 2.782547] [<ffffffff81481e58>] __device_attach+0xa8/0x120
[ 2.782549] [<ffffffff81482523>] device_initial_probe+0x13/0x20
[ 2.782551] [<ffffffff8148116a>] bus_probe_device+0x9a/0xb0
[ 2.782552] [<ffffffff8147edee>] device_add+0x3fe/0x670
[ 2.782554] [<ffffffff814f15c6>] ? usb_new_device+0x216/0x5d0
[ 2.782556] [<ffffffff814f164e>] usb_new_device+0x29e/0x5d0
[ 2.782559] [<ffffffff8148cff1>] ? pm_runtime_set_autosuspend_delay+0x51/0x60
[ 2.782561] [<ffffffff81506612>] ? __usb_detect_quirks+0x52/0x110
[ 2.782563] [<ffffffff814f2c3f>] hub_port_connect+0x31f/0x9c0
[ 2.782565] [<ffffffff814f39b1>] hub_event+0x6d1/0xb10
[ 2.782568] [<ffffffff8107f039>] process_one_work+0x159/0x470
[ 2.782570] [<ffffffff8107f398>] worker_thread+0x48/0x4a0
[ 2.782572] [<ffffffff8107f350>] ? process_one_work+0x470/0x470
[ 2.782574] [<ffffffff8107f350>] ? process_one_work+0x470/0x470
[ 2.782576] [<ffffffff81085089>] kthread+0xc9/0xe0
[ 2.782579] [<ffffffff81084fc0>] ? kthread_worker_fn+0x170/0x170
[ 2.782581] [<ffffffff816a55df>] ret_from_fork+0x3f/0x70
[ 2.782583] [<ffffffff81084fc0>] ? kthread_worker_fn+0x170/0x170
[ 2.782585] ---[ end trace ce1cb4ca0f2cbd0b ]---
[ 2.782586] ------------[ cut here ]------------
next prev parent reply other threads:[~2015-07-21 11:14 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 21:43 [PATCH 0/3] Switch input leds over to standard LED class devices Dmitry Torokhov
2015-06-08 21:43 ` [PATCH 1/3] Input: export LEDs as class devices in sysfs Dmitry Torokhov
2015-06-09 13:19 ` Samuel Thibault
2015-06-09 13:27 ` Samuel Thibault
2015-06-09 16:50 ` Dmitry Torokhov
2015-06-09 17:16 ` Samuel Thibault
2015-06-09 16:49 ` Dmitry Torokhov
2015-06-09 17:22 ` Samuel Thibault
2015-06-09 17:32 ` Dmitry Torokhov
2015-06-10 6:34 ` Pavel Machek
2015-06-09 17:42 ` [PATCH v2 " Dmitry Torokhov
2015-06-10 0:32 ` Samuel Thibault
2015-06-10 1:24 ` Dmitry Torokhov
2015-06-11 17:51 ` Pavel Machek
2015-06-15 10:03 ` Pavel Machek
2015-06-15 10:51 ` Pali Rohár
2015-07-21 11:14 ` Vlastimil Babka [this message]
2015-07-21 17:01 ` Dmitry Torokhov
2015-07-21 21:08 ` Pavel Machek
2015-07-22 13:12 ` Vlastimil Babka
2015-07-22 18:55 ` Jiri Kosina
2015-07-23 5:19 ` Vlastimil Babka
2015-07-23 5:42 ` Jiri Kosina
2015-07-22 14:41 ` Vlastimil Babka
2015-07-22 19:49 ` Jiri Kosina
2015-07-22 21:47 ` Pavel Machek
2015-07-22 21:50 ` Jiri Kosina
2015-07-22 21:49 ` Dmitry Torokhov
2015-07-22 22:01 ` Jiri Kosina
2015-06-08 21:43 ` [PATCH 2/3] tty/vt/keyboard: define LED triggers for VT LED states Dmitry Torokhov
2015-06-08 21:43 ` [PATCH 3/3] tty/vt/keyboard: define LED triggers for VT keyboard lock states Dmitry Torokhov
2015-06-08 22:58 ` [PATCH 0/3] Switch input leds over to standard LED class devices Bastien Nocera
2015-06-08 23:16 ` Dmitry Torokhov
2015-06-09 10:54 ` Pavel Machek
2015-06-09 11:12 ` Pavel Machek
2015-06-09 11:22 ` Pali Rohár
2015-06-09 11:28 ` Pavel Machek
2015-06-09 12:22 ` Samuel Thibault
2015-06-09 11:26 ` Pavel Machek
2015-06-09 16:40 ` Dmitry Torokhov
2015-06-09 12:20 ` Samuel Thibault
2015-06-09 16:18 ` Pavel Machek
2015-06-09 16:32 ` Dmitry Torokhov
2015-06-09 16:37 ` Dmitry Torokhov
2015-06-09 13:42 ` Samuel Thibault
2015-06-09 13:50 ` Pali Rohár
2015-06-09 14:05 ` Samuel Thibault
[not found] ` <20090205113908.GA14224@const.inria.fr>
2015-06-09 14:17 ` caps lock led does not show up Samuel Thibault
2015-06-09 16:03 ` Bug#514464: " Anton Zinoviev
2015-06-11 8:08 ` Samuel Thibault
2015-06-11 14:28 ` Samuel Thibault
2015-06-11 15:37 ` Samuel Thibault
2015-06-25 15:41 ` Samuel Thibault
2015-07-02 16:39 ` Anton Zinoviev
2015-07-02 16:50 ` Samuel Thibault
2015-08-31 8:33 ` Samuel Thibault
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=55AE299F.3010002@suse.cz \
--to=vbabka@suse.cz \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=samuel.thibault@ens-lyon.org \
/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).