On Sat, Nov 21, 2015 at 1:37 PM, Edwin Velds wrote:
> This patch implements force feedback support for the Logitech G920 Driving
> Force
> Racing Wheel.
>
> This patch is based on the basic G920 support patch by Simon Wood:
> http://www.spinics.net/lists/linux-input/msg42174.html
>
> The first pa
On Fri, 27 Nov 2015, Vladis Dronov wrote:
> Hello,
>
> > > Hmm, I see quite a few drivers assuming that endpoint 0 will be present.
> > > I wonder if that should not be solved at USB level.
> >
> > Every USB device always has endpoint 0. If one didn't, the kernel
> > wouldn't be able to initial
On Wed, Nov 25, 2015 at 04:07:21PM -0800, Andrew Duggan wrote:
> Add devicetree binding for I2C devices and add bindings for optional
> parameters in the function drivers. Parameters for function drivers are
> defined in child nodes for each of the functions.
>
> Signed-off-by: Andrew Duggan
> --
On Wed, Nov 25, 2015 at 04:09:13PM -0800, Andrew Duggan wrote:
> 2D sensors have several parameter which can be set in the platform data.
> This patch adds support for getting those values from devicetree.
>
> Signed-off-by: Andrew Duggan
> ---
> .../bindings/input/rmi4/rmi_2d_sensor.txt
On Thu, Nov 26, 2015 at 7:12 AM, Tuomas Räsänen
wrote:
> On Wed, Nov 25, 2015 at 05:15:44PM -0800, Andrew Duggan wrote:
>> Hi Tuomas,
>>
>
> Hi Andrew and thanks for the reply,
>
>> It looks like some other people have reported similar issues with this
>> particular touchpad module. I think there
Hi Jonathan,
On Fri, Nov 27, 2015 at 05:48:56PM +0100, Jonathan Beilharz wrote:
> Still haven't got it on the mailing list... Also can't find any info
> on how to add new stuff. I already had sent an email sometime ago
> but since then I found out more.
Hmm, not sure why your email do not reach t
On Fri, Nov 27, 2015 at 05:24:21PM +, Tirdea, Irina wrote:
>
>
> > -Original Message-
> > From: Rob Herring [mailto:r...@kernel.org]
> > Sent: 20 November, 2015 17:45
> > To: Tirdea, Irina
> > Cc: Dmitry Torokhov; Bastien Nocera; Aleksei Mamlin; Karsten Merker;
> > linux-input@vger.k
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: 20 November, 2015 17:45
> To: Tirdea, Irina
> Cc: Dmitry Torokhov; Bastien Nocera; Aleksei Mamlin; Karsten Merker;
> linux-input@vger.kernel.org; Mark Rutland; Purdila, Octavian;
> linux-ker...@vger.kernel.org; dev
On Friday 27 November 2015 18:00:31 WEN Pingbo wrote:
> This patch depends on 'introduce new evdev interface'.
>
> Userspace cat set / get evdev interface type via the two ioctl
> commands. And default interface type is EV_IF_LEGACY, so the old binary
> will work normal with new kernel. Maybe we s
On Friday 27 November 2015 18:00:29 WEN Pingbo wrote:
> To solve the y2038 problem in input_event, I had some attempts before [1],
> and this is the second one.
>
> We can force userspace to use monotonic time in event timestamp, so the
> 'struct timeval' is enough to keep y2038-safe, as Arnd sugg
2015-11-24 13:24 GMT+01:00 Andrew Shadura :
> On 29/10/15 16:00, Andrew Shadura wrote:
>> PenMount 6000 USB resistive touchscreen controller reports it has three
>> buttons, while in reality it doesn't have any and doesn't support active
>> styli, and only generates touch events.
>>
>> In penmount_
Hello,
> > Hmm, I see quite a few drivers assuming that endpoint 0 will be present.
> > I wonder if that should not be solved at USB level.
>
> Every USB device always has endpoint 0. If one didn't, the kernel
> wouldn't be able to initialize and enumerate it.
Yes for the normal USB device. Thi
Hi WEN,
[auto build test ERROR on: input/next]
[also build test ERROR on: v4.4-rc2 next-20151127]
url:
https://github.com/0day-ci/linux/commits/WEN-Pingbo/introduce-new-evdev-interface-type/20151127-180438
base: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git next
config
This patch depends on 'introduce new evdev interface'.
Userspace cat set / get evdev interface type via the two ioctl
commands. And default interface type is EV_IF_LEGACY, so the old binary
will work normal with new kernel. Maybe we should change this default
option to encourage people to move to
This patch depends on 'add new evdev interface'.
We should not use input_event in kernel any more. Convert it in
uinput, and adapt to new api changes.
Signed-off-by: WEN Pingbo
---
drivers/input/misc/uinput.c | 23 +++
include/linux/uinput.h | 2 +-
2 files changed, 12
The y2038 problem in 'struct input_event' is complained too much. And
after some discussion with other people, I found it's impossible to
solve this in a simple way, and keep backward compatible at the same
time, so we need some new y2038-safe interface here.
This patch add two new evdev interface
To solve the y2038 problem in input_event, I had some attempts before [1],
and this is the second one.
We can force userspace to use monotonic time in event timestamp, so the
'struct timeval' is enough to keep y2038-safe, as Arnd suggested. But we
can not find a way to make kernel compatible with
17 matches
Mail list logo
