1. 02 Nov, 2017 1 commit
    • Greg Kroah-Hartman's avatar
      License cleanup: add SPDX GPL-2.0 license identifier to files with no license · b2441318
      Greg Kroah-Hartman authored
      Many source files in the tree are missing licensing information, which
      makes it harder for compliance tools to determine the correct license.
      
      By default all files without license information are under the default
      license of the kernel, which is GPL version 2.
      
      Update the files which contain no license information with the 'GPL-2.0'
      SPDX license identifier.  The SPDX identifier is a legally binding
      shorthand, which can be used instead of the full boiler plate text.
      
      This patch is based on work done by Thomas Gleixner and Kate Stewart and
      Philippe Ombredanne.
      
      How this work was done:
      
      Patches were generated and checked against linux-4.14-rc6 for a subset of
      the use cases:
       - file had no licensing information it it.
       - file was a */uapi/* one with no licensing information in it,
       - file was a */uapi/* one with existing licensing information,
      
      Further patches will be generated in subsequent months to fix up cases
      where non-standard license headers were used, and references to license
      had to be inferred by heuristics based on keywords.
      
      The analysis to determine which SPDX License Identifier to be applied to
      a file was done in a spreadsheet of side by side results from of the
      output of two independent scanners (ScanCode & Windriver) producing SPDX
      tag:value files created by Philippe Ombredanne.  Philippe prepared the
      base worksheet, and did an initial spot review of a few 1000 files.
      
      The 4.13 kernel was the starting point of the analysis with 60,537 files
      assessed.  Kate Stewart did a file by file comparison of the scanner
      results in the spreadsheet to determine which SPDX license identifier(s)
      to be applied to the file. She confirmed any determination that was not
      immediately clear with lawyers working with the Linux Foundation.
      
      Criteria used to select files for SPDX license identifier tagging was:
       - Files considered eligible had to be source code files.
       - Make and config files were included as candidates if they contained >5
         lines of source
       - File already had some variant of a license header in it (even if <5
         lines).
      
      All documentation files were explicitly excluded.
      
      The following heuristics were used to determine which SPDX license
      identifiers to apply.
      
       - when both scanners couldn't find any license traces, file was
         considered to have no license information in it, and the top level
         COPYING file license applied.
      
         For non */uapi/* files that summary was:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|-------
         GPL-2.0                                              11139
      
         and resulted in the first patch in this series.
      
         If that file was a */uapi/* path one, it was "GPL-2.0 WITH
         Linux-syscall-note" otherwise it was "GPL-2.0".  Results of that was:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|-------
         GPL-2.0 WITH Linux-syscall-note                        930
      
         and resulted in the second patch in this series.
      
       - if a file had some form of licensing information in it, and was one
         of the */uapi/* ones, it was denoted with the Linux-syscall-note if
         any GPL family license was found in the file or had no licensing in
         it (per prior point).  Results summary:
      
         SPDX license identifier                            # files
         ---------------------------------------------------|------
         GPL-2.0 WITH Linux-syscall-note                       270
         GPL-2.0+ WITH Linux-syscall-note                      169
         ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21
         ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17
         LGPL-2.1+ WITH Linux-syscall-note                      15
         GPL-1.0+ WITH Linux-syscall-note                       14
         ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5
         LGPL-2.0+ WITH Linux-syscall-note                       4
         LGPL-2.1 WITH Linux-syscall-note                        3
         ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3
         ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1
      
         and that resulted in the third patch in this series.
      
       - when the two scanners agreed on the detected license(s), that became
         the concluded license(s).
      
       - when there was disagreement between the two scanners (one detected a
         license but the other didn't, or they both detected different
         licenses) a manual inspection of the file occurred.
      
       - In most cases a manual inspection of the information in the file
         resulted in a clear resolution of the license that should apply (and
         which scanner probably needed to revisit its heuristics).
      
       - When it was not immediately clear, the license identifier was
         confirmed with lawyers working with the Linux Foundation.
      
       - If there was any question as to the appropriate license identifier,
         the file was flagged for further research and to be revisited later
         in time.
      
      In total, over 70 hours of logged manual review was done on the
      spreadsheet to determine the SPDX license identifiers to apply to the
      source files by Kate, Philippe, Thomas and, in some cases, confirmation
      by lawyers working with the Linux Foundation.
      
      Kate also obtained a third independent scan of the 4.13 code base from
      FOSSology, and compared selected files where the other two scanners
      disagreed against that SPDX file, to see if there was new insights.  The
      Windriver scanner is based on an older version of FOSSology in part, so
      they are related.
      
      Thomas did random spot checks in about 500 files from the spreadsheets
      for the uapi headers and agreed with SPDX license identifier in the
      files he inspected. For the non-uapi files Thomas did random spot checks
      in about 15000 files.
      
      In initial set of patches against 4.14-rc6, 3 files were found to have
      copy/paste license identifier errors, and have been fixed to reflect the
      correct identifier.
      
      Additionally Philippe spent 10 hours this week doing a detailed manual
      inspection and review of the 12,461 patched files from the initial patch
      version early this week with:
       - a full scancode scan run, collecting the matched texts, detected
         license ids and scores
       - reviewing anything where there was a license detected (about 500+
         files) to ensure that the applied SPDX license was correct
       - reviewing anything where there was no detection but the patch license
         was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
         SPDX license was correct
      
      This produced a worksheet with 20 files needing minor correction.  This
      worksheet was then exported into 3 different .csv files for the
      different types of files to be modified.
      
      These .csv files were then reviewed by Greg.  Thomas wrote a script to
      parse the csv files and add the proper SPDX tag to the file, in the
      format that the file expected.  This script was further refined by Greg
      based on the output to detect more types of files automatically and to
      distinguish between header and source .c files (which need different
      comment types.)  Finally Greg ran the script using the .csv files to
      generate the patches.
      Reviewed-by: default avatarKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: default avatarPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b2441318
  2. 22 Jun, 2017 1 commit
  3. 11 May, 2017 1 commit
    • Hans de Goede's avatar
      HID: ite: Add hid-ite driver · f1918be1
      Hans de Goede authored
      The ITE8595 keyboard uses the HID_GD_RFKILL_BTN usage code
      from the Wireless Radio Controls Application Collection Microsoft
      has defined for Windows 8 and later.
      
      However it has a quirk, when the rfkill hotkey is pressed it does
      generate a report for the collection, but the reported value is
      always 0. Luckily it is the only button in this collection / report,
      and it sends a report on release only, so receiving a report means the
      button was pressed.
      
      This commit adds a hid-ite driver which watches for the Wireless Radio
      Controls Application Collection report and then reports a KEY_RFKILL event,
      ignoring the value, making the rfkill on this keyboard work.
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Reviewed-by: default avatarBenjamin Tissoires <benjamin.tissoires@redhat.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      f1918be1
  4. 21 Mar, 2017 1 commit
  5. 06 Mar, 2017 1 commit
  6. 15 Nov, 2016 1 commit
  7. 03 Nov, 2016 1 commit
  8. 17 Aug, 2016 1 commit
  9. 23 Jun, 2016 1 commit
  10. 17 Jun, 2016 2 commits
  11. 01 Apr, 2016 1 commit
    • Yusuke Fujimaki's avatar
      HID: Asus X205TA keyboard driver · eeb01a57
      Yusuke Fujimaki authored
      Asus X205TA built-in keyboard contains wrong
      logical maximum value in report descriptor.
      
      0x05, 0x01,  // Usage Page (Generic Desktop)
      0x09, 0x06,  // Usage (Keyboard)
      0xa1, 0x01,  // Collection (Application)
      0x85, 0x01,  // Report ID (1)
      0x05, 0x07,  // Usage Page (Keyboard/Keypad)
      0x19, 0xe0,  // Usage Minimum (224)
      0x29, 0xe7,  // Usage Maximum (231)
      0x15, 0x00,  // Logical Minimum (0)
      0x25, 0x01,  // Logical Maximum (1)
      0x75, 0x01,  // Report Size (1)
      0x95, 0x08,  // Report Count (8)
      0x81, 0x02,  // Input (Data,Array,Abs)
      0x95, 0x01,  // Report Count (1)
      0x75, 0x08,  // Report Size (8)
      0x81, 0x03,  // Input (Const,Var,Abs)
      0x95, 0x05,  // Report Count (5)
      0x75, 0x01,  // Report Size (1)
      0x05, 0x08,  // Usage (LED)
      0x19, 0x01,  // Usage Minimum (1)
      0x29, 0x05,  // Usage Maximum (5)
      0x91, 0x02,  // Output (Data,Var,Abs)
      0x95, 0x01,  // Report Count (1)
      0x75, 0x03,  // Report Size (3)
      0x91, 0x03,  // Output (Const,Var,Abs)
      0x95, 0x06,  // Report Count (6)
      0x75, 0x08,  // Report Size (8)
      0x15, 0x00,  // Logical Minimum (0)
      0x25, 0x65,  // Logical Maximum (101)  * too small *
      0x05, 0x07,  // Usage Page (Keyboard/Keypad)
      0x19, 0x00,  // Usage Minimum (0)
      0x29, 0xdd,  // Usage Maximum (221)
      0x81, 0x00,  // Input(Data,Array,Abs)
      
      In Asus X205TA japanese keyboard model,there are language
      specific keys over usage id 101.
      This patch correct wrong logical maximum in report
      descriptor.
      Signed-off-by: default avatarYusuke Fujimaki <usk.fujimaki@gmail.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      eeb01a57
  12. 02 Mar, 2016 1 commit
  13. 26 Oct, 2015 1 commit
  14. 30 Sep, 2015 1 commit
  15. 18 Aug, 2015 1 commit
  16. 26 May, 2015 1 commit
  17. 10 Apr, 2015 1 commit
    • Srinivas Pandruvada's avatar
      HID: sensor: Custom and Generic sensor support · 4a7de051
      Srinivas Pandruvada authored
      HID Sensor Spec defines two usage ids for custom sensors
      
      	HID_USAGE_SENSOR_TYPE_OTHER_CUSTOM (0x09, 0xE1)
      	HID_USAGE_SENSOR_TYPE_OTHER_GENERIC(0x09, 0xE2)
      
      	In addition the standard also defines usage ids for custom fields.
      The purpose of these sensors is to extend the functionality or provide a way to
      obfuscate the data being communicated by a sensor. Without knowing the mapping
      between the data and its encapsulated form, it is difficult for an driver to
      determine what data is being communicated by the sensor.  This allows some
      differentiating use cases, where vendor can provide applications.  Since these
      can't be represented by standard sensor interfaces like IIO, we present these
      as fields with
      
      - type (input/output)
      - units
      - min/max
      - get/set value
      
      In addition an dev interface to transfer report events. Details about this
      interface is described in /Documentation/hid/hid-sensor.txt.  Manufacturers
      should not use these ids for any standard sensors, otherwise the the
      product/vendor id can be added to black list.
      Signed-off-by: default avatarSrinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
      Reviewed-by: default avatarJonathan Cameron <jic23@kernel.org>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      4a7de051
  18. 03 Mar, 2015 1 commit
  19. 21 Jan, 2015 1 commit
  20. 22 Dec, 2014 1 commit
  21. 03 Nov, 2014 1 commit
  22. 29 Oct, 2014 1 commit
  23. 04 Sep, 2014 1 commit
  24. 06 Aug, 2014 1 commit
  25. 29 Jul, 2014 1 commit
  26. 26 Jul, 2014 1 commit
  27. 01 Jul, 2014 1 commit
  28. 09 Apr, 2014 1 commit
  29. 17 Feb, 2014 1 commit
    • David Barksdale's avatar
      HID: add hid-cp2112 driver · e932d817
      David Barksdale authored
      This patch adds support for the Silicon Labs CP2112 "Single-Chip HID USB to
      SMBus Master Bridge."
      
      This is a HID device driver which registers as an i2c adapter and gpiochip to
      expose these functions of the CP2112. The customizable USB descriptor fields
      are exposed as sysfs attributes.  The SMBus byte-read, byte-data-read/write,
      and word-data-read transfer modes have been tested by talking to an i2c
      sensor.  The GPIO functions and USB descriptor field programming have also
      been tested.
      Signed-off-by: default avatarDavid Barksdale <dbarksdale@uplogix.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      e932d817
  30. 30 Oct, 2013 1 commit
  31. 29 Jul, 2013 1 commit
  32. 13 Jun, 2013 1 commit
  33. 03 Jun, 2013 2 commits
  34. 28 May, 2013 3 commits
    • Jiri Slaby's avatar
      HID: add driver for ELO 4000/4500 · d23efc19
      Jiri Slaby authored
      This is a driver for ELO 4000/4500 devices which report themselves as
      HID devices, but do not really send HID events on touch. So we
      introduce a new HID 'quirk' driver with a raw_event handler where we
      take care of those events.
      
      What we need additionally is an input_configured hook, because the
      device does not mention anything about PRESSURE and TOUCH in its
      report descriptor, but it actually generate those. So we set the bits
      in the corresponding input_dev in that hook.
      
      Thanks to Petr Ostadal who was willing to test the driver. The rest of
      Cc's listed below had something to do with that driver over the years
      in our enterprise tree.
      Signed-off-by: default avatarJiri Slaby <jslaby@suse.cz>
      Tested-by: default avatarPetr Ostadal <postadal@suse.cz>
      Cc: Oliver Neukum <oliver@neukum.org>
      Cc: Vojtech Pavlik <vojtech@suse.cz>
      Cc: Egbert Eich <eich@suse.com>
      Cc: Libor Pechacek <lpechacek@suse.cz>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      d23efc19
    • Martin Rusko's avatar
      HID: add support for Huion 580 tablet · 68e353fe
      Martin Rusko authored
      Add hid-huion.c with support for Huion 580 tablet, which is simple
      8x5" tablet with 4000LPI resolution and 2048 levels pressure-sensitive
      pen manufactured by the Chinese company Huion.
      
      The driver fixes incorrect report descriptor sent by the device,
      performs custom initialization required to switch the tablet into
      its native resolution mode and inverts the in-range bit.
      Signed-off-by: default avatarMartin Rusko <martin.rusko@gmail.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      68e353fe
    • Christian Ohm's avatar
      HID: Add driver for Holtek gaming mouse 04d9:a067 · 41de326e
      Christian Ohm authored
      This mouse is sold as Sharkoon Drakonia and Perixx MX-2000 and reports a
      too high usage maximum and logical maximum. This driver fixes the report
      descriptor so those values don't exceed HID_MAX_USAGES.
      Signed-off-by: default avatarChristian Ohm <chr.ohm@gmx.net>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      41de326e
  35. 19 Apr, 2013 1 commit
  36. 14 Mar, 2013 1 commit