1. 09 2月, 2016 1 次提交
  2. 12 1月, 2016 1 次提交
  3. 27 12月, 2015 1 次提交
    • P
      watchdog: Read device status through sysfs attributes · 33b71126
      Pratyush Anand 提交于
      This patch adds following attributes to watchdog device's sysfs interface
      to read its different status.
      
      * state - reads whether device is active or not
      * identity - reads Watchdog device's identity string.
      * timeout - reads current timeout.
      * timeleft - reads timeleft before watchdog generates a reset
      * bootstatus - reads status of the watchdog device at boot
      * status - reads watchdog device's  internal status bits
      * nowayout - reads whether nowayout feature was set or not
      
      Testing with iTCO_wdt:
       # cd /sys/class/watchdog/watchdog1/
       # ls
      bootstatus  dev  device  identity  nowayout  power  state
      subsystem  timeleft  timeout  uevent
       # cat identity
      iTCO_wdt
       # cat timeout
      30
       # cat state
      inactive
       # echo > /dev/watchdog1
       # cat timeleft
      26
       # cat state
      active
       # cat bootstatus
      0
       # cat nowayout
      0
      Signed-off-by: NPratyush Anand <panand@redhat.com>
      Reviewed-by: NGuenter Roeck <linux@roeck-us.net>
      Signed-off-by: NGuenter Roeck <linux@roeck-us.net>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      33b71126
  4. 23 12月, 2015 2 次提交
    • M
      IB/cma: Add configfs for rdma_cm · 045959db
      Matan Barak 提交于
      Users would like to control the behaviour of rdma_cm.
      For example, old applications which don't set the
      required RoCE gid type could be executed on RoCE V2
      network types. In order to support this configuration,
      we implement a configfs for rdma_cm.
      
      In order to use the configfs, one needs to mount it and
      mkdir <IB device name> inside rdma_cm directory.
      
      The patch adds support for a single configuration file,
      default_roce_mode. The mode can either be "IB/RoCE v1" or
      "RoCE v2".
      Signed-off-by: NMatan Barak <matanb@mellanox.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      045959db
    • M
      IB/core: Add gid attributes to sysfs · 470be516
      Matan Barak 提交于
      This patch set adds attributes of net device and gid type to each GID
      in the GID table. Users that use verbs directly need to specify
      the GID index. Since the same GID could have different types or
      associated net devices, users should have the ability to query the
      associated GID attributes. Adding these attributes to sysfs.
      Signed-off-by: NMatan Barak <matanb@mellanox.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      470be516
  5. 21 12月, 2015 1 次提交
  6. 19 12月, 2015 1 次提交
  7. 16 12月, 2015 1 次提交
  8. 15 12月, 2015 1 次提交
  9. 08 12月, 2015 1 次提交
  10. 07 12月, 2015 1 次提交
  11. 05 12月, 2015 1 次提交
  12. 04 12月, 2015 2 次提交
  13. 02 12月, 2015 2 次提交
    • L
      usb: core: lpm: add sysfs node for usb3 lpm permit · 513072d9
      Lu Baolu 提交于
      USB3 LPM is default on in Linux kernel if both xHCI host controller
      and the USB devices declare to be LPM-capable. Unfortunately, some
      devices are known to work well with LPM disabled, but to be broken
      if LPM is enabled, although it declares the LPM capability.  Users
      won't be able to use this kind of devices, until someone puts them
      in the kernel blacklist and gets the kernel upgraded.
      
      This patch adds a sysfs node to permit or forbit USB3 LPM U1 or U2
      entry for a port. The settings apply to both before and after device
      enumeration. Supported values are "0" - neither u1 nor u2 permitted,
      "u1" - only u1 is permitted, "u2" - only u2 is permitted, "u1_u2" -
      both u1 and u2 are permitted. With this interface, users can use an
      LPM-unfriendly USB device on a released Linux kernel.
      Signed-off-by: NLu Baolu <baolu.lu@linux.intel.com>
      Signed-off-by: NZhuang Jin Can <jin.can.zhuang@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      513072d9
    • L
      usb: core: lpm: fix usb3_hardware_lpm sysfs node · bf5ce5bf
      Lu Baolu 提交于
      Commit 655fe4ef ("usbcore: add sysfs support to xHCI usb3
      hardware LPM") introduced usb3_hardware_lpm sysfs node. This
      doesn't show the correct status of USB3 U1 and U2 LPM status.
      
      This patch fixes this by replacing usb3_hardware_lpm with two
      nodes, usb3_hardware_lpm_u1 (for U1) and usb3_hardware_lpm_u2
      (for U2), and recording the U1/U2 LPM status in right places.
      
      This patch should be back-ported to kernels as old as 4.3,
      that contains Commit 655fe4ef ("usbcore: add sysfs support
      to xHCI usb3 hardware LPM").
      
      Cc: stable@vger.kernel.org
      Signed-off-by: NLu Baolu <baolu.lu@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      bf5ce5bf
  14. 10 11月, 2015 1 次提交
  15. 22 10月, 2015 1 次提交
  16. 21 10月, 2015 1 次提交
  17. 19 10月, 2015 1 次提交
  18. 18 10月, 2015 1 次提交
  19. 13 10月, 2015 1 次提交
    • C
      f2fs: export ra_nid_pages to sysfs · ea1a29a0
      Chao Yu 提交于
      After finishing building free nid cache, we will try to readahead
      asynchronously 4 more pages for the next reloading, the count of
      readahead nid pages is fixed.
      
      In some case, like SMR drive, read less sectors with fixed count
      each time we trigger RA may be low efficient, since we will face
      high seeking overhead, so we'd better let user to configure this
      parameter from sysfs in specific workload.
      Signed-off-by: NChao Yu <chao2.yu@samsung.com>
      Signed-off-by: NJaegeuk Kim <jaegeuk@kernel.org>
      ea1a29a0
  20. 11 10月, 2015 3 次提交
  21. 10 10月, 2015 1 次提交
  22. 08 10月, 2015 2 次提交
  23. 05 10月, 2015 5 次提交
    • A
      intel_th: Add PTI output driver · 14cdbf04
      Alexander Shishkin 提交于
      Parallel Trace Interface (PTI) unit is a trace output device that sends
      data over a PTI port.
      
      The driver provides interfaces to configure bus width, bus clock divider
      and mode. Tracing is enabled via output device's "active" attribute.
      Signed-off-by: NAlexander Shishkin <alexander.shishkin@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      14cdbf04
    • A
      intel_th: Add Memory Storage Unit driver · ba82664c
      Alexander Shishkin 提交于
      Memory Storage Unit (MSU) is a trace output device that collects trace
      data to system memory. It consists of 2 independent Memory Storage
      Controllers (MSCs).
      
      This driver provides userspace interfaces to configure in-memory tracing
      parameters, such as contiguous (high-order allocation) buffer or multiblock
      (scatter list) buffer mode, wrapping (data overwrite) and number and sizes
      of windows in multiblock mode. Userspace can read the buffers via mmap()ing
      or read()ing of the corresponding device node.
      Signed-off-by: NLaurent Fert <laurent.fert@intel.com>
      Signed-off-by: NAlexander Shishkin <alexander.shishkin@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ba82664c
    • A
      intel_th: Add Global Trace Hub driver · b27a6a3f
      Alexander Shishkin 提交于
      Global Trace Hub (GTH) is the central component of Intel TH architecture;
      it carries out switching between the trace sources and trace outputs, can
      enable/disable tracing, perform STP encoding, internal buffering, control
      backpressure from outputs to sources and so on.
      
      This property is also reflected in the software model; GTH (switch) driver
      is required for the other subdevices to probe, because it matches trace
      output devices against its output ports and configures them accordingly.
      
      It also implements an interface for output ports to request trace enabling
      or disabling and a few other useful things.
      
      For userspace, it provides an attribute group "masters", which allows
      configuration of per-master trace output destinations for up to master 255
      and "256+" meaning "masters 256 and above". It also provides an attribute
      group to discover and configure some of the parameters of its output ports,
      called "outputs". Via these the user can set up data retention policy for
      an individual output port or check if it is in reset state.
      Signed-off-by: NLaurent Fert <laurent.fert@intel.com>
      Signed-off-by: NAlexander Shishkin <alexander.shishkin@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b27a6a3f
    • A
      intel_th: Add driver infrastructure for Intel(R) Trace Hub devices · 39f40346
      Alexander Shishkin 提交于
      Intel(R) Trace Hub (TH) is a set of hardware blocks (subdevices) that
      produce, switch and output trace data from multiple hardware and
      software sources over several types of trace output ports encoded
      in System Trace Protocol (MIPI STPv2) and is intended to perform
      full system debugging.
      
      For these subdevices, we create a bus, where they can be discovered
      and configured by userspace software.
      
      This patch creates this bus infrastructure, three types of devices
      (source, output, switch), resource allocation, some callback mechanisms
      to facilitate communication between the subdevices' drivers and some
      common sysfs attributes.
      Signed-off-by: NAlexander Shishkin <alexander.shishkin@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      39f40346
    • A
      stm class: Introduce an abstraction for System Trace Module devices · 7bd1d409
      Alexander Shishkin 提交于
      A System Trace Module (STM) is a device exporting data in System Trace
      Protocol (STP) format as defined by MIPI STP standards. Examples of such
      devices are Intel(R) Trace Hub and Coresight STM.
      
      This abstraction provides a unified interface for software trace sources
      to send their data over an STM device to a debug host. In order to do
      that, such a trace source needs to be assigned a pair of master/channel
      identifiers that all the data from this source will be tagged with. The
      STP decoder on the debug host side will use these master/channel tags to
      distinguish different trace streams from one another inside one STP
      stream.
      
      This abstraction provides a configfs-based policy management mechanism
      for dynamic allocation of these master/channel pairs based on trace
      source-supplied string identifier. It has the flexibility of being
      defined at runtime and at the same time (provided that the policy
      definition is aligned with the decoding end) consistency.
      
      For userspace trace sources, this abstraction provides write()-based and
      mmap()-based (if the underlying stm device allows this) output mechanism.
      
      For kernel-side trace sources, we provide "stm_source" device class that
      can be connected to an stm device at run time.
      
      Cc: linux-api@vger.kernel.org
      Reviewed-by: NMathieu Poirier <mathieu.poirier@linaro.org>
      Signed-off-by: NAlexander Shishkin <alexander.shishkin@linux.intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      7bd1d409
  24. 04 10月, 2015 1 次提交
  25. 01 10月, 2015 3 次提交
  26. 24 9月, 2015 3 次提交