19 Jun, 2019

1 commit

  • Based on 2 normalized pattern(s):

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation #

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-only

    has been chosen to replace the boilerplate/reference in 4122 file(s).

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Enrico Weigelt
    Reviewed-by: Kate Stewart
    Reviewed-by: Allison Randal
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190604081206.933168790@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

26 Mar, 2017

1 commit

  • Devices connected to serio bus are quite slow, and to improve apparent
    speed of resume process, serio core resumes (reconnects) its devices
    asynchronously, by posting port reconnect requests to a workqueue.
    Unfortunately this means that if there is a dependent device of a given
    serio port (for example SMBus part of touchpad connected via both PS/2 and
    SMBus), we do not have a good way of ensuring resume order.

    This change allows drivers to define "fast reconnect" handlers that would
    be called in-line during system resume. Drivers need to ensure that these
    handlers are truly "fast".

    Reviewed-by: Benjamin Tissoires
    Signed-off-by: Dmitry Torokhov

    Dmitry Torokhov
     

28 Jul, 2016

1 commit

  • As explained in 1407814240-4275-1-git-send-email-decui@microsoft.com we
    have a hard load dependency between i8042 and atkbd which prevents
    keyboard from working on Gen2 Hyper-V VMs.

    > hyperv_keyboard invokes serio_interrupt(), which needs a valid serio
    > driver like atkbd.c. atkbd.c depends on libps2.c because it invokes
    > ps2_command(). libps2.c depends on i8042.c because it invokes
    > i8042_check_port_owner(). As a result, hyperv_keyboard actually
    > depends on i8042.c.
    >
    > For a Generation 2 Hyper-V VM (meaning no i8042 device emulated), if a
    > Linux VM (like Arch Linux) happens to configure CONFIG_SERIO_I8042=m
    > rather than =y, atkbd.ko can't load because i8042.ko can't load(due to
    > no i8042 device emulated) and finally hyperv_keyboard can't work and
    > the user can't input: https://bugs.archlinux.org/task/39820
    > (Ubuntu/RHEL/SUSE aren't affected since they use CONFIG_SERIO_I8042=y)

    To break the dependency we move away from using i8042_check_port_owner()
    and instead allow serio port owner specify a mutex that clients should use
    to serialize PS/2 command stream.

    Reported-by: Mark Laws
    Tested-by: Mark Laws
    Cc: stable@vger.kernel.org
    Signed-off-by: Dmitry Torokhov

    Dmitry Torokhov
     

17 Jul, 2015

1 commit

  • A big problem with the current i8042 debugging option is that it outputs
    data going to and from the keyboard by default. As a result, many dmesg
    logs uploaded by users will unintentionally contain sensitive information
    such as their password, as such it's probably a good idea not to output
    data coming from the keyboard unless specifically enabled by the user.

    Signed-off-by: Stephen Chandler Paul
    Reviewed-by: Andreas Mohr
    Reviewed-by: Benjamin Tissoires
    Signed-off-by: Dmitry Torokhov

    Stephen Chandler Paul
     

20 Apr, 2014

1 commit

  • serio devices exposed via platform firmware interfaces such as ACPI may
    provide additional identifying information of use to userspace.

    We don't associate the serio devices with the firmware device (we don't
    set it as parent), so there's no way for userspace to make use of this
    information.

    We cannot change the parent for serio devices instantiated though a
    firmware interface as that would break suspend / resume ordering.

    Therefore this patch adds a new firmware_id sysfs attribute so that
    userspace can get a string from there with any additional identifying
    information the firmware interface may provide.

    Signed-off-by: Hans de Goede
    Acked-by: Peter Hutterer
    Signed-off-by: Dmitry Torokhov

    Hans de Goede
     

13 Oct, 2012

1 commit


05 Apr, 2012

1 commit

  • This patch introduces the module_serio_driver macro which is a
    convenience macro for serio driver modules similar to
    module_platform_driver. It is intended to be used by drivers
    which init/exit section does nothing but registers/unregisters
    the serio driver. By using this macro it is possible to eliminate
    a few lines of boilerplate code per serio driver.

    Based on work done by Lars-Peter Clausen for
    other buses (i2c and spi).

    Signed-off-by: Axel Lin
    Signed-off-by: Dmitry Torokhov

    Axel Lin
     

01 Nov, 2011

1 commit

  • The original implementations reference THIS_MODULE in an inline.
    We could include , but it is better to avoid chaining.

    Fortunately someone else already thought of this, and made a similar
    inline into a #define in for device_schedule_callback(),
    [see commit 523ded71de0] so follow that precedent here.

    Also bubble up any __must_check that were used on the prev. wrapper inline
    functions up one to the real __register functions, to preserve any prev.
    sanity checks that were used in those instances.

    Signed-off-by: Paul Gortmaker

    Paul Gortmaker
     

29 Sep, 2011

1 commit


19 Oct, 2010

1 commit


13 Oct, 2010

1 commit


14 Sep, 2010

2 commits


14 Apr, 2010

1 commit


22 Jan, 2010

1 commit


06 Jan, 2010

