1. 01 9月, 2017 2 次提交
  2. 28 8月, 2017 1 次提交
    • J
      usb: misc: lvstest: add entry to place port in compliance mode · f624ec70
      Jack Pham 提交于
      Add support for the SuperSpeed Link Layer test case TD.7.34
      which requires the operator to place the port into compliance
      mode, and to subsequently bring it out via reset. Historically
      according to the (now deprecated) USB 3.0 specification a
      SuperSpeed host downstream port would automatically transition
      to Compliance mode from the Polling state if LFPS polling times
      out. However the language in USB 3.1 as well as xHCI 1.1 states
      it may be required to explicitly enable this transition. For
      such hosts this is done by sending a SET_FEATURE(PORT_LINK_STATE)
      with the state set to Compliance to the root hub port.
      
      Similar to the other supported commands, to do this via sysfs:
      
           echo  > /sys/bus/usb/devices/2-0\:1.0/enable_compliance
      
      According to xHCI 1.1 section 4.19.1.2.4.1, this enables the
      transition to compliance mode upon LFPS timeout. Note that this
      can only be issued when the port is in disconnected state. And
      in order to disable this behavior on subsequent transitions, a
      warm reset should be issued. So add another entry to do that:
      
           echo  > /sys/bus/usb/devices/2-0\:1.0/warm_reset
      
      In general these attributes can also be useful for other USB
      SuperSpeed compliance tests such as electrical and eye diagram
      testing which require CPn patterns to be transmitted.
      Signed-off-by: NJack Pham <jackp@codeaurora.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      f624ec70
  3. 22 8月, 2017 5 次提交
  4. 20 8月, 2017 4 次提交
  5. 17 8月, 2017 1 次提交
  6. 15 8月, 2017 4 次提交
  7. 07 8月, 2017 1 次提交
  8. 01 8月, 2017 2 次提交
    • J
      gpio: exar: Use correct property prefix and document bindings · a589e211
      Jan Kiszka 提交于
      The device-specific property should be prefixed with the vendor name,
      not "linux,", as Linus Walleij pointed out. Change this and document the
      bindings of this platform device.
      
      We didn't ship the old binding in a release yet. So we can still change
      it without breaking an official API.
      
      Fixes: 380b1e2f ("gpio-exar/8250-exar: Make set of exported GPIOs configurable")
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Acked-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      a589e211
    • D
      efifb: allow user to disable write combined mapping. · dd0c41f8
      Dave Airlie 提交于
      This patch allows the user to disable write combined mapping
      of the efifb framebuffer console using an nowc option.
      
      A customer noticed major slowdowns while logging to the console
      with write combining enabled, on other tasks running on the same
      CPU. (10x or greater slow down on all other cores on the same CPU
      as is doing the logging).
      
      I reproduced this on a machine with dual CPUs.
      Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz (6 core)
      
      I wrote a test that just mmaps the pci bar and writes to it in
      a loop, while this was running in the background one a single
      core with (taskset -c 1), building a kernel up to init/version.o
      (taskset -c 8) went from 13s to 133s or so. I've yet to explain
      why this occurs or what is going wrong I haven't managed to find
      a perf command that in any way gives insight into this.
      
          11,885,070,715      instructions              #    1.39  insns per cycle
      vs
          12,082,592,342      instructions              #    0.13  insns per cycle
      
      is the only thing I've spotted of interest, I've tried at least:
      dTLB-stores,dTLB-store-misses,L1-dcache-stores,LLC-store,LLC-store-misses,LLC-load-misses,LLC-loads,\mem-loads,mem-stores,iTLB-loads,iTLB-load-misses,cache-references,cache-misses
      
      For now it seems at least a good idea to allow a user to disable write
      combining if they see this until we can figure it out.
      
      Note also most users get a real framebuffer driver loaded when kms
      kicks in, it just happens on these machines the kernel didn't support
      the gpu specific driver.
      Signed-off-by: NDave Airlie <airlied@redhat.com>
      Acked-by: NPeter Jones <pjones@redhat.com>
      Cc: Andy Lutomirski <luto@kernel.org>
      Cc: H. Peter Anvin <hpa@zytor.com>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: NBartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
      dd0c41f8
  9. 28 7月, 2017 2 次提交
  10. 27 7月, 2017 1 次提交
  11. 26 7月, 2017 4 次提交
  12. 20 7月, 2017 1 次提交
  13. 18 7月, 2017 1 次提交
  14. 17 7月, 2017 2 次提交
  15. 16 7月, 2017 3 次提交
  16. 15 7月, 2017 6 次提交