Hi!
>From the backtrace, it looks evdev related...?
Oct 4 00:59:47 duo wpa_supplicant[3824]: wlan0: SME: Trying to authenticate
with 00:11:95:05:30:d7 (SSID='pavel' freq=2412 MHz)
Oct 4 00:59:47 duo wpa_supplicant[3824]: wlan0: Trying to associate with
00:11:95:05:30:d7 (SSID='pavel' freq=24
out, otherwise we will try copying too much and end up
with up with a page fault.
Reported-by: Pavel Machek
Signed-off-by: Dmitry Torokhov
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe fr
On Mon 2014-10-06 14:03:58, Dmitry Torokhov wrote:
> On Mon, Oct 06, 2014 at 10:45:26PM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > > From the backtrace, it looks evdev related...?
> > >
> > > Hmm, looks like it...
> >
> > I don&#
On Mon 2014-10-06 14:31:15, Dmitry Torokhov wrote:
> On Mon, Oct 06, 2014 at 11:14:30PM +0200, Pavel Machek wrote:
> > On Mon 2014-10-06 14:03:58, Dmitry Torokhov wrote:
> > > On Mon, Oct 06, 2014 at 10:45:26PM +0200, Pavel Machek wrote:
> > > > Hi!
> > >
On Fri 2014-10-10 13:51:31, Dmitry Torokhov wrote:
> Active multiplexing is a nice feature as it allows several pointing devices
> (such as touchpad and external mouse) use their native protocols at the
> same time. Unfortunately many manufacturers do not implement the feature
> properly even thoug
Hi!
> I'm trying to find out which subsystem maintainer I should be talking to -
> apologies if I'm addressing the wrong people.
>
> There is a model for doing touch processing where the touch controller
> becomes a much simpler device which sends out raw acquisitions (over SPI
> at up to 1Mbps
Hi!
I get this. Before I start patching it, perhaps someone has fixed it
already?
Pavel
CC drivers/input/touchscreen/tsc2005.o
drivers/input/touchscreen/tsc2005.c: In function
'tsc2005_disable_store':
drivers/input/touchscree
Hi, I read somewhere that strict_strtoul function was replaced by
> some kstrtol function... So maybe somebody forgot to fix tsc2005
> driver?
Yes.. there are four places in n900 patches that will need fixing.
This only applies to Pali's tree.
Signed-off-by: Pavel Machek
On Fri 2014-10-31 09:24:36, Dmitry Torokhov wrote:
> On Thu, Oct 30, 2014 at 12:25:06PM -0700, Dmitry Torokhov wrote:
> > On Thu, Oct 30, 2014 at 12:06:03PM -0700, Linus Torvalds wrote:
> > > On Thu, Oct 30, 2014 at 11:03 AM, Dmitry Torokhov
> > > wrote:
> > > >
> > > > Linus, any guidance here? C
Implement disable attribute for tsc2005 touchscreen. It is useful to
avoid wakeups when phone is in the pocket.
Signed-off-by: Pavel Machek
---
[This is from Pali's n900 tree that is GPL, so that is okay, but maybe
I should get his sign-off here?]
diff --git a/drivers/input/touchs
On Sun 2014-11-23 14:41:17, Pali Rohár wrote:
> Hello,
>
> pressing some keys on laptops could cause some side effects.
>
> Example scenario 1:
>
> Laptop has Fn key for enabling/disabling WIFI and when that key
> is pressed BIOS is doing two things:
>
> 1) Switch hard rfkill state of WIFI
> 2
On Sat 2014-11-29 18:24:03, Pali Rohár wrote:
> Hello,
>
> there is request to introduce some option (via sysfs) to disable
> one input device. Originally it was for tsc2005 touchscreen found
> on Nokia N900 cellphone. Use case is to completely disable
> touchscreen when phone is in pocket or w
On Thu 2014-03-27 02:08:17, Pali Rohár wrote:
> 2014-03-16 11:19 GMT+01:00 Samuel Thibault :
> > Pali Rohár, le Sun 16 Mar 2014 11:16:25 +0100, a écrit :
> >> Hello, what happened with this patch? Is there any problem with accepting
> >> it?
> >
> > Dmitry finding time to review it, I guess.
> Dm
Hi!
>
> Input: misc - Add driver for Intel Bay Trail GPIO buttons
>
> From: Lejun Zhu
>
> This patch adds support for the GPIO buttons on some Intel Bay Trail
> tablets originally running Windows 8. The ACPI description of these
> buttons follows "Windows ACPI Design Guide for SoC Platforms".
On Sat 2014-04-26 01:56:19, Sebastian Reichel wrote:
> Add devicetree binding documentation for TSC2005 touchscreen.
>
Reviewed-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
0xfff
> +#define TSC2005_DEF_X_FUZZ 4
> +#define TSC2005_DEF_Y_FUZZ 8
> +#define TSC2005_DEF_P_FUZZ 2
> +#define TSC2005_DEF_RESISTOR 280
>
IMO using defines insteaed of plain numbers does not help readability much,
but
Reviewed
On Sat 2014-04-26 01:56:17, Sebastian Reichel wrote:
> Simplify the driver by using managed resources for memory allocation of
> internal struct, input device allocation and irq request.
>
> Signed-off-by: Sebastian Reichel
Reviewed-by: Pavel Machek
--
(english) http://www.liv
On Sat 2014-04-26 01:56:16, Sebastian Reichel wrote:
> Change some dev_dbg() invocations to dev_err() ones, because they
> are supposed to output error messages.
>
> Signed-off-by: Sebastian Reichel
Reviewed-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelm
t interpret the axis inversion properties,
> since there is no matching flag in the generic linux input device.
>
> Signed-off-by: Sebastian Reichel
Reviewed-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/
On Thu 2014-06-12 23:34:12, Janne Kanniainen wrote:
> This driver adds support for USB controlled led panels that exists in
> MSI GT683R laptop
Hi!
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-class-hid-driver-gt683r
> @@ -0,0 +1,10 @@
> +What:/sys/class/hidraw//device
Hi!
> This gives the userspace (Replicant) a chance to fully handle the
> pm_wakeup_event, before autosleep suspends the system alltogether
> again.
>
> This fixes suspend/resume on the OpenPhoenux GTA04, in combination with
> the Replicant 4.2.2 userspace, which needs to execute this to stay
> a
Hi!
> >> This gives the userspace (Replicant) a chance to fully handle the
> >> pm_wakeup_event, before autosleep suspends the system alltogether
> >> again.
> >>
> >> This fixes suspend/resume on the OpenPhoenux GTA04, in combination with
> >> the Replicant 4.2.2 userspace, which needs to execut
Hi!
On Mon 2012-12-03 23:58:48, Alan Cox wrote:
> On 3 Dec 2012 16:19:11 -0500
> "George Spelvin" wrote:
>
> > (Not sure who owns this; Cc: to the last few people to touch
> > drivers/tty/vt/keyboard.c.)
>
> linux-input is probably the best place to discuss this
Added few more ccs. Yes, I see t
On Sun 2013-03-24 11:30:18, Pavel Machek wrote:
> Hi!
> On Mon 2012-12-03 23:58:48, Alan Cox wrote:
> > On 3 Dec 2012 16:19:11 -0500
> > "George Spelvin" wrote:
> >
> > > (Not sure who owns this; Cc: to the last few people to touch
> > >
Hi!
> Many new laptop keyboards aren't shipping with LEDs in the keys for
> caps lock, num lock, and scroll lock. They do, however, ship with many LEDs
> for specialized functions that mostly go non-utilized by any current
> Linux drivers. Having a caps lock LED is very helpful in early boot full
Hi!
> Add device tree support for twl4030 keypad driver and update the
> Documentation with twl4030 keypad device tree binding information.
>
> Tested on Nokia N900.
It looks pretty good.
> +++ b/Documentation/devicetree/bindings/input/twl4030-keypad.txt
> @@ -0,0 +1,31 @@
> +* TWL4030's Keypad
Hi!
> > > + * keypad,num-rows and keypad,num-columns are required.
> > Is "keypad," prefix neccessary here?
>
> See Documentation/devicetree/bindings/input/matrix-keymap.txt
>
> > > +Optional Properties specific to linux:
> > > +- linux,keypad-no-autorepeat: do no enable autorepeat feature.
> >
On Wed 2013-10-30 06:53:07, Grant Likely wrote:
> On Sun, 27 Oct 2013 12:47:53 +0100, Pavel Machek wrote:
> > > > > +#if IS_ENABLED(CONFIG_OF)
> > > > I'm probably missing something here, but why not #ifdef CONFIG_OF?
> > >
> > > I have been t
Hi!
> + if (of_get_property(np, "linux,input-no-autorepeat", NULL))
> + keypad_data->no_autorepeat = true;
>From 2/2:
+Optional Properties specific to linux:
+- linux,keypad-no-autorepeat: do not enable autorepeat feature.
I'm confused now.
--
(english) http://www.livejournal.
Hi!
> On Mon, Nov 11, 2013 at 11:19:41PM +0100, Pavel Machek wrote:
> > > + if (of_get_property(np, "linux,input-no-autorepeat", NULL))
> > > + keypad_data->no_autorepeat = true;
> >
> > From 2/2:
> >
> > +Optional Properties sp
Hi!
> > > DRIVER CODEDOCUMENTATION
> > > twl4030-keypad linux,input-no-autorepeat linux,keypad-no-autorepeat
> > > omap4-keypadlinux,input-no-autorepeat linux,keypad-no-autorepeat
> > > samsung-keypad linux,input-no-autorepeat linux,keyp
Hi!
> + Komunikate KIP1000 Keyboard Matrix
> +
> + -> -- 1 -- 2 -- 3 --> GPI pin 4 (0x10)
> + ||||
> + <- -- 4 -- 5 -- 6 --> GPI pin 5 (0x20)
> + ||||
> + END - 7 -- 8 -- 9 --> GPI pin 6 (0x40)
> + ||||
> + OK -- * -- 0 -- # --
power_state is being removed from kernel, this time in input.
Signed-off-by: Pavel Machek <[EMAIL PROTECTED]>
diff --git a/drivers/input/serio/i8042.c b/drivers/input/serio/i8042.c
index 2763394..3816e44 100644
--- a/drivers/input/serio/i8042.c
+++ b/drivers/input/serio/i8042.c
@@ -
; >
> > Adding Dmitry and linux-input.
>
> Does the patch below help?
Yes. With this patch, my mice are back.
Tested-by: Pavel Machek
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
j Zolnierkiewicz
> Reviewed-by: Sebastian Reichel
For 1-3: Acked-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-input
On Fri 2015-01-30 15:47:58, Krzysztof Kozlowski wrote:
> Use power_supply_put() to decrement the power supply's device reference
> counter.
>
> Signed-off-by: Krzysztof Kozlowski
> Reviewed-by: Bartlomiej Zolnierkiewicz
> Reviewed-by: Sebastian Reichel
11,13,20 nothing obviously wrong. But I'm
On Fri 2015-02-06 15:43:08, Krzysztof Kozlowski wrote:
> On pią, 2015-02-06 at 14:49 +0100, Pavel Machek wrote:
> > On Fri 2015-01-30 15:47:58, Krzysztof Kozlowski wrote:
> > > Use power_supply_put() to decrement the power supply's device reference
> > > cou
On Mon 2015-02-09 11:07:12, Krzysztof Kozlowski wrote:
> On pią, 2015-02-06 at 15:59 +0100, Pavel Machek wrote:
> > On Fri 2015-02-06 15:43:08, Krzysztof Kozlowski wrote:
> > > On pią, 2015-02-06 at 14:49 +0100, Pavel Machek wrote:
> > > > On Fri 2015-01-30 15:47
On Wed 2015-01-21 20:38:46, Henrik Rydberg wrote:
> Hi Benjamin,
>
> > - there is a fragmentation problem: we would have to fix the bug in
> > xorg-synaptics (which is slowly waiting for its death), libinput,
> > ChromeOS, Qt Embedded, Kivy (I think), etc...
>
> Indeed, this is the problem I want
Hi!
I plugged in part of PS move to the PC, to let it charge. Got: full
dmesg in attachment. I believe I charged it in PC before, but it may
be year ago or more.
Ideas?
Pavel
[124225.084151] usb 2-1: USB disconnect, device number 2
Hi!
>
> The patchset fixes invalid memory accesses in certain race scenarios by
> moving ownership of struct power_supply to the core. All drivers are
> modified.
Ok, who can apply the patches? Sebastian?
Pavel
--
(english
;
> >
> > @@ -1965,6 +1965,8 @@ static int sony_probe(struct hid_device *hdev, const
> > struct hid_device_id *id)
> > return -ENOMEM;
> > }
> >
> > + spin_lock_init(&sc->lock);
> > +
> > sc->quirks = quirks;
Robert Jarzmik
Acked-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majord...@vg
Hi!
Suspend-to-RAM works on the desktop, but moon key in X no longer
triggers it. Booting to older kernel seems to fix it.
3.19+ may be 4.0-rc0, not sure. Let me try latest 4.0.
Pavel
--
(english) http://www.livejournal.com
On Fri 2015-03-13 11:12:48, Pavel Machek wrote:
> Hi!
>
> Suspend-to-RAM works on the desktop, but moon key in X no longer
> triggers it. Booting to older kernel seems to fix it.
>
> 3.19+ may be 4.0-rc0, not sure. Let me try latest 4.0.
Seems to be ok in 4.0-rc3. S
Hi!
After oopsing kernel with ps/3 peripherals, I decided to play some
more.
First "sony motion controller" (part of ps/3 move without the
led). Good news is that it no longer oopses. After pressing the PS
button, it seems to work, but it produces endless stream of events in
evtest:
Event: time
Hi!
Second "sony motion controller" (part of ps/3 move with the big
LED). The LED is something I'd really like to work.
It is detected:
[ 741.363723] input: Sony Computer Entertainment Motion Controller as
/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/0003:054C:03D5.000A/input/input19
[ 74
Hi!
After oopsing kernel with ps/3 peripherals, I decided to play some
more.
Third, regular controller. The one you don't have to dance with.
/sys/class/power_supply/*/capacity works.
again, evtest reports funny-looking multitouch events:
Event: time 1426361100.640824, -- EV_SYN --
Hi!
> After oopsing kernel with ps/3 peripherals, I decided to play some
> more.
>
> First "sony motion controller" (part of ps/3 move without the
I meant "navigation controller".
I enabled CONFIG_HID_SONY_FF, and fftest now works with the other
controller, but not work this one:
Setting maste
Hi!
> Second "sony motion controller" (part of ps/3 move with the big
> LED). The LED is something I'd really like to work.
>
> It is detected:
>
> [ 741.363723] input: Sony Computer Entertainment Motion Controller as
> /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/0003:054C:03D5.000A/input
Usage of __uX types is unneccessary in the kernel, replace it with uX.
Signed-off-by: Pavel Machek
diff --git a/drivers/hid/hid-sony.c b/drivers/hid/hid-sony.c
index 1896c01..f65e334 100644
--- a/drivers/hid/hid-sony.c
+++ b/drivers/hid/hid-sony.c
@@ -57,7 +57,7 @@
#define MAX_LEDS 4
On Mon 2015-03-16 13:55:39, Jiri Kosina wrote:
> On Sat, 14 Mar 2015, Pavel Machek wrote:
>
> > Hi!
> >
> > After oopsing kernel with ps/3 peripherals, I decided to play some
> > more.
> >
> > First "sony motion controller" (part of ps/3 move
On Tue 2015-02-10 09:14:36, Oliver Neukum wrote:
> On Mon, 2015-02-09 at 20:44 +0200, Lauri Kasanen wrote:
> > On Mon, 09 Feb 2015 11:08:01 +0100
> > Oliver Neukum wrote:
> >
> > > > + ret = usb_interrupt_msg(dev, usb_sndintpipe(dev, 0x02),
> > > > + buf2, size
On Tue 2015-03-10 00:08:43, Rafael J. Wysocki wrote:
> On Monday, March 09, 2015 11:41:12 PM Rafael J. Wysocki wrote:
> > On Monday, March 09, 2015 11:00:04 AM Dmitry Torokhov wrote:
> > > Hi Rafael,
> > >
> > > On Mon, Mar 09, 2015 at 04:19:50PM +0100, Rafael J. Wysocki wrote:
> > > > From: Rafae
Hi!
> >I am sure Frank will comment on this as well.
>
> The Dualshock 3 is a special case in that every button except for start,
> select and the PS button are both digital and analog. As such, the
> controller reports 27 axes that end up spilling over into the ABS_MT values.
> This mapping com
> > > Yeah, that works too. And you're right that there's no reason to do that
> > > for
> > > keyboard only.
> >
> > Actually, are you sure?
> >
> > Resuming on mouse click is reasonable, resuming on mouse move is not,
> > as table vibrations are likely to cause that.
>
> This is disabled by
On Thu 2015-03-19 10:14:21, Oliver Neukum wrote:
> On Mon, 2015-03-16 at 22:37 +0100, Jiri Kosina wrote:
> > On Mon, 16 Mar 2015, Pavel Machek wrote:
> >
> > > > > Oliver Neukum wrote:
> > > > >
> > > > >
On Thu 2015-03-19 10:54:22, Oliver Neukum wrote:
> On Thu, 2015-03-19 at 10:38 +0100, Pavel Machek wrote:
> > On Thu 2015-03-19 10:14:21, Oliver Neukum wrote:
> > > On Mon, 2015-03-16 at 22:37 +0100, Jiri Kosina wrote:
>
> > > > Are you sure CONFIG
ld go in AFAICT.
Signed-off-by: Pavel Machek
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 56ce8c2..a1c8b63 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1941,6 +1941,7 @@ static const struct hid_device_id
hid_have_specia
Hi!
> >I did not yet figure out how to get sensor data from the controller,
> >but it works rather well as a RGB led.
>
> Hi Pavel,
>
> From what I've read, the motion controller only sends sensor data when
> connected via bluetooth.
> Otherwise it should be in report 1 with the buttons and othe
re's the updated version. Thanks,
Signed-off-by: Pavel Machek
Pavel
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 722a925..1c5b515 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -195
Hi!
> Not sure how this is expected to work. I tried: (and did not get any
> vibrations).
Hmm. Seems I tried wrong device. But no vibrations with the right
device, either:
root@duo:/sys/class/leds/0003:054C:03D5.0002:global# echo 4 | fftest
/dev/input/event8
Force feedback test program.
HOLD FIR
This commit restores the previous behaviour, that the
> drivers default value will be used for the unspecified value.
>
> Reported-By: Pavel Machek
> Fixes: 3eea8b5d68c8 (Input: of_touchscreen - rework the DT parsing function)
> Signed-off-by: Sebastian Reichel
> ---
> drivers/i
Hi!
> I finally was able to spend some time looking over Samuel's patch set
> switching input LEDs from custom implementation over to standard LED class
> devices and I think this is the shape I am reasonably happy with. The
> changes:
Thanks!
> Please take a look and see if you see any holes.
On Tue 2015-06-09 12:54:21, Pavel Machek wrote:
> Hi!
>
> > I finally was able to spend some time looking over Samuel's patch set
> > switching input LEDs from custom implementation over to standard LED class
> > devices and I think this is the shape I am reasonabl
On Tue 2015-06-09 13:12:42, Pavel Machek wrote:
> On Tue 2015-06-09 12:54:21, Pavel Machek wrote:
> > Hi!
> >
> > > I finally was able to spend some time looking over Samuel's patch set
> > > switching input LEDs from custom implementation over to standard LE
On Tue 2015-06-09 13:22:21, Pali Rohár wrote:
> On Tuesday 09 June 2015 13:12:42 Pavel Machek wrote:
> > On Tue 2015-06-09 12:54:21, Pavel Machek wrote:
> > > I did echo kbd-capslock > trigger, but still no luck. (That might be
> > > bug in Debian, IIRC?)
> &g
Hi!
> > I finally was able to spend some time looking over Samuel's patch set
> > switching input LEDs from custom implementation over to standard LED class
> > devices and I think this is the shape I am reasonably happy with. The
> > changes:
>
> Thanks!
>
> > Please take a look and see if you
On Tue 2015-06-09 09:49:35, Dmitry Torokhov wrote:
> On Tue, Jun 09, 2015 at 03:19:55PM +0200, Samuel Thibault wrote:
> > Hello,
> >
> > Dmitry Torokhov, le Mon 08 Jun 2015 14:43:08 -0700, a écrit :
> > > 1. Instead of making LED class devices part of the input device they are
> > > implemented as
7;s give Pavel and Pali chance to test it out and let's get
> it in 4.2.
Tested-by: Pavel Machek
Acked-by: Pavel Machek
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karl
On Tue 2015-06-09 18:24:54, Dmitry Torokhov wrote:
> On Wed, Jun 10, 2015 at 02:32:32AM +0200, Samuel Thibault wrote:
> > Hello,
> >
> > Thanks for the modified version. This all seems to be working as
> > expected with multiple keyboards.
>
> Excellent. Let's give Pavel and Pali chance to test
On Tue 2015-07-21 10:01:33, Dmitry Torokhov wrote:
> On Tue, Jul 21, 2015 at 01:14:39PM +0200, Vlastimil Babka wrote:
> > On 06/09/2015 07:42 PM, Dmitry Torokhov wrote:
> > > From: Samuel Thibault
> > >
> > > This change creates a new input handler called "leds" that exports LEDs
> > > on input
On Wed 2015-07-22 21:49:06, Jiri Kosina wrote:
> On Wed, 22 Jul 2015, Vlastimil Babka wrote:
>
> > [ 101.805120] usb 3-4: new low-speed USB device number 3 using xhci_hcd
> > [ 101.979584] usb 3-4: New USB device found, idVendor=046d, idProduct=c50e
> > [ 101.979589] usb 3-4: New USB device str
On Wed 2015-07-22 15:02:02, Dmitry Torokhov wrote:
> Devices may declare more LEDs than what is known to input-leds
> (HID does this for some devices). Instead of showing ugly warnings
> on connect and, even worse, oopsing on disconnect, let's simply
> ignore LEDs that are not known to us.
>
> Rep
On Thu 2015-07-23 13:57:13, Dmitry Torokhov wrote:
> On Thu, Jul 23, 2015 at 08:19:13AM +0200, Pavel Machek wrote:
> > On Wed 2015-07-22 15:02:02, Dmitry Torokhov wrote:
> > > Devices may declare more LEDs than what is known to input-leds
> > > (HID does this for some d
On Fri 2015-07-24 10:22:04, Vlastimil Babka wrote:
> On 07/23/2015 12:02 AM, Dmitry Torokhov wrote:
> >Devices may declare more LEDs than what is known to input-leds
> >(HID does this for some devices). Instead of showing ugly warnings
> >on connect and, even worse, oopsing on disconnect, let's sim
On Mon 2015-07-27 12:17:06, Reilly Grant wrote:
> In commit 30ba2fbde1840db44 an LED class driver for this device was
> added and at the same time it was blacklisted by the hid-generic
> driver. This patch removes the device from the hid-generic driver's
> blacklist if the LED class driver is not e
On Wed 2015-07-29 12:46:59, Takashi Iwai wrote:
> Hi,
>
> while debugging a problem of X and gdm with the old systemd-210, we
> encountered a sudden death of systemd-logind, and this turned out to
> be an unexpected errno from close(). The close() call for input
> devices returns ENODEV error. T
On Sat 2015-08-01 13:44:59, Pali Rohár wrote:
> On Saturday 01 August 2015 13:22:51 Viresh Kumar wrote:
> > On 31-07-15, 09:58, Dmitry Torokhov wrote:
> > > On Fri, Jul 31, 2015 at 02:08:25PM +0530, Viresh Kumar wrote:
> > > > IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and
> > > >
> > >> In fact, then, what you need seems to be the feature discussed by Alan
> > >> and me some time ago allowing remote wakeup do be disabled for runtime
> > >> PM from user space as that in combination with autosuspend should
> > >> address your use case.
> > >
> > > I'd doubt that. Suppose you
On Wed 2015-09-09 11:20:25, Alan Stern wrote:
> On Wed, 9 Sep 2015, Rafael J. Wysocki wrote:
>
> > > The best example and actually the very specific problem we want to
> > > solve is handling touchscreens on a phone / tablet. When the screen is
> > > turned off, it is ideal to suspend the touchscr
On Mon 2015-09-21 10:38:46, Alan Stern wrote:
> On Mon, 21 Sep 2015, Pavel Machek wrote:
>
> > > > In fact, then, what you need seems to be the feature discussed by Alan
> > > > and me some time ago allowing remote wakeup do be disabled for runtime
> &g
Hi!
> > > > That, or there may be an additional value, say "aggressive", to write
> > > > to the
> > > > control file in which case it becomes just
> > > >
> > > > echo aggressive >/sys/.../power/control
> > >
> > > That said I suppose that the "off" value for the "wakeup" file might also
> >
Hi!
> > >
> > >> > This suggests we forget about power/wakeup == "off" and introduce an
> > >> > "inhibit" attribute instead.
> > >>
> > >> If we do that, can it still be regarded as a PM attribute?
> > >
> > > Why not? Consider this: Is there any reason to support inhibit when
> > > CONFIG_PM is
On Mon 2015-09-07 17:36:15, Irina Tirdea wrote:
> Signed-off-by: Irina Tirdea
> ---
> drivers/input/touchscreen/goodix.c | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
Don't.
Yes, we sometimes sort includes... to avoid patch rejects.
This is guaranteed to cause rejects.
Hi!
> > Subject: Re: [PATCH v5 1/9] Input: goodix - sort includes alphabetically
> >
> > On Mon 2015-09-07 17:36:15, Irina Tirdea wrote:
> > > Signed-off-by: Irina Tirdea
> > > ---
> > > drivers/input/touchscreen/goodix.c | 12 ++--
> > > 1 file changed, 6 insertions(+), 6 deletions(-)
86 matches
Mail list logo
