Re: [GIT] HID

From: Ingo Molnar
Date: Fri May 10 2013 - 07:52:17 EST



* Jiri Kosina <jkosina@xxxxxxx> wrote:

> On Fri, 10 May 2013, Ingo Molnar wrote:
>
> > hi Jiri,
> >
> > * Jiri Kosina <jkosina@xxxxxxx> wrote:
> >
> > > Linus,
> > >
> > > please pull from
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
> > >
> > > to receive HID subsystem updates for 3.10. Highlights:
> > >
> > >
> > > - hid driver transport cleanup, finalizing the long-desired decoupling of
> > > core from transport layers, by Benjamin Tissoires and Henrik Rydberg
> > > - support for hybrid finger/pen multitouch HID devices, by Benjamin
> > > Tissoires
> > > - fix for long-standing issue in Logitech unifying driver sometimes not
> > > inializing properly due to device specifics, by Andrew de los Reyes
> > > - Wii remote driver updates to support 2nd generation of devices, by David
> > > Herrmann
> > > - support for Apple IR remote
> > > - roccat driver now supports new devices (Roccat Kone Pure, IskuFX), by
> > > Stefan Achatz
> > > - debugfs locking fixes in hid debug interface, by Jiri Kosina
> >
> > FYI, there's a new HID related lockdep and RCU splat upstream, probably
> > relatd to the debugfs locking fixes:
> >
> > [ 79.088631] ======================================================
> > [ 79.088631] [ INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected ]
> > [ 79.088631] 3.9.0-13694-g7cf229a-dirty #224212 Tainted: G W
> > [ 79.088631] ------------------------------------------------------
> > [ 79.088631] swapper/0/1 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
> > [ 79.088631] (&hdev->debug_list_lock){+.+...}, at: [<ffffffff82e510d9>] hid_debug_event+0x2e/0xd0
> > [ 79.088631]
> >
> > See the full bootlog below. It's from an allyesconfig x86-64 bootup log.
>
> Hi Ingo,
>
> thanks for the report. I have a fix for this in my tree already and am
> going to send pull request to Linus shortly.

Great, thanks!

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/