copy when
> direct filesystem lookup fails. This will make the touchscreen work OOTB
> on devices where there is a fw copy embedded in the UEFI code.
>
> Signed-off-by: Hans de Goede
Acked-by: Dmitry Torokhov
Feel free to merge with the rest of the series.
> ---
> drivers/inpu
hen
> direct filesystem lookup fails. This will make the touchscreen work OOTB
> on devices where there is a fw copy embedded in the UEFI code.
>
> Signed-off-by: Hans de Goede
Acked-by: Dmitry Torokhov
> ---
> drivers/input/touchscreen/silead.c | 2 +-
> 1 file chang
Hi Hans,
On Fri, Oct 04, 2019 at 04:50:52PM +0200, Hans de Goede wrote:
> In some cases the platform's main firmware (e.g. the UEFI fw) may contain
> an embedded copy of device firmware which needs to be (re)loaded into the
> peripheral. Normally such firmware would be part of linux-firmware, but
On Sun, Feb 18, 2018 at 05:17:46PM +0100, Marcus Folkesson wrote:
> This driver let you plug in your RC controller to the adapter and
> use it as input device in various RC simulators.
>
> Signed-off-by: Marcus Folkesson
Applied, thank you.
> ---
>
> v5:
> - Drop autosuspend support
>
On Mon, Jan 22, 2018 at 02:54:57PM +0200, Andy Shevchenko wrote:
> Instead of using PROPERTY_ENTRY_INTEGER() with explicitly supplied type,
> use PROPERTY_ENTRY_U32() dedicated macro.
>
> It will help modify internals of built-in device properties API.
>
> No functional change intended.
>
> Sign
On Wed, Jan 17, 2018 at 02:58:40PM +0100, Marcus Folkesson wrote:
> Hello Dmitry,
>
> On Tue, Jan 16, 2018 at 03:16:25PM -0800, Dmitry Torokhov wrote:
> > Hi Marcus,
> >
> > On Sat, Jan 13, 2018 at 09:15:32PM +0100, Marcus Folkesson wrote:
> > > This driver l
On Thu, Jan 18, 2018 at 04:49:03PM -0500, Jean-François Têtu wrote:
> Fix small typos in the Instructions and Uploading sections. Fix a typo in
> the start/stop effect example usage code.
>
> Signed-off-by: Jean-François Têtu
Applied, thank you.
> ---
> Documentation/input/ff.rst | 6 +++---
>
Hi Marcus,
On Sat, Jan 13, 2018 at 09:15:32PM +0100, Marcus Folkesson wrote:
> This driver let you plug in your RC controller to the adapter and
> use it as input device in various RC simulators.
>
> Signed-off-by: Marcus Folkesson
> ---
> v3:
> - Use RUDDER and MISC instead of TILT_X and
On Thu, Jan 11, 2018 at 01:07:42PM +0100, Marcus Folkesson wrote:
> Hi Dmitry,
>
> Thank you for your review!
>
> On Wed, Jan 10, 2018 at 04:37:14PM -0800, Dmitry Torokhov wrote:
> > Hi Marcus,
> >
> > On Wed, Jan 10, 2018 at 02:11:39PM +0100, Marcus Folkesson
Hi Marcus,
On Wed, Jan 10, 2018 at 02:11:39PM +0100, Marcus Folkesson wrote:
> This driver let you plug in your RC controller to the adapter and
> use it as input device in various RC simulators.
>
> Signed-off-by: Marcus Folkesson
> ---
> v2:
> - Change module license to GPLv2 to match SP
mprove multi-touch-protocol.rst documentation.
> >
> > Signed-off-by: Wei-Ning Huang
> > Signed-off-by: Wei-Ning Huang
> > Reviewed-by: Dmitry Torokhov
> > ---
> > Documentation/input/multi-touch-protocol.rst | 9 ++---
> > drivers/hid/hid-mu
On Thu, Sep 28, 2017 at 12:22:13PM -0700, David Lin wrote:
> On Wed, Sep 27, 2017 at 10:43 PM, Dmitry Torokhov
> wrote:
> >>One thing I noticed is that input_ff_create_memless() also does not
> >>use high-resolution timer hence it also does not have the stop-time
> &
On September 27, 2017 10:03:28 PM PDT, David Lin wrote:
>Dmitry,
>
>On Fri, Sep 15, 2017 at 3:30 PM, Dmitry Torokhov
> wrote:
>> On Fri, Sep 15, 2017 at 2:55 PM, Jacek Anaszewski
>> wrote:
>>> On 09/15/2017 08:34 PM, Dmitry Torokhov wrote:
>>>>
On Tue, Sep 19, 2017 at 1:45 PM, Jacek Anaszewski
wrote:
> On 09/19/2017 12:29 AM, Dmitry Torokhov wrote:
>> On Mon, Sep 18, 2017 at 1:50 PM, Jacek Anaszewski
>> wrote:
>>> Hi,
>>>
>>> On 09/17/2017 08:22 PM, Pavel Machek wrote:
>>>> Hi!
On Mon, Sep 18, 2017 at 1:50 PM, Jacek Anaszewski
wrote:
> Hi,
>
> On 09/17/2017 08:22 PM, Pavel Machek wrote:
>> Hi!
>>
If your objection is that FF is not easily engaged from the shell -
yes, but I do not think that actual users who want to do vibration do
that via shell either. O
On Fri, Sep 15, 2017 at 2:55 PM, Jacek Anaszewski
wrote:
> On 09/15/2017 08:34 PM, Dmitry Torokhov wrote:
>> On Thu, Sep 14, 2017 at 1:58 PM, Pavel Machek wrote:
>>> On Thu 2017-09-14 21:31:31, Jacek Anaszewski wrote:
>>>> Hi David and Pavel,
>>>>
>&
On Thu, Sep 14, 2017 at 1:58 PM, Pavel Machek wrote:
> On Thu 2017-09-14 21:31:31, Jacek Anaszewski wrote:
>> Hi David and Pavel,
>>
>> On 09/13/2017 10:20 PM, Pavel Machek wrote:
>> > Hi!
>> >
>> >> These patch series add the LED_BRIGHTNESS_FAST flag support for
>> >> ledtrig-transient to use hrt
On Thu, May 25, 2017 at 05:16:27PM -0700, Luis R. Rodriguez wrote:
> When checking if we want to allow a kmod thread to kick off we increment,
> then read to see if we should enable a thread. If we were over the allowed
> limit limit we decrement. Splitting the increment far apart from decrement
>
On Thu, May 25, 2017 at 05:16:29PM -0700, Luis R. Rodriguez wrote:
> This adds helpers for getting access to the kmod limit from
> userspace. This knob should help userspace more gracefully and
> deterministically handle module loading.
I think more details is needed before we add a new ABI to the
On Thu, May 25, 2017 at 08:06:03PM +0200, Luis R. Rodriguez wrote:
> On Thu, May 25, 2017 at 10:38:40AM -0700, Luis R. Rodriguez wrote:
> > On Thu, May 25, 2017 at 10:30 AM, Dmitry Torokhov
> > > There is
> > > no slippery slope for systems to move away, no need to backp
On Thu, May 25, 2017 at 09:50:15AM -0700, Luis R. Rodriguez wrote:
> On Thu, May 25, 2017 at 9:38 AM, Dmitry Torokhov
> wrote:
> > On Thu, May 25, 2017 at 06:22:01PM +0200, Luis R. Rodriguez wrote:
> >> On Fri, May 19, 2017 at 02:58:29PM -0700, Dmitry Torokhov wrote:
> &
On Thu, May 25, 2017 at 01:19:31PM +0200, Petr Mladek wrote:
> On Wed 2017-05-24 19:27:38, Dmitry Torokhov wrote:
> > On Thu, May 25, 2017 at 03:00:17AM +0200, Luis R. Rodriguez wrote:
> > > On Wed, May 24, 2017 at 05:45:37PM -0700, Dmitry Torokhov wrote:
> > > > On T
On Thu, May 25, 2017 at 06:22:01PM +0200, Luis R. Rodriguez wrote:
> On Fri, May 19, 2017 at 02:58:29PM -0700, Dmitry Torokhov wrote:
> > On Fri, May 19, 2017 at 02:45:29PM -0700, Luis R. Rodriguez wrote:
> > > On May 19, 2017 1:45 PM, "Dmitry Torokhov"
> > &g
On Thu, May 25, 2017 at 03:00:17AM +0200, Luis R. Rodriguez wrote:
> On Wed, May 24, 2017 at 05:45:37PM -0700, Dmitry Torokhov wrote:
> > On Thu, May 25, 2017 at 02:14:52AM +0200, Luis R. Rodriguez wrote:
> > > On Fri, May 19, 2017 at 03:27:12PM -0700, Dmitry Torokhov wrote:
>
On Thu, May 25, 2017 at 02:14:52AM +0200, Luis R. Rodriguez wrote:
> On Fri, May 19, 2017 at 03:27:12PM -0700, Dmitry Torokhov wrote:
> > On Thu, May 18, 2017 at 08:24:43PM -0700, Luis R. Rodriguez wrote:
> > > In theory it is possible multiple concurrent t
On Mon, May 08, 2017 at 11:11:46AM -0500, Rob Herring wrote:
> On Tue, May 02, 2017 at 05:00:59PM +0200, Martin Kepplinger wrote:
> > The datasheet and application note does not mention an allowed range for
> > the M09_REGISTER_THRESHOLD parameter. One of our customers needs to set
> > lower values
On Thu, May 18, 2017 at 08:24:43PM -0700, Luis R. Rodriguez wrote:
> In theory it is possible multiple concurrent threads will try to
> kmod_umh_threads_get() and as such atomic_inc(&kmod_concurrent) at
> the same time, therefore enabling a small time during which we've
> bumped kmod_concurrent but
On Thu, May 18, 2017 at 08:24:44PM -0700, Luis R. Rodriguez wrote:
> Just use the simplified rate limit printk when the max modprobe
> limit is reached, while at it throw out a bone should the error
> be triggered.
>
> Reviewed-by: Petr Mladek
> Signed-off-by: Luis R. Rodriguez
> ---
> kernel/k
On Fri, May 19, 2017 at 02:45:29PM -0700, Luis R. Rodriguez wrote:
> On May 19, 2017 1:45 PM, "Dmitry Torokhov"
> wrote:
>
> On Thu, May 18, 2017 at 08:24:39PM -0700, Luis R. Rodriguez wrote:
> > We currently statically limit the number of modprobe threads which
>
On Thu, May 18, 2017 at 08:24:39PM -0700, Luis R. Rodriguez wrote:
> We currently statically limit the number of modprobe threads which
> we allow to run concurrently to 50. As per Keith Owens, this was a
> completely arbitrary value, and it was set in the 2.3.38 days [0]
> over 16 years ago in yea
On Sun, Apr 23, 2017 at 03:40:50PM -0300, Marcos Paulo de Souza wrote:
> Signed-off-by: Marcos Paulo de Souza
> ---
I adjusted wording a bit here and there and applied, thank you.
>
> v5 -> v6:
> Resend v5, but now include a change into input_uapi.rst (added by Dmitry and
> Mauro) to include
Do not recommend people write to Dominic, rather everyone should be using
linux-input mailing list.
Signed-off-by: Dmitry Torokhov
---
Documentation/input/devices/xpad.rst | 6 --
1 file changed, 6 deletions(-)
diff --git a/Documentation/input/devices/xpad.rst
b/Documentation/input
On Mon, Apr 17, 2017 at 09:46:13AM -0300, Mauro Carvalho Chehab wrote:
> The /proc/bus/usb/devices got moved to sysfs. It is now
> sitting at:
> /sys/kernel/debug/usb/devices
>
> Signed-off-by: Mauro Carvalho Chehab
Applied, thank you.
> ---
> Documentation/input/devices/xpad.rst
On Mon, Apr 17, 2017 at 09:46:14AM -0300, Mauro Carvalho Chehab wrote:
> Unfortunately, Sphinx (or LaTeX) can't handle literal blocks
> inside footnotes. So, just use normal text for the two
> literal code-blocks that documents the output of
> /sys/kernel/debug/usb/devices for xpad devices.
>
> Si
Hi Mauro,
On Mon, Apr 17, 2017 at 09:46:15AM -0300, Mauro Carvalho Chehab wrote:
> xpad.rst requests a dump of the USB description, as found
> on the USB character device. When we got rid of usbfs,
> its location change. Update it.
I have not heard from Dom ever so I think the best option is to r
The driver has been converted to use generic device properties, so
stop referring to platform data.
Signed-off-by: Dmitry Torokhov
---
Documentation/input/rotary-encoder.rst | 85 ++
1 file changed, 44 insertions(+), 41 deletions(-)
diff --git a/Documentation
The heading level should be the same as for other devices.
Signed-off-by: Dmitry Torokhov
---
Documentation/input/joystick.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/input/joystick.rst b/Documentation/input/joystick.rst
index 202f5a090675..c9c175ffc2ff
Move the documentation for Amiga CD32 together with other parallel port
joysticks.
Signed-off-by: Dmitry Torokhov
---
Documentation/input/cd32.rst | 24 -
Documentation/input/index.rst| 1 -
Documentation/input/joystick-parport.rst | 37
Everyone should be using multitouch protocol B (slotted) now.
Signed-off-by: Dmitry Torokhov
---
Documentation/input/multi-touch-protocol.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/input/multi-touch-protocol.rst
b/Documentation/input/multi-touch
Split input documentation into several groups: kernel- and user-facing, and
notes about individual device drivers. Move device drivers docs into a
separate subdirectory.
Signed-off-by: Dmitry Torokhov
---
Documentation/input/{ => devices}/alps.rst | 2 +-
Documentation/in
This is just a part of kernel documentation, it does not require explicit
license notice.
Signed-off-by: Dmitry Torokhov
---
Documentation/input/index.rst | 21 -
1 file changed, 21 deletions(-)
diff --git a/Documentation/input/index.rst b/Documentation/input/index.rst
Consolidate use instructions and userspace API notes into the same chapter;
remove completely obsolete references, move into a separate subdirectory.
Signed-off-by: Dmitry Torokhov
---
Documentation/input/index.rst | 6 +-
Documentation/input/joydev/index.rst
Stop saying that API is experimental and that only USB is supported,
acknowledge that evdev is the preferred interface, and remove paragraph
encouraging people sending snail mail to Vojtech :) along with his email.
Signed-off-by: Dmitry Torokhov
---
Documentation/input/event-codes.rst
Hi Mauro,
On Tue, Apr 11, 2017 at 10:29:40AM -0300, Mauro Carvalho Chehab wrote:
> Some mice have a switch on their wheel, allowing to switch
> between ratchet and free wheel mode. Add support for it.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/input/event-codes.txt| 12 +
of files that are scanned when compiling
RapiodIO documentations as it no longer has any structured comments, and
leaving it in leads to warning when building docs.
Signed-off-by: Dmitry Torokhov
---
v2: drop rio-sysfs.c from Documentation/DocBook/rapidio.tmpl to avoid
warnings when building docs
On Tue, Oct 11, 2016 at 04:20:52PM +0200, Benjamin Tissoires wrote:
> On Oct 10 2016 or thereabouts, Dmitry Torokhov wrote:
> > Hi Benjamin,
> >
> > On Mon, Oct 10, 2016 at 9:42 AM, Benjamin Tissoires
> > wrote:
> > > The Thinkpad series 13 uses Host Notif
Hi Benjamin,
On Mon, Oct 10, 2016 at 9:42 AM, Benjamin Tissoires
wrote:
> The Thinkpad series 13 uses Host Notify to report the interrupt.
> Add elan_smb_alert() to handle those interrupts and disable the irq
> handling on this case.
>
> Signed-off-by: Benjamin Tissoires
>
Why do we have to do
On Fri, Sep 23, 2016 at 6:37 PM, Herbert, Marc wrote:
> On 03/09/2016 11:10, Dmitry Torokhov wrote:
>> I was thinking if we kernel could post
>> "conditions" (maybe simple stings) that it waits for, and userspace
>> could unlock these "conditions". On
On Sat, Sep 3, 2016 at 11:01 AM, Linus Torvalds
wrote:
> On Sat, Sep 3, 2016 at 10:49 AM, Dmitry Torokhov
> wrote:
>>
>> Unfortunately module loading and availability of firmware is very
>> loosely coupled.
>
> The whole "let's add a new magical proc
On Fri, Sep 02, 2016 at 09:41:18PM -0700, Linus Torvalds wrote:
> On Sep 2, 2016 9:20 PM, "Dmitry Torokhov" wrote:
> >
> > Like what? Some devices do need to have firmware loaded so we know
> > their capabilities, so we really can't push the firmware loadi
On Fri, Sep 2, 2016 at 9:11 PM, Linus Torvalds
wrote:
> On Fri, Sep 2, 2016 at 5:20 PM, Luis R. Rodriguez wrote:
>>
>> Thoughts ?
>
> I really think this is a horrible hack.
>
> It's basically the kernel giving up, and relying on user space to give
> a single flag, and it's broken nasty crap. Wo
On Thu, Aug 25, 2016 at 12:41 PM, Luis R. Rodriguez wrote:
> On Thu, Aug 25, 2016 at 01:05:44PM +0200, Daniel Vetter wrote:
>> On Wed, Aug 24, 2016 at 10:39 PM, Luis R. Rodriguez
>> wrote:
>> > Can they use initramfs for this ?
>>
>> Apparently that's also uncool with the embedded folks.
>
> Wh
On Fri, Jun 24, 2016 at 09:19:32AM +0200, Benjamin Tissoires wrote:
> On Jun 23 2016 or thereabouts, Dmitry Torokhov wrote:
> > On Thu, Jun 09, 2016 at 04:53:50PM +0200, Benjamin Tissoires wrote:
> > > +
> > > +static struct i2c_driver rmi_smb_driver = {
> > >
Hi Benjamin,
On Thu, Jun 09, 2016 at 04:53:50PM +0200, Benjamin Tissoires wrote:
> +
> +struct mapping_table_entry {
> + u16 rmiaddr;
Should be __le16 rmiaddr, otherwise:
CHECK drivers/input/rmi4/rmi_smbus.c
drivers/input/rmi4/rmi_smbus.c:116:33: warning: incorrect type in assignment
(d
On Thu, Jun 23, 2016 at 11:46:55PM +0200, Wolfram Sang wrote:
> On Thu, Jun 23, 2016 at 01:55:52PM -0700, Dmitry Torokhov wrote:
> > On Thu, Jun 16, 2016 at 08:09:42AM +0200, Wolfram Sang wrote:
> > > > > - removed the .resume hook as upstream changed suspend/resume ho
On Thu, Jun 16, 2016 at 08:09:42AM +0200, Wolfram Sang wrote:
> > > - removed the .resume hook as upstream changed suspend/resume hooks and
> > > there
> > > is no need in the end to re-enable host notify on resume (tested on
> > > Lenovo
> > > t440 and t450).
> >
> > Actually, this hook see
On Thu, May 19, 2016 at 02:34:00PM +0530, Vignesh R wrote:
> There are rotary-encoders where GPIO lines reflect the actual position
> of the rotary encoder dial. For example, if dial points to 9, then four
> GPIO lines connected to the rotary encoder will read HLLH(1001b = 9).
> Add support for suc
On Thu, Apr 14, 2016 at 09:17:33PM +0200, Boris Brezillon wrote:
> Call pwm_apply_args() just after requesting the PWM device so that the
> polarity and period are initialized according to the information provided
> in pwm_args.
>
> This is an intermediate state, and pwm_apply_args() should be dro
Hi Boris,
On Wed, Mar 30, 2016 at 10:03:59PM +0200, Boris Brezillon wrote:
> pwm_config/enable/disable() have been deprecated and should be replaced
> by pwm_apply_state().
>
> Signed-off-by: Boris Brezillon
> ---
> drivers/input/misc/max77693-haptic.c | 23 +--
> 1 file cha
Hi Boris,
On Wed, Mar 30, 2016 at 10:03:55PM +0200, Boris Brezillon wrote:
> Prefix those function as deprecated to encourage all existing users to
> switch to pwm_apply_state().
Why not keep at least some of them as wrappers where we do not need to
chnage several parameters at once? It is much e
60 matches
Mail list logo
