https://bugzilla.kernel.org/show_bug.cgi?id=42696





--- Comment #6 from Peter <lekenst...@gmail.com>  2012-11-11 00:31:56 ---
So let's check this again (the below is against 3.7).

- acpi_scan_init
 - acpi_bus_scan
  - acpi_bus_check_add
   - acpi_add_single_object
    - acpi_device_set_id
     - if (acpi_is_video_device(device))
        acpi_add_id(device, ACPI_VIDEO_HID) // add "LNXVIDEO" to PNP ids

The following video devices are detected (incomplete list):
- \_SB.PCI0.PEG0.PEGP due to _ROM
- \_SB.PCI0.PEG0.VGA due to _DOS

Now, the part that is responsible for setting archdata.acpi_handle
(drivers/acpi/glue.c). Let's assume the nvidia PCI device at 01:00.0.

- ...
 - pci_bus_add_device
  - device_add
   - platform_notify points to acpi_platform_notify on x86 and ia64
     - type = acpi_get_bus_type() (returns acpi_pnp_bus)
     - type->find_device() calls acpi_pnp_find_device
      - loop through all ACPI bus things?
       - acpi_pnp_match: find the first (?) unbound device with its PNP id list
containing "LNXVIDEO"
     - if a handle was found, call acpi_bind_one which basically sets
dev->archdata.acpi_handle
(please correct me if I'm wrong, having a "struct acpi_bus_type" and a
"acpi_bus_type" of type "struct bus_type" (in drivers/acpi/scan.c) is not
helpful) 

Looking at a log from https://lists.launchpad.net/bumblebee/msg00069.html, the
"video" module seems to be able to find the correct handle:
[    8.935976] input: Video Bus as
/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:2f/LNXVIDEO:00/input/input6
[    8.936011] ACPI: Video Device [PEGP] (multi-head: no  rom: yes  post: no)
[    8.938801] acpi device:3d: registered as cooling_device11
[    8.939038] input: Video Bus as
/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input7
[    8.939091] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    8.939127] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor
0

Request for owners of these laptops (notable IdeaPad Y570), please attach the
output of the below, without applying the hack (one affected machine is
enough):

(cd /sys/devices/LNXSYSTM:00/device:00;grep --include=path -r .)
ls -l /sys/bus/acpi/drivers/video
dmesg


If this does not give useful information, then the next step would be getting a
kernel log with ACPI debugging enabled.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to