1. 12 1月, 2011 1 次提交
    • L
      ACPICA: Rename some function and variable names · 3a37898d
      Lin Ming 提交于
      Some function and variable names are renamed to be consistent with
      ACPICA code base.
      
      acpi_raw_enable_gpe -> acpi_ev_add_gpe_reference
      acpi_raw_disable_gpe -> acpi_ev_remove_gpe_reference
      acpi_gpe_can_wake -> acpi_setup_gpe_for_wake
      acpi_gpe_wakeup -> acpi_set_gpe_wake_mask
      acpi_update_gpes -> acpi_update_all_gpes
      acpi_all_gpes_initialized -> acpi_gbl_all_gpes_initialized
      acpi_handler_info -> acpi_gpe_handler_info
      ...
      Signed-off-by: NLin Ming <ming.m.lin@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      3a37898d
  2. 07 7月, 2010 2 次提交
  3. 12 6月, 2010 3 次提交
    • R
      ACPI / ACPICA: Avoid writing full enable masks to GPE registers · c9a8bbb7
      Rafael J. Wysocki 提交于
      ACPICA uses acpi_hw_write_gpe_enable_reg() to re-enable a GPE after
      an event signaled by it has been handled.  However, this function
      writes the entire GPE enable mask to the GPE's enable register which
      may not be correct.  Namely, if one of the other GPEs in the same
      register was previously enabled by acpi_enable_gpe() and subsequently
      disabled using acpi_set_gpe(), acpi_hw_write_gpe_enable_reg() will
      re-enable it along with the target GPE.
      
      To fix this issue rework acpi_hw_write_gpe_enable_reg() so that it
      calls acpi_hw_low_set_gpe() with a special action value,
      ACPI_GPE_COND_ENABLE, that will make it only enable the GPE if the
      corresponding bit in its register's enable_for_run mask is set.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      c9a8bbb7
    • R
      ACPI / ACPICA: Fix low-level GPE manipulation code · fd247447
      Rafael J. Wysocki 提交于
      ACPICA uses acpi_ev_enable_gpe() for enabling GPEs at the low level,
      which is incorrect, because this function only enables the GPE if the
      corresponding bit in its enable register's enable_for_run mask is set.
      This causes acpi_set_gpe() to work incorrectly if used for enabling
      GPEs that were not previously enabled with acpi_enable_gpe().  As a
      result, among other things, wakeup-only GPEs are never enabled by
      acpi_enable_wakeup_device(), so the devices that use them are unable
      to wake up the system.
      
      To fix this issue remove acpi_ev_enable_gpe() and its counterpart
      acpi_ev_disable_gpe() and replace acpi_hw_low_disable_gpe() with
      acpi_hw_low_set_gpe() that will be used instead to manipulate GPE
      enable bits at the low level.  Make the users of acpi_ev_enable_gpe()
      and acpi_ev_disable_gpe() call acpi_hw_low_set_gpe() instead and
      make sure that GPE enable masks are only updated by acpi_enable_gpe()
      and acpi_disable_gpe() when GPE reference counters change from 0
      to 1 and from 1 to 0, respectively.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      fd247447
    • R
      ACPI / ACPICA: Use helper function for computing GPE masks · e4e9a735
      Rafael J. Wysocki 提交于
      In quite a few places ACPICA needs to compute a GPE enable mask with
      only one bit, corresponding to a given GPE, set.  Currently, that
      computation is always open coded which leads to unnecessary code
      duplication.  Fix this by introducing a helper function for computing
      one-bit GPE enable masks and using it where appropriate.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      e4e9a735
  4. 23 1月, 2010 2 次提交
  5. 27 8月, 2009 1 次提交
  6. 28 3月, 2009 1 次提交
  7. 09 1月, 2009 2 次提交
  8. 31 12月, 2008 3 次提交
  9. 17 7月, 2008 2 次提交
  10. 24 4月, 2008 1 次提交
  11. 03 2月, 2007 2 次提交
  12. 14 6月, 2006 1 次提交
    • B
      ACPI: ACPICA 20060421 · b229cf92
      Bob Moore 提交于
      Removed a device initialization optimization introduced in
      20051216 where the _STA method was not run unless an _INI
      was also present for the same device. This optimization
      could cause problems because it could allow _INI methods
      to be run within a not-present device subtree (If a
      not-present device had no _INI, _STA would not be run,
      the not-present status would not be discovered, and the
      children of the device would be incorrectly traversed.)
      
      Implemented a new _STA optimization where namespace
      subtrees that do not contain _INI are identified and
      ignored during device initialization. Selectively running
      _STA can significantly improve boot time on large machines
      (with assistance from Len Brown.)
      
      Implemented support for the device initialization case
      where the returned _STA flags indicate a device not-present
      but functioning. In this case, _INI is not run, but the
      device children are examined for presence, as per the
      ACPI specification.
      
      Implemented an additional change to the IndexField support
      in order to conform to MS behavior. The value written to
      the Index Register is not simply a byte offset, it is a
      byte offset in units of the access width of the parent
      Index Field. (Fiodor Suietov)
      
      Defined and deployed a new OSL interface,
      acpi_os_validate_address().  This interface is called during
      the creation of all AML operation regions, and allows
      the host OS to exert control over what addresses it will
      allow the AML code to access. Operation Regions whose
      addresses are disallowed will cause a runtime exception
      when they are actually accessed (will not affect or abort
      table loading.)
      
      Defined and deployed a new OSL interface,
      acpi_os_validate_interface().  This interface allows the host OS
      to match the various "optional" interface/behavior strings
      for the _OSI predefined control method as appropriate
      (with assistance from Bjorn Helgaas.)
      
      Restructured and corrected various problems in the
      exception handling code paths within DsCallControlMethod
      and DsTerminateControlMethod in dsmethod (with assistance
      from Takayoshi Kochi.)
      
      Modified the Linux source converter to ignore quoted string
      literals while converting identifiers from mixed to lower
      case. This will correct problems with the disassembler
      and other areas where such strings must not be modified.
      
      The ACPI_FUNCTION_* macros no longer require quotes around
      the function name. This allows the Linux source converter
      to convert the names, now that the converter ignores
      quoted strings.
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      b229cf92
  13. 31 3月, 2006 1 次提交
  14. 20 1月, 2006 1 次提交
    • B
      [ACPI] ACPICA 20060113 · 4a90c7e8
      Bob Moore 提交于
      Added 2006 copyright.
      
      At SuSE's suggestion, enabled all error messages
      without enabling function tracing, ie with CONFIG_ACPI_DEBUG=n
      
      Replaced all instances of the ACPI_DEBUG_PRINT macro invoked at
      the ACPI_DB_ERROR and ACPI_DB_WARN debug levels with
      the ACPI_REPORT_ERROR and ACPI_REPORT_WARNING macros,
      respectively. This preserves all error and warning messages
      in the non-debug version of the ACPICA code (this has been
      referred to as the "debug lite" option.) Over 200 cases
      were converted to create a total of over 380 error/warning
      messages across the ACPICA code. This increases the code
      and data size of the default non-debug version by about 13K.
      Added ACPI_NO_ERROR_MESSAGES flag to enable deleting all messages.
      The size of the debug version remains about the same.
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      4a90c7e8
  15. 05 8月, 2005 1 次提交
  16. 14 7月, 2005 1 次提交
    • R
      ACPICA 20050617-0624 from Bob Moore <robert.moore@intel.com> · 73459f73
      Robert Moore 提交于
      ACPICA 20050617:
      
      Moved the object cache operations into the OS interface
      layer (OSL) to allow the host OS to handle these operations
      if desired (for example, the Linux OSL will invoke the
      slab allocator).  This support is optional; the compile
      time define ACPI_USE_LOCAL_CACHE may be used to utilize
      the original cache code in the ACPI CA core.  The new OSL
      interfaces are shown below.  See utalloc.c for an example
      implementation, and acpiosxf.h for the exact interface
      definitions.  Thanks to Alexey Starikovskiy.
      	acpi_os_create_cache
      	acpi_os_delete_cache
      	acpi_os_purge_cache
      	acpi_os_acquire_object
      	acpi_os_release_object
      
      Modified the interfaces to acpi_os_acquire_lock and
      acpi_os_release_lock to return and restore a flags
      parameter.  This fits better with many OS lock models.
      Note: the current execution state (interrupt handler
      or not) is no longer passed to these interfaces.  If
      necessary, the OSL must determine this state by itself, a
      simple and fast operation.  Thanks to Alexey Starikovskiy.
      
      Fixed a problem in the ACPI table handling where a valid
      XSDT was assumed present if the revision of the RSDP
      was 2 or greater.  According to the ACPI specification,
      the XSDT is optional in all cases, and the table manager
      therefore now checks for both an RSDP >=2 and a valid
      XSDT pointer.  Otherwise, the RSDT pointer is used.
      Some ACPI 2.0 compliant BIOSs contain only the RSDT.
      
      Fixed an interpreter problem with the Mid() operator in the
      case of an input string where the resulting output string
      is of zero length.  It now correctly returns a valid,
      null terminated string object instead of a string object
      with a null pointer.
      
      Fixed a problem with the control method argument handling
      to allow a store to an Arg object that already contains an
      object of type Device.  The Device object is now correctly
      overwritten.  Previously, an error was returned.
      
      ACPICA 20050624:
      
      Modified the new OSL cache interfaces to use ACPI_CACHE_T
      as the type for the host-defined cache object.  This allows
      the OSL implementation to define and type this object in
      any manner desired, simplifying the OSL implementation.
      For example, ACPI_CACHE_T is defined as kmem_cache_t for
      Linux, and should be defined in the OS-specific header
      file for other operating systems as required.
      
      Changed the interface to AcpiOsAcquireObject to directly
      return the requested object as the function return (instead
      of ACPI_STATUS.) This change was made for performance
      reasons, since this is the purpose of the interface in the
      first place.  acpi_os_acquire_object is now similar to the
      acpi_os_allocate interface.  Thanks to Alexey Starikovskiy.
      
      Modified the initialization sequence in
      acpi_initialize_subsystem to call the OSL interface
      acpi_osl_initialize first, before any local initialization.
      This change was required because the global initialization
      now calls OSL interfaces.
      
      Restructured the code base to split some files because
      of size and/or because the code logically belonged in a
      separate file.  New files are listed below.
      
        utilities/utcache.c	/* Local cache interfaces */
        utilities/utmutex.c	/* Local mutex support */
        utilities/utstate.c	/* State object support */
        parser/psloop.c	/* Main AML parse loop */
      Signed-off-by: NLen Brown <len.brown@intel.com>
      73459f73
  17. 12 7月, 2005 1 次提交
    • R
      ACPICA 20050408 from Bob Moore · 44f6c012
      Robert Moore 提交于
      Fixed three cases in the interpreter where an "index"
      argument to an ASL function was still (internally) 32
      bits instead of the required 64 bits.  This was the Index
      argument to the Index, Mid, and Match operators.
      
      The "strupr" function is now permanently local
      (acpi_ut_strupr), since this is not a POSIX-defined
      function and not present in most kernel-level C
      libraries. References to the C library strupr function
      have been removed from the headers.
      
      Completed the deployment of static
      functions/prototypes. All prototypes with the static
      attribute have been moved from the headers to the owning
      C file.
      
      ACPICA 20050329 from Bob Moore
      
      An error is now generated if an attempt is made to create
      a Buffer Field of length zero (A CreateField with a length
      operand of zero.)
      
      The interpreter now issues a warning whenever executable
      code at the module level is detected during ACPI table
      load. This will give some idea of the prevalence of this
      type of code.
      
      Implemented support for references to named objects (other
      than control methods) within package objects.
      
      Enhanced package object output for the debug
      object. Package objects are now completely dumped, showing
      all elements.
      
      Enhanced miscellaneous object output for the debug
      object. Any object can now be written to the debug object
      (for example, a device object can be written, and the type
      of the object will be displayed.)
      
      The "static" qualifier has been added to all local
      functions across the core subsystem.
      
      The number of "long" lines (> 80 chars) within the source
      has been significantly reduced, by about 1/3.
      
      Cleaned up all header files to ensure that all CA/iASL
      functions are prototyped (even static functions) and the
      formatting is consistent.
      
      Two new header files have been added, acopcode.h and
      acnames.h.
      
      Removed several obsolete functions that were no longer
      used.
      Signed-off-by: NLen Brown <len.brown@intel.com>
      44f6c012
  18. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4