2 commits

  • No need to keep track of it by ourselves.

    Signed-off-by: Dmitry Torokhov

    Dmitry Torokhov
     
  • sysfs_remove_group() waits for sysfs attributes to be removed, therefore
    we do not need to worry about driver-specific attributes being accessed
    after driver has been detached from the device. In fact, attempts to take
    serio->drv_mutex in attribute methods may lead to the following deadlock:

    sysfs_read_file()
    fill_read_buffer()
    sysfs_get_active_two()
    psmouse_attr_show_helper()
    serio_pin_driver()
    serio_disconnect_driver()
    mutex_lock(&serio->drv_mutex);
    mutex_lock(&serio_drv_mutex);
    psmouse_disconnect()
    sysfs_remove_group(... psmouse_attr_group);
    ....
    sysfs_deactivate();
    wait_for_completion();

    Fix this by removing calls to serio_[un]pin_driver() and functions themselves
    and using driver-private mutexes to serialize access to attribute's set()
    methods that may change device state.

    Signed-off-by: Eric W. Biederman
    Signed-off-by: Dmitry Torokhov

    Eric W. Biederman
     

27 Oct, 2009

1 commit

  • This is a driver for Dynapro serial touchscreen, which used to be
    supported in Xorg. The driver needs updated inputattach utility to
    initialize serial port and create proper serio device before the
    driver will be bound to it.

    Signed-off-by: Tias Guns
    Signed-off-by: Dmitry Torokhov

    Tias Guns
     

27 Jul, 2009

1 commit


10 May, 2009

1 commit


08 Mar, 2009

1 commit


25 Nov, 2008

1 commit


24 Jul, 2008

1 commit


08 Jul, 2008

2 commits


30 Jun, 2008

1 commit


16 Apr, 2008

1 commit

  • This is a driver for Zhen Hua PPM-4CH RC transmitter (commonly used in cheap
    Ready To Fly RC helicopters by Walkera) which using "Zhen Hua 5-byte protocol"
    for using them as a four axis joystick via serial port. Transmitter connected
    to serial port (19200 8N1) sending periodically 5 bytes where first byte is for
    synchronization and next four bytes are values of axis.

    Signed-off-by: Martin Kebert
    Signed-off-by: Jiri Kosina
    Signed-off-by: Dmitry Torokhov

    Martin Kebert
     

18 Jul, 2007

1 commit

  • These serial touchscreens are found on some Fujitsu lifebook
    P-series laptops, and the B6210. Using this requires a new
    version of inputattach and doing:

    inputattach -fjt /dev/ttyS0

    Big thanks to Stephen Hemminger for testing it and making it
    work on his B6210 laptop.

    Signed-off-by: Stephen Hemminger
    Signed-off-by: Dmitry Torokhov

    Dmitry Torokhov
     

12 Jul, 2007

1 commit


18 Feb, 2007

1 commit


08 Feb, 2007

1 commit


24 Nov, 2006

1 commit

  • Perform actual driver registration right in serio_register_driver()
    instead of offloading it to kseriod and return proper error code to
    callers if driver registration fails.

    Note that driver port matching is still done by kseriod to
    speed up boot process since probing for PS/2 mice and keyboards
    is pretty slow.

    Signed-off-by: Dmitry Torokhov

    Dmitry Torokhov
     

17 Nov, 2006

1 commit


11 Oct, 2006

1 commit


05 Oct, 2006

1 commit

  • Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
    of passing regs around manually through all ~1800 interrupt handlers in the
    Linux kernel.

    The regs pointer is used in few places, but it potentially costs both stack
    space and code to pass it around. On the FRV arch, removing the regs parameter
    from all the genirq function results in a 20% speed up of the IRQ exit path
    (ie: from leaving timer_interrupt() to leaving do_IRQ()).

    Where appropriate, an arch may override the generic storage facility and do
    something different with the variable. On FRV, for instance, the address is
    maintained in GR28 at all times inside the kernel as part of general exception
    handling.

    Having looked over the code, it appears that the parameter may be handed down
    through up to twenty or so layers of functions. Consider a USB character
    device attached to a USB hub, attached to a USB controller that posts its
    interrupts through a cascaded auxiliary interrupt controller. A character
    device driver may want to pass regs to the sysrq handler through the input
    layer which adds another few layers of parameter passing.

    I've build this code with allyesconfig for x86_64 and i386. I've runtested the
    main part of the code on FRV and i386, though I can't test most of the drivers.
    I've also done partial conversion for powerpc and MIPS - these at least compile
    with minimal configurations.

    This will affect all archs. Mostly the changes should be relatively easy.
    Take do_IRQ(), store the regs pointer at the beginning, saving the old one:

    struct pt_regs *old_regs = set_irq_regs(regs);

    And put the old one back at the end:

    set_irq_regs(old_regs);

    Don't pass regs through to generic_handle_irq() or __do_IRQ().

    In timer_interrupt(), this sort of change will be necessary:

    - update_process_times(user_mode(regs));
    - profile_tick(CPU_PROFILING, regs);
    + update_process_times(user_mode(get_irq_regs()));
    + profile_tick(CPU_PROFILING);

    I'd like to move update_process_times()'s use of get_irq_regs() into itself,
    except that i386, alone of the archs, uses something other than user_mode().

    Some notes on the interrupt handling in the drivers:

    (*) input_dev() is now gone entirely. The regs pointer is no longer stored in
    the input_dev struct.

    (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
    something different depending on whether it's been supplied with a regs
    pointer or not.

    (*) Various IRQ handler function pointers have been moved to type
    irq_handler_t.

    Signed-Off-By: David Howells
    (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)

    David Howells
     

05 Aug, 2006

3 commits


02 Apr, 2006

1 commit


27 Mar, 2006

1 commit