1. 18 12月, 2015 2 次提交
    • K
      Input: goodix - add axis swapping and axis inversion support · ad48cf5e
      Karsten Merker 提交于
      Implement support for the following device-tree and ACPI 5.1 DSD
      properties in the goodix touchscreen driver:
      
       - touchscreen-inverted-x:  X axis is inverted (boolean)
       - touchscreen-inverted-y:  Y axis is inverted (boolean)
       - touchscreen-swapped-x-y: X and Y axis are swapped (boolean)
      
      These are necessary on tablets which have a display in portrait
      format while the touchscreen is in landscape format, such as e.g.
      the MSI Primo 81.
      Signed-off-by: NKarsten Merker <merker@debian.org>
      Tested-by: NBastien Nocera <hadess@hadess.net>
      Tested-by: Irina Tirdea <irina.tirdea@intel.com> (with ACPI DSD properties)
      Tested-by: Aleksei Mamlin <mamlinav@gmail.com> (with device-tree properties)
      Acked-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>
      ad48cf5e
    • I
      Input: goodix - reset device at init · ec6e1b40
      Irina Tirdea 提交于
      After power on, it is recommended that the driver resets the device.
      The reset procedure timing is described in the datasheet and is used
      at device init (before writing device configuration) and
      for power management. It is a sequence of setting the interrupt
      and reset pins high/low at specific timing intervals. This procedure
      also includes setting the slave address to the one specified in the
      ACPI/device tree.
      
      This is based on Goodix datasheets for GT911 and GT9271 and on Goodix
      driver gt9xx.c for Android (publicly available in Android kernel
      trees for various devices).
      
      For reset the driver needs to control the interrupt and
      reset gpio pins (configured through ACPI/device tree). For devices
      that do not have the gpio pins properly declared, the functionality
      depending on these pins will not be available, but the device can still
      be used with basic functionality.
      
      For both device tree and ACPI, the interrupt gpio pin configuration is
      read from the "irq-gpios" property and the reset pin configuration is
      read from the "reset-gpios" property. For ACPI 5.1, named properties
      can be specified using the _DSD section. This functionality will not be
      available for devices that use indexed gpio pins declared in the _CRS
      section (we need to provide backward compatibility with devices
      that do not support using the interrupt gpio pin as output).
      
      For ACPI, the pins can be specified using ACPI 5.1:
      Device (STAC)
      {
          Name (_HID, "GDIX1001")
          ...
      
          Method (_CRS, 0, Serialized)
          {
              Name (RBUF, ResourceTemplate ()
              {
                  I2cSerialBus (0x0014, ControllerInitiated, 0x00061A80,
                      AddressingMode7Bit, "\\I2C0",
                      0x00, ResourceConsumer, ,
                      )
      
                  GpioInt (Edge, ActiveHigh, Exclusive, PullNone, 0x0000,
                      "\\I2C0", 0x00, ResourceConsumer, ,
                       )
                       {   // Pin list
                           0
                       }
      
                  GpioIo (Exclusive, PullDown, 0x0000, 0x0000,
                      IoRestrictionOutputOnly, "\\I2C0", 0x00,
                      ResourceConsumer, ,
                      )
                      {
                           1
                      }
              })
              Return (RBUF)
          }
      
          Name (_DSD,  Package ()
          {
              ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
              Package ()
              {
                  Package (2) {"irq-gpios", Package() {^STAC, 0, 0, 0 }},
                  Package (2) {"reset-gpios", Package() {^STAC, 1, 0, 0 }},
                  ...
              }
          }
      Signed-off-by: NOctavian Purdila <octavian.purdila@intel.com>
      Signed-off-by: NIrina Tirdea <irina.tirdea@intel.com>
      Acked-by: NRob Herring <robh@kernel.org>
      Acked-by: NBastien Nocera <hadess@hadess.net>
      Tested-by: NBastien Nocera <hadess@hadess.net>
      Tested-by: NAleksei Mamlin <mamlinav@gmail.com>
      Signed-off-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>
      ec6e1b40
  2. 04 11月, 2015 1 次提交
  3. 17 10月, 2015 1 次提交
  4. 03 10月, 2015 1 次提交
  5. 28 9月, 2015 2 次提交
  6. 06 9月, 2015 2 次提交
  7. 04 8月, 2015 1 次提交
    • D
      Input: zforce - make the interrupt GPIO optional · 62f46669
      Dirk Behme 提交于
      Add support for hardware which uses an I2C Serializer / Deserializer
      (SerDes) to communicate with the zFroce touch driver. In this case the
      SerDes will be configured as an interrupt controller and the zForce driver
      will have no access to poll the GPIO line.
      
      To support this, we add two dedicated new GPIOs in the device tree:
      reset-gpios and irq-gpios, with the irq-gpios being optional.
      
      To not break the existing device trees, the index based 'gpios' entries
      are still supported, but marked as deprecated.
      
      With this, if the interrupt GPIO is available, either via the old or new
      device tree style, the while loop will read and handle the packets as long
      as the GPIO indicates that the interrupt is asserted (existing, unchanged
      driver behavior).
      
      If the interrupt GPIO isn't available, i.e. not configured via the new
      device tree style, we are falling back to one read per ISR invocation
      (new behavior to support the SerDes).
      
      Note that the gpiod functions help to handle the optional GPIO:
      devm_gpiod_get_index_optional() will return NULL in case the interrupt
      GPIO isn't available. And gpiod_get_value_cansleep() does cover this, too,
      by returning 0 in this case.
      Signed-off-by: NDirk Behme <dirk.behme@de.bosch.com>
      Reviewed-by: NHeiko Stuebner <heiko.stuebner@bq.com>
      Signed-off-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>
      62f46669
  8. 12 7月, 2015 1 次提交
  9. 30 5月, 2015 1 次提交
  10. 14 5月, 2015 1 次提交
  11. 25 3月, 2015 2 次提交
  12. 24 3月, 2015 2 次提交
  13. 09 3月, 2015 1 次提交
    • H
      Input: sun4i-ts - A10 (sun4i) has a different temperature curve · 91c68a7c
      Hans de Goede 提交于
      Testing has revealed that the temperature in the rtp controller of the A10
      (sun4i) SoC has a different curve then on the A13 (sun5i) and later models.
      
      Add a new sun5i-a13-ts compatible to differentiate the newer models and
      set the curve based on the compatible string.
      
      The new curve is still not ideal on all A10-s, that seems to have to
      do with there being a large spread between different A10-s out there,
      the new curve us based on callibration results on 4 completely different
      models:
                              raw min raw max temp min temp max stepsize offset
      Tong Zhang's hackberry    2402    2680    45.0     80.0    0.125   -255.3
      Hansg's Cubieboard        2207    2300    36.0     45.0    0.096   -175.8
      Olliver's lime 1 (*):     2258    2537    48.3     87.1    0.139   -265.7
      Olliver's lime 2 (*):     2222    2486    46.7     91.7    0.170   -331.0
      *) from: http://linux-sunxi.org/Temperature_Calibration
      
      Average all 4:                                             0.133   -257.0
      Average without outliers (middle 2):                       0.132   -261.0
      
      Since it is better to slightly overreport the temperature this patch uses
      the average of all 4 as curve.
      
      This fixes the temperature reported on the A10 being much higher then
      expected.
      Reported-by: NTong Zhang <lovewilliam@gmail.com>
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Signed-off-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>
      91c68a7c
  14. 07 3月, 2015 2 次提交
  15. 04 2月, 2015 1 次提交
  16. 27 1月, 2015 1 次提交
  17. 18 1月, 2015 1 次提交
  18. 29 7月, 2014 1 次提交
  19. 22 7月, 2014 1 次提交
  20. 29 5月, 2014 2 次提交
  21. 15 5月, 2014 2 次提交
  22. 29 3月, 2014 1 次提交
  23. 28 1月, 2014 1 次提交
  24. 26 11月, 2013 1 次提交
  25. 11 11月, 2013 1 次提交
  26. 30 8月, 2013 1 次提交
  27. 13 6月, 2013 1 次提交
  28. 16 4月, 2013 1 次提交
  29. 25 2月, 2013 1 次提交
  30. 23 11月, 2012 1 次提交
  31. 01 11月, 2012 1 次提交
  32. 25 10月, 2012 1 次提交
    • H
      Input: egalax_ts - get gpio from devicetree · ae495e84
      Hui Wang 提交于
      The irq_to_gpio() is old, most platforms use GENERIC_GPIO framework
      and don't support this API anymore.
      
      The i.MX6q sabrelite platform equips an egalax touchscreen controller,
      and this platform already transfered to GENERIC_GPIO framework, to
      support this driver, we use a more generic way to get gpio.
      
      Add a return value checking for waking up the controller in the probe
      function, this guarantee only a workable device can pass init.
      
      [dmitry.torokhov@gmail.com: Make driver depend on CONFIG_OF as it is
       now required.]
      
      Acked-by Zhang Jiejing <jiejing.zhang@freescale.com>
      Reviewed-by: NShawn Guo <shawn.guo@linaro.org>
      Signed-off-by: NHui Wang <jason77.wang@gmail.com>
      Signed-off-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>
      ae495e84