1. 05 Apr, 2016 1 commit
  2. 20 Feb, 2016 1 commit
    • Paul Gortmaker's avatar
      drivers/hwtracing: make coresight-* explicitly non-modular · 941943cf
      Paul Gortmaker authored
      None of the Kconfig currently controlling compilation of any of
      the files here are tristate, meaning that none of it currently
      is being built as a module by anyone.
      
      We need not be concerned about .remove functions and blocking the
      unbind sysfs operations, since that was already done in a recent
      commit.
      
      Lets remove any remaining modular references, so that when reading the
      drivers there is no doubt they are builtin-only.
      
      All drivers get mostly the same changes, so they are handled in batch.
      Changes are (1) convert to builtin_amba_driver, (2) delete module.h
      include where unused, and (3) relocate the description into the
      comments so we don't need MODULE_DESCRIPTION and associated tags.
      
      The etm3x and etm4x use module_param_named, and have been adjusted
      to just include moduleparam.h for that purpose.
      
      In commit f309d444 ("platform_device:
      better support builtin boilerplate avoidance") we introduced the
      builtin_driver macro.
      
      Here we use that support and extend it to amba driver registration,
      so where a driver is clearly non-modular and builtin-only, we can
      update with the simple mapping of
      
           module_amba_driver(...)  ---> builtin_amba_driver(...)
      
      Since module_amba_driver() uses the same init level priority as
      builtin_amba_driver() the init ordering remains unchanged with
      this commit.
      
      Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
      Cc: linux-arm-kernel@lists.infradead.org
      Signed-off-by: default avatarPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: default avatarMathieu Poirier <mathieu.poirier@linaro.org>
      Acked-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      941943cf
  3. 13 Dec, 2015 1 commit
  4. 19 Oct, 2015 1 commit
  5. 04 Sep, 2015 1 commit
  6. 04 Aug, 2015 1 commit
  7. 17 Jul, 2015 1 commit
  8. 17 Mar, 2015 1 commit
  9. 10 Feb, 2015 1 commit
  10. 16 Jan, 2015 1 commit
  11. 17 Nov, 2014 1 commit
  12. 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: default avatarPratik Patel <pratikp@codeaurora.org>
      Signed-off-by: default avatarMathieu Poirier <mathieu.poirier@linaro.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      a06ae860
  13. 24 Sep, 2014 1 commit
  14. 02 Jun, 2014 1 commit
  15. 25 May, 2014 1 commit
  16. 19 May, 2014 1 commit
  17. 12 May, 2014 2 commits
  18. 29 Apr, 2014 1 commit
  19. 02 Jan, 2014 1 commit
  20. 17 Dec, 2013 1 commit
  21. 08 Dec, 2013 1 commit
  22. 08 Nov, 2013 1 commit
  23. 31 Oct, 2013 1 commit
  24. 14 Oct, 2013 1 commit
  25. 02 Sep, 2013 1 commit
  26. 05 Jul, 2013 1 commit
  27. 29 Mar, 2013 1 commit
    • Chanho Min's avatar
      ARM: PL011: Add support for Rx DMA buffer polling. · cb06ff10
      Chanho Min authored
      In DMA support, The received data is not pushed to tty until the DMA buffer
      is filled. But some megabyte rate chips such as BT expect fast response and
      data should be pushed immediately. In order to fix this issue, We suggest
      the use of the timer for polling DMA buffer.
      In our test, no data loss occurred at high-baudrate as compared with interrupt-
      driven (We tested with 3Mbps).
      We changes:
      
      - We add timer for polling. If we set poll_timer to 10, every 10ms,
       timer handler checks the residue in the dma buffer and transfer data
       to the tty. Also, last_residue is updated for the next polling.
      
      - poll_timeout is used to prevent the timer's system cost.
        If poll_timeout is set to 3000 and no data is received in 3 seconds,
        we inactivate poll timer and driver falls back to interrupt-driven.
        When data is received again in FIFO and UART irq is occurred, we switch
        back to DMA mode and start polling.
      
      - We use consistent DMA mappings to avoid from the frequent cache operation
        of the timer function for default.
      
      - pl011_dma_rx_chars is modified. the pending size is recalculated because
        data can be taken by polling.
      
      - the polling time is adjusted if dma rx poll is enabled but no rate is
        specified. Ideal polling interval to push 1 character at every interval
        is the reciprocal of 'baud rate / 10 line bits per character / 1000 ms
        per sec'. But It is very aggressive to system. Experimentally,
       '10000000 / baud' is suitable to receive dozens of characters. the poll rate
       can be specified statically by dma_rx_poll_rate of the platform data as well.
      
      Changes compared to v1:
       - Use of consistent DMA mappings.
       - Added dma_rx_poll_rate in platform data to specify the polling interval.
       - Added dma_rx_poll_timeout in platform data to specify the polling timeout.
      
      Changes compared to v2:
       - Use of consistent DMA mappings for default.
       - Added dma_rx_poll_enable in platform data to adjust the polling time
         according to the baud rate.
       - remove unnecessary lock from the polling function.
      Signed-off-by: default avatarChanho Min <chanho.min@lge.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      cb06ff10
  28. 30 Jan, 2013 1 commit
  29. 13 Jan, 2013 1 commit
  30. 03 Dec, 2012 1 commit
  31. 10 Sep, 2012 1 commit
  32. 22 Aug, 2012 1 commit
  33. 02 Jul, 2012 1 commit
  34. 01 Jul, 2012 5 commits
  35. 25 Apr, 2012 1 commit