1. 04 11月, 2017 3 次提交
  2. 19 9月, 2017 2 次提交
  3. 17 7月, 2017 1 次提交
  4. 29 6月, 2017 1 次提交
  5. 06 2月, 2017 1 次提交
  6. 26 1月, 2017 1 次提交
    • M
      pinctrl / gpio: Introduce .set_config() callback for GPIO chips · 2956b5d9
      Mika Westerberg 提交于
      Currently we already have two pin configuration related callbacks
      available for GPIO chips .set_single_ended() and .set_debounce(). In
      future we expect to have even more, which does not scale well if we need
      to add yet another callback to the GPIO chip structure for each possible
      configuration parameter.
      
      Better solution is to reuse what we already have available in the
      generic pinconf.
      
      To support this, we introduce a new .set_config() callback for GPIO
      chips. The callback takes a single packed pin configuration value as
      parameter. This can then be extended easily beyond what is currently
      supported by just adding new types to the generic pinconf enum.
      
      If the GPIO driver is backed up by a pinctrl driver the GPIO driver can
      just assign gpiochip_generic_config() (introduced in this patch) to
      .set_config and that will take care configuration requests are directed
      to the pinctrl driver.
      
      We then convert the existing drivers over .set_config() and finally
      remove the .set_single_ended() and .set_debounce() callbacks.
      Suggested-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NMika Westerberg <mika.westerberg@linux.intel.com>
      Reviewed-by: NAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      2956b5d9
  7. 21 11月, 2016 1 次提交
  8. 17 11月, 2016 1 次提交
  9. 24 10月, 2016 4 次提交
  10. 20 10月, 2016 1 次提交
  11. 27 9月, 2016 1 次提交
  12. 15 7月, 2016 1 次提交
  13. 05 5月, 2016 3 次提交
  14. 24 4月, 2016 2 次提交
  15. 07 4月, 2016 1 次提交
  16. 01 3月, 2016 4 次提交
  17. 18 2月, 2016 1 次提交
  18. 25 1月, 2016 1 次提交
  19. 29 12月, 2015 1 次提交
  20. 26 11月, 2015 1 次提交
  21. 23 11月, 2015 1 次提交
  22. 16 11月, 2015 3 次提交
    • K
      USB: cp210x: work around cp2108 GET_LINE_CTL bug · d0bf1ff0
      Konstantin Shkolnyy 提交于
      Add helper to access line-control register in order to work around a
      cp2108 GET_LINE_CTL bug.
      
      cp2108 GET_LINE_CTL returns the 16-bit value with the 2 bytes swapped.
      However, SET_LINE_CTL functions properly. When the driver tries to modify
      the register, it reads it, modifies some bits and writes back. Because the
      read bytes were swapped, this often results in an invalid value to be
      written. In turn, this causes cp2108 respond with a stall. The stall
      sometimes doesn't clear properly and cp2108 starts responding to following
      valid commands also with stalls, effectively failing.
      Signed-off-by: NKonstantin Shkolnyy <konstantin.shkolnyy@gmail.com>
      [johan: amend commit message, modify probe error handling ]
      Signed-off-by: NJohan Hovold <johan@kernel.org>
      d0bf1ff0
    • K
      USB: cp210x: relocate private data from USB interface to port · e2ae67a3
      Konstantin Shkolnyy 提交于
      This change is preparation for implementing a cp2108 bug workaround.
      The workaround requires storing some private data. Right now the data is
      attached to the USB interface and allocated in the attach() callback.
      The bug detection requires USB I/O which is done easier from port_probe()
      callback rather than attach(). Since the USB access functions take port
      as a parameter, and since the private data is used exclusively by these
      functions, it can be allocated in port_probe(). Also, all cp210x devices
      have exactly 1 port per USB iterface, so moving private data from the USB
      interface to port is trivial.
      Signed-off-by: NKonstantin Shkolnyy <konstantin.shkolnyy@gmail.com>
      Signed-off-by: NJohan Hovold <johan@kernel.org>
      e2ae67a3
    • K
      USB: cp210x: flush device queues at close · ebfb319b
      Konstantin Shkolnyy 提交于
      Flush all device queues at close in order to work around a cp2108 Tx
      queue bug.
      
      Occasionally, writing data and immediately closing the port makes cp2108
      stop responding. The device has to be unplugged to clear the error.
      The failure is induced by shutting down the device while its Tx queue
      still has unsent data. This condition is avoided by issuing PURGE command
      from the close() callback.
      
      This change is applied to all cp210x devices. Clearing internal queues on
      close is generally good.
      Signed-off-by: NKonstantin Shkolnyy <konstantin.shkolnyy@gmail.com>
      [johan: amend commit message ]
      Signed-off-by: NJohan Hovold <johan@kernel.org>
      ebfb319b
  23. 06 7月, 2015 1 次提交
  24. 05 6月, 2015 1 次提交
  25. 29 4月, 2015 1 次提交
  26. 27 2月, 2015 1 次提交