1. 26 1月, 2007 1 次提交
    • B
      ACPI: move FADT resource reservations from motherboard driver to osl · 9a47cdb1
      Bjorn Helgaas 提交于
      Resources described by the FADT aren't really a good fit for the
      ACPI motherboard driver.
      
      The motherboard driver cares about PNP0C01 and PNP0C02 devices and
      their resources.
      
      The FADT describes some resources used by the ACPI core.  Often, they
      are also described by by the _CRS of a motherboard device, but I think
      it's better to reserve them specifically in the ACPI osl.c because
      (a) the motherboard driver is optional and ACPI uses the resources even
      if the driver is absent, and (b) I want to remove the ACPI motherboard
      driver because it's mostly redundant with the PNP system.c driver.
      Signed-off-by: NBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      9a47cdb1
  2. 06 1月, 2007 1 次提交
  3. 21 12月, 2006 2 次提交
    • R
      ACPI: fix Supermicro X7DB8+ Boot regression · 2786f6e3
      Rui Zhang 提交于
      http://bugzilla.kernel.org/show_bug.cgi?id=7695
      
      Originally we converted bind/unbind to use a new pci bridge driver.
      The driver will add/remove _PRT, so we can eventually remove
      .bind/.unbind methods.
      
      But we found that some of the _ADR-Based devices don't have _PRT,
      i.e. they are not managed by the new ACPI PCI bridge driver.
      So that .bind method is not called for some _ADR-Based devices,
      which leads to a failure.
      
      Now we make ACPI PCI Root Bridge Driver scan and binds all _ADR-Based devices
      once the driver is loaded, in the .add method of ACPI PCI Root Bridge driver.
      
      Extra code path for calling .bind/.unbind when _ADR-Based devices
      are hot added/removed is also added.
      Signed-off-by: NZhang Rui <rui.zhang@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      2786f6e3
    • Z
      ACPI: use PNPID:instance_no as bus_id of ACPI device · e49bd2dd
      Zhang Rui 提交于
      Previously we used the device name in the DSDT, but would
      crash upon encountering a duplicate. Also, exposing the
      DSDT device name to the user in a patch isn't a good idea,
      because it is arbitrary.
      
      After some discussion, we finally decided to use
      "PNPID:instance_no" as the bus_id of ACPI devices.
      
      Two attributes for each device are added at the same time,
      the full pathname in ACPI namespace and hardware_id if it has.
      
      NOTE:	acpi_bus_id_list is used to keep the information of PNPID
      	and instance number of the given PNPID. Loop the
      	acpi_bus_id_list to find the instance_no of the	same PNPID
      	when register a device. If failed, i.e. we don't have a
      	node with this PNPID, allocate one and link it to this list.
      
      NOTE:	Now I don't take the memory free work in charge.
      	If necessary, I can add a reference count in
      	struct acpi_device_bus_id, and check the reference and
      	when unregister a device, i.e. memory is freed when
      	the reference count of a given PNPID is 0.
      Signed-off-by: NLi Shaohua <shaohua.li@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      e49bd2dd
  4. 16 12月, 2006 12 次提交
  5. 14 12月, 2006 24 次提交