1. 25 Feb, 2018 1 commit
  2. 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: 's avatarKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: 's avatarPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: 's avatarThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      b2441318
  3. 24 Aug, 2017 1 commit
  4. 03 Jun, 2017 1 commit
    • Peter Rosin's avatar
      mux: minimal mux subsystem · a3b02a9c
      Peter Rosin authored
      Add a new minimalistic subsystem that handles multiplexer controllers.
      When multiplexers are used in various places in the kernel, and the
      same multiplexer controller can be used for several independent things,
      there should be one place to implement support for said multiplexer
      controller.
      
      A single multiplexer controller can also be used to control several
      parallel multiplexers, that are in turn used by different subsystems
      in the kernel, leading to a need to coordinate multiplexer accesses.
      The multiplexer subsystem handles this coordination.
      
      Thanks go out to Lars-Peter Clausen, Jonathan Cameron, Rob Herring,
      Wolfram Sang, Paul Gortmaker, Dan Carpenter, Colin Ian King, Greg
      Kroah-Hartman and last but certainly not least to Philipp Zabel for
      helpful comments, reviews, patches and general encouragement!
      Reviewed-by: 's avatarJonathan Cameron <jic23@kernel.org>
      Signed-off-by: 's avatarPeter Rosin <peda@axentia.se>
      Reviewed-by: 's avatarPhilipp Zabel <p.zabel@pengutronix.de>
      Tested-by: 's avatarPhilipp Zabel <p.zabel@pengutronix.de>
      Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      a3b02a9c
  5. 25 Apr, 2017 1 commit
    • Alexey Brodkin's avatar
      usb: Make sure usb/phy/of gets built-in · 3d615964
      Alexey Brodkin authored
      DWC3 driver uses of_usb_get_phy_mode() which is
      implemented in drivers/usb/phy/of.c and in bare minimal
      configuration it might not be pulled in kernel binary.
      
      In case of ARC or ARM this could be easily reproduced with
      "allnodefconfig" +CONFIG_USB=m +CONFIG_USB_DWC3=m.
      
      On building all ends-up with:
      ---------------------->8------------------
        Kernel: arch/arm/boot/Image is ready
        Kernel: arch/arm/boot/zImage is ready
        Building modules, stage 2.
        MODPOST 5 modules
      ERROR: "of_usb_get_phy_mode" [drivers/usb/dwc3/dwc3.ko] undefined!
      make[1]: *** [__modpost] Error 1
      make: *** [modules] Error 2
      ---------------------->8------------------
      Signed-off-by: 's avatarAlexey Brodkin <abrodkin@synopsys.com>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
      Cc: Geert Uytterhoeven <geert+renesas@glider.be>
      Cc: Nicolas Pitre <nicolas.pitre@linaro.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Felipe Balbi <balbi@kernel.org>
      Cc: Felix Fietkau <nbd@nbd.name>
      Cc: Jeremy Kerr <jk@ozlabs.org>
      Cc: linux-snps-arc@lists.infradead.org
      Cc: stable@vger.kernel.org
      Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      3d615964
  6. 13 Apr, 2017 1 commit
    • Dan Williams's avatar
      dax: refactor dax-fs into a generic provider of 'struct dax_device' instances · 7b6be844
      Dan Williams authored
      We want dax capable drivers to be able to publish a set of dax
      operations [1]. However, we do not want to further abuse block_devices
      to advertise these operations. Instead we will attach these operations
      to a dax device and add a lookup mechanism to go from block device path
      to a dax device. A dax capable driver like pmem or brd is responsible
      for registering a dax device, alongside a block device, and then a dax
      capable filesystem is responsible for retrieving the dax device by path
      name if it wants to call dax_operations.
      
      For now, we refactor the dax pseudo-fs to be a generic facility, rather
      than an implementation detail, of the device-dax use case. Where a "dax
      device" is just an inode + dax infrastructure, and "Device DAX" is a
      mapping service layered on top of that base 'struct dax_device'.
      "Filesystem DAX" is then a mapping service that layers a filesystem on
      top of that same base device. Filesystem DAX is associated with a
      block_device for now, but perhaps directly to a dax device in the
      future, or for new pmem-only filesystems.
      
      [1]: https://lkml.org/lkml/2017/1/19/880Suggested-by: 's avatarChristoph Hellwig <hch@lst.de>
      Signed-off-by: 's avatarDan Williams <dan.j.williams@intel.com>
      7b6be844
  7. 11 Apr, 2017 1 commit
  8. 09 Mar, 2017 1 commit
    • Jens Wiklander's avatar
      tee: generic TEE subsystem · 967c9cca
      Jens Wiklander authored
      Initial patch for generic TEE subsystem.
      This subsystem provides:
      * Registration/un-registration of TEE drivers.
      * Shared memory between normal world and secure world.
      * Ioctl interface for interaction with user space.
      * Sysfs implementation_id of TEE driver
      
      A TEE (Trusted Execution Environment) driver is a driver that interfaces
      with a trusted OS running in some secure environment, for example,
      TrustZone on ARM cpus, or a separate secure co-processor etc.
      
      The TEE subsystem can serve a TEE driver for a Global Platform compliant
      TEE, but it's not limited to only Global Platform TEEs.
      
      This patch builds on other similar implementations trying to solve
      the same problem:
      * "optee_linuxdriver" by among others
        Jean-michel DELORME<jean-michel.delorme@st.com> and
        Emmanuel MICHEL <emmanuel.michel@st.com>
      * "Generic TrustZone Driver" by Javier González <javier@javigon.com>
      Acked-by: 's avatarAndreas Dannenberg <dannenberg@ti.com>
      Tested-by: Jerome Forissier <jerome.forissier@linaro.org> (HiKey)
      Tested-by: Volodymyr Babchuk <vlad.babchuk@gmail.com> (RCAR H3)
      Tested-by: 's avatarScott Branden <scott.branden@broadcom.com>
      Reviewed-by: 's avatarJavier González <javier@javigon.com>
      Signed-off-by: 's avatarJens Wiklander <jens.wiklander@linaro.org>
      967c9cca
  9. 21 Feb, 2017 1 commit
  10. 10 Feb, 2017 1 commit
  11. 16 Nov, 2016 1 commit
  12. 30 Sep, 2016 1 commit
    • Alistair Popple's avatar
      ipmi: add an Aspeed BT IPMI BMC driver · 54f9c4d0
      Alistair Popple authored
      This patch adds a simple device driver to expose the iBT interface on
      Aspeed SOCs (AST2400 and AST2500) as a character device. Such SOCs are
      commonly used as BMCs (BaseBoard Management Controllers) and this
      driver implements the BMC side of the BT interface.
      
      The BT (Block Transfer) interface is used to perform in-band IPMI
      communication between a host and its BMC. Entire messages are buffered
      before sending a notification to the other end, host or BMC, that
      there is data to be read. Usually, the host emits requests and the BMC
      responses but the specification provides a mean for the BMC to send
      SMS Attention (BMC-to-Host attention or System Management Software
      attention) messages.
      
      For this purpose, the driver introduces a specific ioctl on the
      device: 'BT_BMC_IOCTL_SMS_ATN' that can be used by the system running
      on the BMC to signal the host of such an event.
      
      The device name defaults to '/dev/ipmi-bt-host'
      Signed-off-by: 's avatarAlistair Popple <alistair@popple.id.au>
      Signed-off-by: 's avatarJeremy Kerr <jk@ozlabs.org>
      Signed-off-by: 's avatarJoel Stanley <joel@jms.id.au>
      [clg: - checkpatch fixes
            - added a devicetree binding documentation
            - replace 'bt_host' by 'bt_bmc' to reflect that the driver is
              the BMC side of the IPMI BT interface
            - renamed the device to 'ipmi-bt-host'
            - introduced a temporary buffer to copy_{to,from}_user
            - used platform_get_irq()
            - moved the driver under drivers/char/ipmi/ but kept it as a misc
              device
            - changed the compatible cell to "aspeed,ast2400-bt-bmc"
      ]
      Signed-off-by: 's avatarCédric Le Goater <clg@kaod.org>
      Acked-by: 's avatarArnd Bergmann <arnd@arndb.de>
      [clg: - checkpatch --strict fixes
            - removed the use of devm_iounmap, devm_kfree in cleanup paths
            - introduced an atomic-t to limit opens to 1
            - introduced a mutex to protect write/read operations]
      Acked-by: 's avatarRob Herring <robh@kernel.org>
      Signed-off-by: 's avatarCédric Le Goater <clg@kaod.org>
      Signed-off-by: 's avatarCorey Minyard <cminyard@mvista.com>
      54f9c4d0
  13. 23 Sep, 2016 1 commit
  14. 02 Aug, 2016 1 commit
  15. 27 Jun, 2016 1 commit
  16. 15 Jun, 2016 1 commit
  17. 14 Jun, 2016 1 commit
  18. 30 May, 2016 1 commit
  19. 21 May, 2016 1 commit
    • Dan Williams's avatar
      /dev/dax, pmem: direct access to persistent memory · ab68f262
      Dan Williams authored
      Device DAX is the device-centric analogue of Filesystem DAX
      (CONFIG_FS_DAX).  It allows memory ranges to be allocated and mapped
      without need of an intervening file system.  Device DAX is strict,
      precise and predictable.  Specifically this interface:
      
      1/ Guarantees fault granularity with respect to a given page size (pte,
      pmd, or pud) set at configuration time.
      
      2/ Enforces deterministic behavior by being strict about what fault
      scenarios are supported.
      
      For example, by forcing MADV_DONTFORK semantics and omitting MAP_PRIVATE
      support device-dax guarantees that a mapping always behaves/performs the
      same once established.  It is the "what you see is what you get" access
      mechanism to differentiated memory vs filesystem DAX which has
      filesystem specific implementation semantics.
      
      Persistent memory is the first target, but the mechanism is also
      targeted for exclusive allocations of performance differentiated memory
      ranges.
      
      This commit is limited to the base device driver infrastructure to
      associate a dax device with pmem range.
      
      Cc: Jeff Moyer <jmoyer@redhat.com>
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Cc: Dave Hansen <dave.hansen@linux.intel.com>
      Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
      Reviewed-by: 's avatarJohannes Thumshirn <jthumshirn@suse.de>
      Signed-off-by: 's avatarDan Williams <dan.j.williams@intel.com>
      ab68f262
  20. 08 Dec, 2015 1 commit
    • Krzysztof Kozlowski's avatar
      power: Fix unmet dependency on POWER_SUPPLY by POWER_RESET by uncoupling them · f96576bd
      Krzysztof Kozlowski authored
      Currently the reset/power off handlers (POWER_RESET) and Adaptive Voltage
      Scaling class (POWER_AVS) are not built when POWER_SUPPLY is disabled.
      The POWER_RESET is also not visible in drivers main section of config.
      
      However they do not really depend on power supply so they can be built
      always. The objects for power supply drivers already depend on
      particular Kconfig symbols so there is no need for any changes in
      drivers/power/Makefile.
      
      This allows selecting POWER_RESET from main drivers config section and
      fixes following build warning (encountered on ARM exynos defconfig when
      POWER_SUPPLY is disabled manually):
      
      warning: (ARCH_HISI && ARCH_INTEGRATOR && ARCH_EXYNOS && ARCH_VEXPRESS && REALVIEW_DT) selects POWER_RESET which has unmet direct dependencies (POWER_SUPPLY)
      warning: (ARCH_EXYNOS) selects POWER_RESET_SYSCON which has unmet direct dependencies (POWER_SUPPLY && POWER_RESET && OF)
      warning: (ARCH_EXYNOS) selects POWER_RESET_SYSCON_POWEROFF which has unmet direct dependencies (POWER_SUPPLY && POWER_RESET && OF)
      Reported-by: 's avatarPavel Fedin <p.fedin@samsung.com>
      Signed-off-by: 's avatarKrzysztof Kozlowski <k.kozlowski@samsung.com>
      Signed-off-by: 's avatarSebastian Reichel <sre@kernel.org>
      f96576bd
  21. 16 Nov, 2015 1 commit
    • Matias Bjørling's avatar
      null_blk: register as a LightNVM device · b2b7e001
      Matias Bjørling authored
      Add support for registering as a LightNVM device. This allows us to
      evaluate the performance of the LightNVM subsystem.
      
      In /drivers/Makefile, LightNVM is moved above block device drivers
      to make sure that the LightNVM media managers have been initialized
      before drivers under /drivers/block are initialized.
      Signed-off-by: 's avatarMatias Bjørling <m@bjorling.me>
      Fix by Jens Axboe to remove unneeded slab cache and the following
      memory leak.
      Signed-off-by: 's avatarJens Axboe <axboe@fb.com>
      b2b7e001
  22. 29 Oct, 2015 1 commit
    • Matias Bjørling's avatar
      lightnvm: Support for Open-Channel SSDs · cd9e9808
      Matias Bjørling authored
      Open-channel SSDs are devices that share responsibilities with the host
      in order to implement and maintain features that typical SSDs keep
      strictly in firmware. These include (i) the Flash Translation Layer
      (FTL), (ii) bad block management, and (iii) hardware units such as the
      flash controller, the interface controller, and large amounts of flash
      chips. In this way, Open-channels SSDs exposes direct access to their
      physical flash storage, while keeping a subset of the internal features
      of SSDs.
      
      LightNVM is a specification that gives support to Open-channel SSDs
      LightNVM allows the host to manage data placement, garbage collection,
      and parallelism. Device specific responsibilities such as bad block
      management, FTL extensions to support atomic IOs, or metadata
      persistence are still handled by the device.
      
      The implementation of LightNVM consists of two parts: core and
      (multiple) targets. The core implements functionality shared across
      targets. This is initialization, teardown and statistics. The targets
      implement the interface that exposes physical flash to user-space
      applications. Examples of such targets include key-value store,
      object-store, as well as traditional block devices, which can be
      application-specific.
      
      Contributions in this patch from:
      
        Javier Gonzalez <jg@lightnvm.io>
        Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
        Jesper Madsen <jmad@itu.dk>
      Signed-off-by: 's avatarMatias Bjørling <m@bjorling.me>
      Signed-off-by: 's avatarJens Axboe <axboe@fb.com>
      cd9e9808
  23. 09 Oct, 2015 1 commit
  24. 07 Oct, 2015 1 commit
    • Alan Tull's avatar
      add FPGA manager core · 6a8c3be7
      Alan Tull authored
      API to support programming FPGA's.
      
      The following functions are exported as GPL:
      * fpga_mgr_buf_load
         Load fpga from image in buffer
      
      * fpga_mgr_firmware_load
         Request firmware and load it to the FPGA.
      
      * fpga_mgr_register
      * fpga_mgr_unregister
         FPGA device drivers can be added by calling
         fpga_mgr_register() to register a set of
         fpga_manager_ops to do device specific stuff.
      
      * of_fpga_mgr_get
      * fpga_mgr_put
         Get/put a reference to a fpga manager.
      
      The following sysfs files are created:
      * /sys/class/fpga_manager/<fpga>/name
        Name of low level driver.
      
      * /sys/class/fpga_manager/<fpga>/state
        State of fpga manager
      Signed-off-by: 's avatarAlan Tull <atull@opensource.altera.com>
      Acked-by: 's avatarMichal Simek <michal.simek@xilinx.com>
      Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      6a8c3be7
  25. 04 Oct, 2015 2 commits
    • Alexander Shishkin's avatar
      intel_th: Add driver infrastructure for Intel(R) Trace Hub devices · 39f40346
      Alexander Shishkin authored
      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: 's avatarAlexander Shishkin <alexander.shishkin@linux.intel.com>
      Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      39f40346
    • Alexander Shishkin's avatar
      stm class: Introduce an abstraction for System Trace Module devices · 7bd1d409
      Alexander Shishkin authored
      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: 's avatarMathieu Poirier <mathieu.poirier@linaro.org>
      Signed-off-by: 's avatarAlexander Shishkin <alexander.shishkin@linux.intel.com>
      Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      7bd1d409
  26. 05 Aug, 2015 1 commit
  27. 31 Jul, 2015 1 commit
    • Mark Rutland's avatar
      arm: perf: factor arm_pmu core out to drivers · fa8ad788
      Mark Rutland authored
      To enable sharing of the arm_pmu code with arm64, this patch factors it
      out to drivers/perf/. A new drivers/perf directory is added for
      performance monitor drivers to live under.
      
      MAINTAINERS is updated accordingly. Files added previously without a
      corresponsing MAINTAINERS update (perf_regs.c, perf_callchain.c, and
      perf_event.h) are also added.
      
      Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
      Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Will Deacon <will.deacon@arm.com>
      Signed-off-by: 's avatarMark Rutland <mark.rutland@arm.com>
      [will: augmented Kconfig help slightly]
      Signed-off-by: 's avatarWill Deacon <will.deacon@arm.com>
      fa8ad788
  28. 16 Jul, 2015 1 commit
  29. 25 Jun, 2015 1 commit
  30. 24 May, 2015 1 commit
  31. 03 Apr, 2015 1 commit
  32. 22 Dec, 2014 1 commit
    • Oded Gabbay's avatar
      drivers: Move iommu/ before gpu/ in Makefile · 1bacc894
      Oded Gabbay authored
      AMD GPU devices are dependent on AMD IOMMU controller functionality to allow
      the GPU to access a process's virtual memory address space, without the need
      for pinning the memory.
      
      This patch changes the order in the drivers makefile, so iommu/ subsystem is
      linked before gpu/ subsystem. That way, if the gpu and iommu drivers are
      compiled inside the kernel image (not as modules), the correct order of device
      loading is still maintained (iommu module is loaded before gpu module).
      Signed-off-by: 's avatarOded Gabbay <oded.gabbay@amd.com>
      Reviewed-by: 's avatarChristian König <christian.koenig@amd.com>
      1bacc894
  33. 07 Nov, 2014 1 commit
    • Pratik Patel's avatar
      coresight: add CoreSight core layer framework · a06ae860
      Pratik Patel authored
      CoreSight components are compliant with the ARM CoreSight
      architecture specification and can be connected in various
      topologies to suit a particular SoC tracing needs. These trace
      components can generally be classified as sources, links and
      sinks. Trace data produced by one or more sources flows through
      the intermediate links connecting the source to the currently
      selected sink.
      
      The CoreSight framework provides an interface for the CoreSight trace
      drivers to register themselves with. It's intended to build up a
      topological view of the CoreSight components and configure the
      correct serie of components on user input via sysfs.
      
      For eg., when enabling a source, the framework builds up a path
      consisting of all the components connecting the source to the
      currently selected sink(s) and enables all of them.
      
      The framework also supports switching between available sinks
      and provides status information to user space applications
      through the debugfs interface.
      Signed-off-by: 's avatarPratik Patel <pratikp@codeaurora.org>
      Signed-off-by: 's avatarMathieu Poirier <mathieu.poirier@linaro.org>
      Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      a06ae860
  34. 20 Oct, 2014 1 commit
  35. 08 Jul, 2014 1 commit
  36. 23 Jun, 2014 1 commit
  37. 19 Jun, 2014 1 commit
    • Andreas Noever's avatar
      thunderbolt: Add initial cactus ridge NHI support · 16603153
      Andreas Noever authored
      Thunderbolt hotplug is supposed to be handled by the firmware. But Apple
      decided to implement thunderbolt at the operating system level. The
      firmare only initializes thunderbolt devices that are present at boot
      time. This driver enables hotplug of thunderbolt of non-chained
      thunderbolt devices on Apple systems with a cactus ridge controller.
      
      This first patch adds the Kconfig file as well the parts of the driver
      which talk directly to the hardware (that is pci device setup, interrupt
      handling and RX/TX ring management).
      Signed-off-by: 's avatarAndreas Noever <andreas.noever@gmail.com>
      Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      16603153
  38. 27 May, 2014 1 commit
  39. 23 May, 2014 1 commit