06 Jan, 2009

1 commit


04 Jan, 2009

1 commit


19 Dec, 2008

2 commits

  • The ACPI interpreter usually runs with irqs enabled.
    However, during suspend/resume it runs with
    irqs disabled to evaluate _GTS/_BFS, as well as
    by irqrouter_resume() which evaluates _CRS, _PRS, _SRS.

    http://bugzilla.kernel.org/show_bug.cgi?id=12252

    Signed-off-by: Wu Fengguang
    Signed-off-by: Len Brown

    Wu Fengguang
     
  • acpi_early_init() was changed to over-write the cmdline param,
    making it really inconvenient to set debug flags at boot-time.

    Also,
    This sets the default level to "info", which is what all the ACPI
    drivers use. So to enable messages from drivers, you only have to
    supply the "layer" (a.k.a. "component"). For non-"info" ACPI core
    and ACPI interpreter messages, you have to supply both level and
    layer masks, as before.

    Signed-off-by: Bjorn Helgaas
    Signed-off-by: Len Brown

    Bjorn Helgaas
     

27 Nov, 2008

2 commits

  • A generic work-around from ACPICA is in the queue,
    but since Linux has a work-around in its battery
    driver, we can disable this warning now.

    Allow _BIF method to return an Package with Buffer elements

    http://bugzilla.kernel.org/show_bug.cgi?id=11822

    Signed-off-by: Lin Ming
    Signed-off-by: Len Brown

    Lin Ming
     
  • This can happen if the _WAK method returns nothing (as per ACPI
    1.0) but does return an integer if the implicit return mechanism
    is enabled. This is the only method that has this problem,
    since it is also defined to return a package of two integers
    (ACPI 1.0b+). In all other cases, if a method returns an object
    when one was not expected, no warning is issued.

    Signed-off-by: Bob Moore
    Signed-off-by: Lin Ming
    Signed-off-by: Len Brown

    Bob Moore
     

12 Nov, 2008

5 commits


08 Nov, 2008

4 commits

  • This is a reimplemention of commit
    0119509c4fbc9adcef1472817fda295334612976
    from Matthew Garrett

    This patch got removed because of a regression: ThinkPads with a
    Intel graphics card and an Integrated Graphics Device BIOS implementation
    stopped working.
    In fact, they only worked because the ACPI device of the discrete, the
    wrong one, got used (via int10). So ACPI functions were poking on the wrong
    hardware used which is a sever bug.
    The next patch provides support for above ThinkPads to be able to
    switch brightness via the legacy thinkpad_acpi driver and automatically
    detect when to use it.

    Original commit message from Matthew Garrett:
    Vendors often ship machines with a choice of integrated or discrete
    graphics, and use the same DSDT for both. As a result, the ACPI video
    module will locate devices that may not exist on this specific platform.
    Attempt to determine whether the device exists or not, and abort the
    device creation if it doesn't.

    http://bugzilla.kernel.org/show_bug.cgi?id=9614

    Signed-off-by: Thomas Renninger
    Acked-by: Zhang Rui
    Signed-off-by: Andi Kleen
    Signed-off-by: Len Brown

    Thomas Renninger
     
  • /sys/module/acpi/parameters/debug_layers used to contain only the
    debug layers defined by the ACPI CA. This patch adds the additional
    layer definitions for ACPI drivers.

    Signed-off-by: Bjorn Helgaas
    Signed-off-by: Len Brown

    Bjorn Helgaas
     
  • Some of the component definitions that were previous scattered around
    the drivers conflict with each other. That doesn't hurt anything
    except that setting one bit in the debug_layer mask would turn on
    debugging in two different modules. This patch fixes the conflicts.

    Signed-off-by: Bjorn Helgaas
    Signed-off-by: Len Brown

    Bjorn Helgaas
     
  • Move all the component definitions for drivers to a single shared place,
    include/acpi/acpi_drivers.h.

    Signed-off-by: Bjorn Helgaas
    Signed-off-by: Len Brown

    Bjorn Helgaas
     

07 Nov, 2008

3 commits

  • Declaring processors in ACPI namespace can be done using either a
    "Processor" definition or a "Device" definition (see section 8.4 -
    Declaring Processors; "Advanced Configuration and Power Interface
    Specification", Revision 3.0b). Currently the two processor
    declaration types are conflated.

    This patch disambiguates the processor declaration's definition type
    enabling subsequent code to behave uniquely based explicitly on the
    declaration's type.

    Signed-off-by: Myron Stowe
    Signed-off-by: Len Brown

    Myron Stowe
     
  • Remove CONFIG_ACPI_EC. It was always set the same as CONFIG_ACPI,
    and it had no menu label, so there was no way to set it to anything
    other than "y".

    Per section 6.5.4 of the ACPI 3.0b specification,

    OSPM must make Embedded Controller operation regions, accessed
    via the Embedded Controllers described in ECDT, available before
    executing any control method.

    The ECDT table is optional, but if it is present, the above text
    means that the EC it describes is a required part of the ACPI
    subsystem, so CONFIG_ACPI_EC=n wouldn't make sense.

    Signed-off-by: Bjorn Helgaas
    Acked-by: Alexey Starikovskiy
    Signed-off-by: Len Brown

    Bjorn Helgaas
     
  • Remove CONFIG_ACPI_POWER. It was always set the same as CONFIG_ACPI,
    and it had no menu label, so there was no way to set it to anything
    other than "y".

    The interfaces under CONFIG_ACPI_POWER (acpi_device_sleep_wake(),
    acpi_power_transition(), etc) are called unconditionally from the
    ACPI core, so we already depend on it always being present.

    Signed-off-by: Bjorn Helgaas
    Signed-off-by: Len Brown

    Bjorn Helgaas
     

28 Oct, 2008

1 commit

  • Introduce a new flag showing whether the event has an event handler/method.

    For all the GPEs and Fixed Events,
    1. ACPI_EVENT_FLAG_HANDLE is cleared, it's an "invalid" ACPI event.
    2. Both ACPI_EVENT_FLAG_HANDLE and ACPI_EVENT_FLAG_DISABLE are set,
    it's "disabled".
    3. Both ACPI_EVENT_FLAG_HANDLE and ACPI_EVENT_FLAG_ENABLE are set,
    it's "enabled".
    4. Both ACPI_EVENT_FLAG_HANDLE and ACPI_EVENT_FLAG_WAKE_ENABLE are set,
    it's "wake_enabled".

    Among other things, this prevents incorrect reporting of ACPI events
    as being "invalid" when it's really just (temporarily) "disabled".

    Signed-off-by: Zhang Rui
    Signed-off-by: David Brownell
    Signed-off-by: Len Brown

    Zhang Rui
     

23 Oct, 2008

21 commits