1. 03 Jul, 2017 2 commits
  2. 05 Jun, 2017 3 commits
  3. 24 May, 2017 1 commit
  4. 23 May, 2017 3 commits
  5. 22 May, 2017 2 commits
  6. 19 May, 2017 1 commit
    • Paolo Bonzini's avatar
      iTCO_wdt: all versions count down twice · 1fccb730
      Paolo Bonzini authored
      The ICH9 is listed as having TCO v2, and indeed the behavior in the
      datasheet corresponds to v2 (for example the NO_REBOOT flag is
      accessible via the 16KiB-aligned Root Complex Base Address).
      However, the TCO counts twice just like in v1; the documentation
      of the SECOND_TO_STS bit says: "ICH9 sets this bit to 1 to indicate
      that the TIMEOUT bit had been (or is currently) set and a second
      timeout occurred before the TCO_RLD register was written. If this
      bit is set and the NO_REBOOT config bit is 0, then the ICH9 will
      reboot the system after the second timeout.  The same can be found
      in the BayTrail (Atom E3800) datasheet, and even HOWTOs around
      the Internet say that it will reboot after _twice_ the specified
      I did not find the Apollo Lake datasheet, but because v4/v5 has
      a SECOND_TO_STS bit just like the previous version I'm enabling
      this for Apollo Lake as well.
      Cc: linux-watchdog@vger.kernel.org
      Reviewed-by: default avatarAndy Shevchenko <andy.shevchenko@gmail.com>
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Reviewed-by: default avatarGuenter Roeck <linux@roeck-us.net>
      Signed-off-by: default avatarGuenter Roeck <linux@roeck-us.net>
      Signed-off-by: default avatarWim Van Sebroeck <wim@iguana.be>
  7. 17 May, 2017 1 commit
    • Markus Heiser's avatar
      doc-rst: fixed kernel-doc directives in usb/typec.rst · 5383fae7
      Markus Heiser authored
      Even if this file is not yet included in any toctree, it is parsed by
      Sphinx since it is named '.rst'. This patch fixes the following two
      ERRORs from Sphinx build:
      Documentation/usb/typec.rst:116: ERROR: Error in "kernel-doc" directive:
      invalid option block.
      .. kernel-doc:: drivers/usb/typec/typec.c
         :functions: typec_register_cable typec_unregister_cable typec_register_plug
      Documentation/usb/typec.rst:139: ERROR: Error in "kernel-doc" directive:
      invalid option block.
      .. kernel-doc:: drivers/usb/typec/typec.c
         :functions: typec_set_data_role typec_set_pwr_role typec_set_vconn_role
      Signed-off-by: default avatarMarkus Heiser <markus.heiser@darmarit.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  8. 15 May, 2017 1 commit
  9. 14 May, 2017 1 commit
  10. 12 May, 2017 3 commits
  11. 11 May, 2017 2 commits
  12. 10 May, 2017 4 commits
    • Nicolas Dichtel's avatar
      uapi: export all arch specifics directories · 61562f98
      Nicolas Dichtel authored and Masahiro Yamada's avatar Masahiro Yamada committed
      This patch removes the need of subdir-y. Now all files/directories under
      arch/<arch>/include/uapi/ are exported.
      The only change for userland is the layout of the command 'make
      headers_install_all': directories asm-<arch> are replaced by arch-<arch>/.
      Those new directories contains all files/directories of the specified arch.
      Note that only cris and tile have more directories than only asm:
       - arch-v[10|32] for cris;
       - arch for tile.
      Signed-off-by: default avatarNicolas Dichtel <nicolas.dichtel@6wind.com>
      Signed-off-by: Masahiro Yamada's avatarMasahiro Yamada <yamada.masahiro@socionext.com>
    • Nicolas Dichtel's avatar
      uapi: export all headers under uapi directories · fcc8487d
      Nicolas Dichtel authored and Masahiro Yamada's avatar Masahiro Yamada committed
      Regularly, when a new header is created in include/uapi/, the developer
      forgets to add it in the corresponding Kbuild file. This error is usually
      detected after the release is out.
      In fact, all headers under uapi directories should be exported, thus it's
      useless to have an exhaustive list.
      After this patch, the following files, which were not exported, are now
      exported (with make headers_install_all):
    • Nicolas Dichtel's avatar
      Makefile.headersinst: remove destination-y option · bd73a328
      Nicolas Dichtel authored and Masahiro Yamada's avatar Masahiro Yamada committed
      This option was added in commit c7bb349e
       ("kbuild: introduce destination-y
      for exported headers") but never used in-tree.
      Signed-off-by: default avatarNicolas Dichtel <nicolas.dichtel@6wind.com>
      Acked-by: default avatarPaul Bolle <pebolle@tiscali.nl>
      Signed-off-by: Masahiro Yamada's avatarMasahiro Yamada <yamada.masahiro@socionext.com>
    • Paolo Valente's avatar
      block, bfq: stress that low_latency must be off to get max throughput · 43c1b3d6
      Paolo Valente authored
      The introduction of the BFQ and Kyber I/O schedulers has triggered a
      new wave of I/O benchmarks. Unfortunately, comments and discussions on
      these benchmarks confirm that there is still little awareness that it
      is very hard to achieve, at the same time, a low latency and a high
      throughput. In particular, virtually all benchmarks measure
      throughput, or throughput-related figures of merit, but, for BFQ, they
      use the scheduler in its default configuration. This configuration is
      geared, instead, toward a low latency. This is evidently a sign that
      BFQ documentation is still too unclear on this important aspect. This
      commit addresses this issue by stressing how BFQ configuration must be
      (easily) changed if the only goal is maximum throughput.
      Signed-off-by: default avatarPaolo Valente <paolo.valente@linaro.org>
      Signed-off-by: default avatarJens Axboe <axboe@fb.com>
  13. 09 May, 2017 10 commits
  14. 08 May, 2017 2 commits
  15. 07 May, 2017 1 commit
  16. 06 May, 2017 1 commit
    • Masahiro Yamada's avatar
      docs: bump minimal GNU Make version to 3.81 · 37d69ee3
      Masahiro Yamada authored
      Since 2014, you can't successfully build kernels with GNU Make version
      3.80. Example errors:
        $ git describe
        $ make --version | head -1
        GNU Make 3.80
        $ make defconfig
          HOSTCC  scripts/basic/fixdep
        scripts/Makefile.host:135: *** missing separator.  Stop.
        make: *** [defconfig] Error 2
        $ make ARCH=arm64 help
        arch/arm64/Makefile:43: *** unterminated call to function `warning': missing `)'.  Stop.
        $ make help >/dev/null
        ./Documentation/Makefile.sphinx:25: Extraneous text after `else' directive
        ./Documentation/Makefile.sphinx:31: *** only one `else' per conditional.  Stop.
        make: *** [help] Error 2
      The first breakage was introduced by commit c8589d1e
      handle multi-objs dependency appropriately").  Since then (i.e. v3.18),
      GNU Make 3.80 has not been able to compile the kernel, but nobody has
      ever complained aboutt (or noticed) it.
      Even GNU Make 3.81 is more than 10 years old.  It would not hurt to
      match the documentation with reality instead of fixing makefiles.
      Signed-off-by: Masahiro Yamada's avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
  17. 05 May, 2017 2 commits
    • Amir Goldstein's avatar
    • Keerthy's avatar
      thermal: core: Add a back up thermal shutdown mechanism · ef1d87e0
      Keerthy authored
      orderly_poweroff is triggered when a graceful shutdown
      of system is desired. This may be used in many critical states of the
      kernel such as when subsystems detects conditions such as critical
      temperature conditions. However, in certain conditions in system
      boot up sequences like those in the middle of driver probes being
      initiated, userspace will be unable to power off the system in a clean
      manner and leaves the system in a critical state. In cases like these,
      the /sbin/poweroff will return success (having forked off to attempt
      powering off the system. However, the system overall will fail to
      completely poweroff (since other modules will be probed) and the system
      is still functional with no userspace (since that would have shut itself
      However, there is no clean way of detecting such failure of userspace
      powering off the system. In such scenarios, it is necessary for a backup
      workqueue to be able to force a shutdown of the system when orderly
      shutdown is not successful after a configurable time period.
      Reported-by: default avatarNishanth Menon <nm@ti.com>
      Signed-off-by: default avatarKeerthy <j-keerthy@ti.com>
      Acked-by: default avatarEduardo Valentin <edubezval@gmail.com>
      Signed-off-by: default avatarZhang Rui <rui.zhang@intel.com>