1. 21 7月, 2014 2 次提交
  2. 10 5月, 2014 1 次提交
  3. 06 5月, 2014 1 次提交
  4. 09 4月, 2014 1 次提交
    • H
      ACPI: Update the ACPI spec information in Kconfig · c7f5220d
      Hanjun Guo 提交于
      The UEFI Forum included the ACPI spec in its portfolio in October 2013
      and will host future spec iterations, following the ACPI v5.0a release.
      
      A UEFI Forum working group named ACPI Specification Working Group (ASWG)
      has been established to handle future ACPI developments, any UEFI member
      can join the group and contribute to ACPI specification.
      
      So update the ownership and developers for ACPI in Kconfig accordingly,
      and add another website link to ACPI specification too.
      Signed-off-by: NHanjun Guo <hanjun.guo@linaro.org>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      c7f5220d
  5. 20 3月, 2014 1 次提交
  6. 19 2月, 2014 1 次提交
  7. 05 2月, 2014 1 次提交
    • A
      ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE_ONLY · af1ae78a
      Al Stone 提交于
      ACPI hardware reduced mode exists to allow newer platforms to use a
      simpler form of ACPI that does not require supporting legacy versions
      of the specification and their associated hardware.  This mode was
      introduced in the ACPI 5.0 specification.
      
      The ACPI hardware reduced mode is supposed to be used on systems
      having the HW_REDUCED_ACPI flag set in the FADT.  ACPICA checks
      that flag to determine whether or not it should work in the HW
      reduced mode and there are pieces of code in it that will never
      be used in that case.
      
      Since some architecutres will always use the ACPI HW reduced mode,
      it doesn't make sense for them to ever compile support for anything
      else.  Thus, they should set the flag ACPI_REDUCED_HARDWARE to TRUE
      in the ACPICA source.  To enable them to do that, introduce a new
      kernel configuration option, CONFIG_ACPI_REDUCED_HARDWARE_ONLY, that
      will cause the ACPICA's ACPI_REDUCED_HARDWARE flag to be TRUE when
      set.
      
      Introducing this configuration item is based on suggestions from Lv
      Zheng saying that this does not belong in ACPICA, but rather to the
      Linux kernel itself.
      
      References: http://www.spinics.net/lists/linux-acpi/msg46369.htmlSigned-off-by: NHanjun Guo <hanjun.guo@linaro.org>
      Signed-off-by: NAl Stone <al.stone@linaro.org>
      [rjw: Subject and changelog]
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      af1ae78a
  8. 20 12月, 2013 1 次提交
  9. 13 11月, 2013 1 次提交
    • L
      ACPI: delete CONFIG_ACPI_BLACKLIST_YEAR · 4c47cb19
      Len Brown 提交于
      About 10 years ago, this option was created to help
      distros enable ACPI and not get distracted by ACPI
      BIOS issues in machines which were deemed old
      at that time, eg 1999 and earlier.
      
      After a couple of years, the high volume distros
      stopped bothering to set this option, and instead
      simply ran in ACPI mode on all systems with an
      ACPI BIOS -- regardless of BIOS DMI year.
      
      Recently there have been some ACPI-enabled systems
      with no DMI, mandating that CONFIG_ACPI_BLACKLIST_YEAR=0.
      
      So it seems vanishingly unlikely that this option
      is helping anybody run a 2013 kernel on a 1998 system,
      and now more systems mandate this option be disabled,
      so we simplify by deleting it entirely.
      Signed-off-by: NLen Brown <len.brown@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      4c47cb19
  10. 11 11月, 2013 1 次提交
  11. 01 11月, 2013 1 次提交
  12. 24 10月, 2013 1 次提交
  13. 16 10月, 2013 1 次提交
  14. 12 10月, 2013 1 次提交
  15. 11 10月, 2013 1 次提交
  16. 01 10月, 2013 1 次提交
  17. 23 8月, 2013 1 次提交
  18. 15 7月, 2013 1 次提交
  19. 08 4月, 2013 1 次提交
  20. 03 4月, 2013 1 次提交
    • T
      ACPI / BGRT: Don't let users configure BGRT on non X86 systems · e66cd537
      Tony Luck 提交于
      Fengguang Wu's 0-Day kernel build testing backend found the
      following build error for an allmodconfig build on ia64:
      
         drivers/built-in.o: In function `show_yoffset':
      >> bgrt.c:(.text+0xe5a71): undefined reference to `bgrt_tab'
      >> bgrt.c:(.text+0xe5a91): undefined reference to `bgrt_tab'
         drivers/built-in.o: In function `show_xoffset':
      >> bgrt.c:(.text+0xe5b51): undefined reference to `bgrt_tab'
      >> bgrt.c:(.text+0xe5b71): undefined reference to `bgrt_tab'
         drivers/built-in.o: In function `show_type':
      >> bgrt.c:(.text+0xe5c31): undefined reference to `bgrt_tab'
         drivers/built-in.o:bgrt.c:(.text+0xe5c51): more undefined references to `bgrt_tab' follow
         drivers/built-in.o: In function `bgrt_init':
         bgrt.c:(.init.text+0x8931): undefined reference to `bgrt_image'
         bgrt.c:(.init.text+0x8932): undefined reference to `bgrt_image_size'
         bgrt.c:(.init.text+0x8950): undefined reference to `bgrt_image'
         bgrt.c:(.init.text+0x8960): undefined reference to `bgrt_image_size'
      
      The problem is that all these undefined names are provided by
      arch/x86/platform/efi/efi-bgrt.c - which is obviously not available
      to the ia64 build.
      
      It doesn't seem useful to provide the BGRT support for Itanium
      (many systems are headless and have no graphics at all). So
      just don't let users configure this driver on non-X86 machines.
      Reported-by: NFengguang Wu <fengguang.wu@intel.com>
      Acked-by: NH. Peter Anvin <hpa@zytor.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      e66cd537
  21. 25 3月, 2013 1 次提交
  22. 04 3月, 2013 1 次提交
  23. 26 2月, 2013 1 次提交
  24. 16 2月, 2013 1 次提交
  25. 13 2月, 2013 1 次提交
  26. 22 1月, 2013 1 次提交
  27. 23 11月, 2012 1 次提交
  28. 01 10月, 2012 1 次提交
  29. 30 9月, 2012 1 次提交
  30. 04 6月, 2012 1 次提交
  31. 30 3月, 2012 1 次提交
  32. 04 1月, 2012 1 次提交
  33. 29 5月, 2011 1 次提交
  34. 26 5月, 2011 1 次提交
  35. 15 3月, 2011 1 次提交
  36. 21 1月, 2011 1 次提交
    • D
      kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT · 6a108a14
      David Rientjes 提交于
      The meaning of CONFIG_EMBEDDED has long since been obsoleted; the option
      is used to configure any non-standard kernel with a much larger scope than
      only small devices.
      
      This patch renames the option to CONFIG_EXPERT in init/Kconfig and fixes
      references to the option throughout the kernel.  A new CONFIG_EMBEDDED
      option is added that automatically selects CONFIG_EXPERT when enabled and
      can be used in the future to isolate options that should only be
      considered for embedded systems (RISC architectures, SLOB, etc).
      
      Calling the option "EXPERT" more accurately represents its intention: only
      expert users who understand the impact of the configuration changes they
      are making should enable it.
      Reviewed-by: NIngo Molnar <mingo@elte.hu>
      Acked-by: NDavid Woodhouse <david.woodhouse@intel.com>
      Signed-off-by: NDavid Rientjes <rientjes@google.com>
      Cc: Greg KH <gregkh@suse.de>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Jens Axboe <axboe@kernel.dk>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Robin Holt <holt@sgi.com>
      Cc: <linux-arch@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      6a108a14
  37. 12 1月, 2011 2 次提交
    • Z
      ACPI: delete CONFIG_ACPI_PROCFS_POWER and power procfs I/F in 2.6.39 · 6d855fcd
      Zhang Rui 提交于
      sysfs I/F for ACPI power devices, including AC and Battery,
      has been working in upstream kenrel since 2.6.24, Sep 2007.
      In 2.6.37, we made the sysfs I/F always built in and this option
      disabled by default.
      Now, we plan to remove this option and the ACPI power procfs
      interface in 2.6.39.
      
      First, update the feature-removal-schedule to announce this change.
      Second, add runtime warnings in ACPI AC/Battery/SBS driver, so that
      users will notice this change even if "make oldconfig" is used.
      Signed-off-by: NZhang Rui <rui.zhang@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      6d855fcd
    • Z
      ACPI: update CONFIG_ACPI_PROCFS description · 4464ed3b
      Zhang Rui 提交于
      Update CONFIG_ACPI_PROCFS description because the processor,
      video and thermal zone procfs I/F have been removed.
      
      Some ACPI drivers, e.g. button, have their procfs I/F always built in,
      because we don't have sysfs I/F replacement at the moment.
      But once we finish developing the sysfs I/F for these driver,
      we need CONFIG_ACPI_PROCFS to enabled/disable the corresponding procfs I/F.
      
      So just updating the description rather than removing this option,
      although there is no procfs I/F depends on it for now.
      Signed-off-by: NZhang Rui <rui.zhang@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      4464ed3b
  38. 14 12月, 2010 1 次提交
    • Z
      IPMI/ACPI: Add the IPMI opregion driver to enable ACPI to access BMC controller · e92b297c
      Zhao Yakui 提交于
      ACPI 4.0 spec adds the ACPI IPMI opregion, which means that the ACPI AML
      code can also communicate with the BMC controller. This is to install
      the ACPI IPMI opregion and enable the ACPI to access the BMC controller
      through the IPMI message.
      
           It will create IPMI user interface for every IPMI device detected
      in ACPI namespace and install the corresponding IPMI opregion space handler.
      Then it can enable ACPI to access the BMC controller through the IPMI
      message.
      
      The following describes how to process the IPMI request in IPMI space handler:
          1. format the IPMI message based on the request in AML code.
          IPMI system address. Now the address type is SYSTEM_INTERFACE_ADDR_TYPE
          IPMI net function & command
          IPMI message payload
          2. send the IPMI message by using the function of ipmi_request_settime
          3. wait for the completion of IPMI message. It can be done in different
      routes: One is in handled in IPMI user recv callback function. Another is
      handled in timeout function.
          4. format the IPMI response and return it to ACPI AML code.
      
      At the same time it also addes the module dependency. The ACPI IPMI opregion
      will depend on the IPMI subsystem.
      Signed-off-by: NZhao Yakui <yakui.zhao@intel.com>
      cc: Bjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: NCorey Minyard <cminyard@mvista.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      e92b297c