Set disconnected flag in struct usbhid when a usb device
is removed. Check for disconnected flag before sending urb
requests. This prevents a kernel panic when a hid driver calls
hid_hw_request() after removing a usb device.
Signed-off-by: Reyad Attiyat
---
drivers/hid/usbhid/hid-core.c | 6
RMI4 Function 0x30 provides support for GPIOs, LEDs and mechanical
buttons. In particular, the mechanical button support is used in
an increasing number of touchpads.
Signed-off-by: Andrew Duggan
Signed-off-by: Allie Xiong
Acked-by: Christopher Heiny
---
I discovered that the v3 version of thi
> "Waiman" == Waiman Long writes:
Waiman> On 07/24/2014 02:36 PM, Peter Zijlstra wrote:
>> On Thu, Jul 24, 2014 at 11:18:16AM -0700, Linus Torvalds wrote:
>>> On Thu, Jul 24, 2014 at 5:58 AM, Peter Zijlstra
>>> wrote:
So going by the nifty picture rostedt made:
[ 61.454336
On Thu, Jul 24, 2014 at 04:38:28PM -0400, Waiman Long wrote:
> Borislav, can you apply the following patch on top of the lockdep
> patch to see if it can fix the problem?
It is too late here for me to test anything but the ingridients to
reproduce are nothing special. Just grab a kvm guest and pic
On 07/24/2014 07:47 AM, Nick Dyer wrote:
On 23/07/14 18:22, Stephen Warren wrote:
That didn't make any difference.
I also tried the tool interactively. the "Display raw (M)essages" option
never displayed anything, and the couple of self-tests I tried just
timed out. "Read (I)nfo block" did disp
On Thu, Jul 24, 2014 at 12:58 PM, Dmitry Torokhov
wrote:
>
> On Thu, Jul 24, 2014 at 03:43:52PM -0400, Benjamin Tissoires wrote:
> > On Jul 24 2014 or thereabouts, Dmitry Torokhov wrote:
> > > Hi Benjamin,
> > >
> > > On Thu, Jul 24, 2014 at 02:14:02PM -0400, Benjamin Tissoires wrote:
> > > > +
On 07/24/2014 02:36 PM, Peter Zijlstra wrote:
On Thu, Jul 24, 2014 at 11:18:16AM -0700, Linus Torvalds wrote:
On Thu, Jul 24, 2014 at 5:58 AM, Peter Zijlstra wrote:
So going by the nifty picture rostedt made:
[ 61.454336]CPU0CPU1
[ 61.454336]
wacom_wac.h will be moving to drivers/hid. Since we only need 3 definitions
from it let's simply copy them over.
Signed-off-by: Dmitry Torokhov
---
drivers/input/tablet/wacom_serial4.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/input/tablet/wacom_serial4.c
b/drivers/input/
On Tue, Jul 15, 2014 at 02:45:46PM -0400, Benjamin Tissoires wrote:
> wacom.ko is now a full HID driver, we have to move it into the proper
> subdirectory: drivers/hid.
>
> Signed-off-by: Benjamin Tissoires
Hmm, this breaks the new wacom_serial4 driver that wants wacom_wac.h. It
looks like it on
On 07/23/2014 06:41 PM, Christopher Heiny wrote:
On 07/22/2014 11:11 PM, Dmitry Torokhov wrote:
Signed-off-by: Dmitry Torokhov
I've reviewed this, and can say:
Acked-by: Christopher Heiny
but I haven't had a chance to apply it to my build tree.
Andrew - I'll be OOO for a couple of days.
On Jul 24 2014 or thereabouts, Dmitry Torokhov wrote:
> On Thu, Jul 24, 2014 at 03:43:52PM -0400, Benjamin Tissoires wrote:
> > On Jul 24 2014 or thereabouts, Dmitry Torokhov wrote:
> > > Hi Benjamin,
> > >
> > > On Thu, Jul 24, 2014 at 02:14:02PM -0400, Benjamin Tissoires wrote:
> > > > +
On Thu, Jul 24, 2014 at 03:43:52PM -0400, Benjamin Tissoires wrote:
> On Jul 24 2014 or thereabouts, Dmitry Torokhov wrote:
> > Hi Benjamin,
> >
> > On Thu, Jul 24, 2014 at 02:14:02PM -0400, Benjamin Tissoires wrote:
> > > + } else if (features->type == GRAPHIRE_BT) {
> > > +
On Jul 24 2014 or thereabouts, Dmitry Torokhov wrote:
> Hi Benjamin,
>
> On Thu, Jul 24, 2014 at 02:14:02PM -0400, Benjamin Tissoires wrote:
> > First, merge the Graphire BT tablet.
> >
> > Signed-off-by: Benjamin Tissoires
> > ---
> >
> > changes in v2:
> > - simplified because part of it has
Hi Benjamin,
On Thu, Jul 24, 2014 at 02:14:02PM -0400, Benjamin Tissoires wrote:
> First, merge the Graphire BT tablet.
>
> Signed-off-by: Benjamin Tissoires
> ---
>
> changes in v2:
> - simplified because part of it has been splitted out in the previous commit.
>
> drivers/hid/hid-core.c |
Add the TI drv260x haptics/vibrator driver.
This device uses the input force feedback
to produce a wave form to driver an
ERM or LRA actuator device.
The initial driver supports the devices
real time playback mode. But the device
has additional wave patterns in ROM.
This functionality will be ad
On Thu, Jul 24, 2014 at 11:18:16AM -0700, Linus Torvalds wrote:
> On Thu, Jul 24, 2014 at 5:58 AM, Peter Zijlstra wrote:
> >
> > So going by the nifty picture rostedt made:
> >
> > [ 61.454336]CPU0CPU1
> > [ 61.454336]
> > [ 61.
Hi Dmitry,
this is the second series I told you about for wacom.ko. This series also have
a good number of removed lines of code. \o/
The first patch is Jason's one that I finally decided to take with me. His
previous submission still applied correctly even after the moving of the files
(git is d
On Thu, Jul 24, 2014 at 5:58 AM, Peter Zijlstra wrote:
>
> So going by the nifty picture rostedt made:
>
> [ 61.454336]CPU0CPU1
> [ 61.454336]
> [ 61.454336] lock(&(&p->alloc_lock)->rlock);
> [ 61.454336]
From: Jason Gerecke
Signed-off-by: Jason Gerecke
Rebased in drivers/hid/
Signed-off-by: Benjamin Tissoires
---
changes in v2:
- rebased in drivers/hid/
drivers/hid/wacom_wac.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hid/wacom_wac.c b/drivers/hid/wacom_wac.
The current implementation uses "wacom_battery" as a generic name for
batteries. This prevents us to have two Wacom devices with a battery
attached as the power system will complain about the name which is already
registered.
Use an incremental name for each battery attached.
Related bug:
https:/
This solves a bug with the wireless receiver:
- at plug, the wireless receiver does not know which Wacom device it is
connected to, so it does not actually creates all the LEDs
- when the tablet connects, wacom->wacom_wac.features.type is set to the
proper device so that wacom_wac can understan
Signed-off-by: Benjamin Tissoires
---
new in v2:
- I thought it was interesting to bump the number of the release
drivers/hid/wacom.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/wacom.h b/drivers/hid/wacom.h
index 2b5562b..e354972 100644
--- a/drivers/hid/wacom.h
+++ b/dr
- Reports the current status of the battery (discharging, charging, full).
- Also notify the upower daemon when there is a change in the battery
value.
- keep the battery value as a percentage, not the raw value
- add WACOM_QUIRK_BATTERY to easily add a battery to a device (required
for Bluetoo
First, merge the Graphire BT tablet.
Signed-off-by: Benjamin Tissoires
---
changes in v2:
- simplified because part of it has been splitted out in the previous commit.
drivers/hid/hid-core.c | 1 -
drivers/hid/hid-wacom.c | 1 -
drivers/hid/wacom_sys.c | 42 +
drivers/hi
A good point of this change is that now, the Intuos4 bluetooth can handle
the different tools (artpen, airbrush, mice), and we get a common interface
between USB and BT for accessing the LEDs/OLEDs.
Signed-off-by: Benjamin Tissoires
---
no or little changes in v2
drivers/hid/hid-core.c | 1 -
This is used by HID Bluetooth devices but also add some more information
to the USB Wireless Receiver.
We are just porting the bits from hid-wacom.c to the common driver here.
Signed-off-by: Benjamin Tissoires
---
new in v2
drivers/hid/wacom.h | 1 +
drivers/hid/wacom_sys.c | 58 +
Now that wacom is a hid driver, there is no point in having a separate
driver for bluetooth devices.
This patch prepares the common paths of Bluetooth devices in the
common wacom driver.
It also adds the sysfs file "speed" used by Bluetooth devices.
Signed-off-by: Benjamin Tissoires
---
new in v
Bluetooth Wacom tablets are now handled by the regular wacom.ko driver.
Remove the now useless hid-wacom driver.
Signed-off-by: Benjamin Tissoires
---
no changes in v2
drivers/hid/Kconfig | 10 +-
drivers/hid/Makefile| 3 +-
drivers/hid/hid-wacom.c | 971
Hi,
On Tue, Jan 07, 2014 at 11:08:03AM +0800, Duson Lin wrote:
> +/*
> + **
> + * General functions
> + **
> + */
> +/*
> + * (value from firmware) * 10 + 790 = dpi
> + *
On Thu, Jul 24, 2014 at 02:58:14PM +0200, Peter Zijlstra wrote:
> Of course we should have made the lockdep change before merging qrwlock,
> and that's entirely my fail, but with qrwlock in these new semantics are
> already a reality.
>
> We could of course disable qrwlock until all such issues ar
Hi,
I have a HP EliteBook Revolve 810 (which is a hybrid laptop/tablet) with
the HP active pen that goes with it. I have installed fedora 20 (kernel
3.15.6-200.fc20.x86_64) on this, and the pen does not work out of the box.
Playing with evtest, it appears that the kernel reports the X coordinate i
On 07/24/2014 09:10 AM, Nick Dyer wrote:
> On 23/07/14 22:36, Stephen Warren wrote:
>> Hmm. It looks like the version of this patch that was actually applied
>> varies quite a bit from what was posted, in particular in the
>> implementation and call site of mxt_parse_dt(). It'd be nice if the
>> co
On 23/07/14 22:50, Dmitry Torokhov wrote:
> I think having control flow with 2 goto/labels/flags is quite hard to read,
> this version is a bit more readable IMO.
>
> Signed-off-by: Dmitry Torokhov
Yes, this looks much clearer to me. Although I can't see anything wrong
looking at it, I think I s
On 24/07/14 00:29, Dmitry Torokhov wrote:
> Let's split config update code a bit so it is hopefully a bit easier to
> read. Also, the firmware update callback should be the entity releasing
> firmware blob, not lower layers.
>
> Signed-off-by: Dmitry Torokhov
Thanks, this is obviously sensible.
On 23/07/14 22:36, Stephen Warren wrote:
> Hmm. It looks like the version of this patch that was actually applied
> varies quite a bit from what was posted, in particular in the
> implementation and call site of mxt_parse_dt(). It'd be nice if the
> commit log had been adjusted to mention this, so
On 23/07/14 18:22, Stephen Warren wrote:
> That didn't make any difference.
>
> I also tried the tool interactively. the "Display raw (M)essages" option
> never displayed anything, and the couple of self-tests I tried just
> timed out. "Read (I)nfo block" did display some values that seemed like
>
On Wed, Jul 23, 2014 at 7:36 PM, Dmitry Torokhov
wrote:
> Wire up open/close so we do not try to send events until someone uses them;
> this also allows us to remove micro_ts_remove() and rely fully on managed
> resources.
>
> Signed-off-by: Dmitry Torokhov
Looks good.
Acked-by: Linus Walleij
On Thu, Jul 24, 2014 at 02:25:13PM +0200, Borislav Petkov wrote:
> On Thu, Jul 24, 2014 at 10:41:27AM +0200, Borislav Petkov wrote:
> > you can easily reproduce by booting a kvm guest with rc6 + tip/master.
>
> Right, so reverting
>
> 586fefe5bbdc ("locking/selftest: Support queued rwlock")
> e06
On Thu, Jul 24, 2014 at 10:41:27AM +0200, Borislav Petkov wrote:
> you can easily reproduce by booting a kvm guest with rc6 + tip/master.
Right, so reverting
586fefe5bbdc ("locking/selftest: Support queued rwlock")
e0645a111cb4 ("locking/lockdep: Restrict the use of recursive read_lock() with
qr
On Thu, Jul 24, 2014 at 08:43:53AM +0200, Peter Zijlstra wrote:
> On Wed, Jul 23, 2014 at 05:37:43PM -0700, Linus Torvalds wrote:
> > On Wed, Jul 23, 2014 at 2:53 AM, Borislav Petkov wrote:
> > >
> > > Well, it looks like we f*cked up something after -rc5 since I'm starting
> > > to see lockdep sp
40 matches
Mail list logo
