Re: no acpi events generated at all Sony Vaio SZ61

2007-11-15 Thread Zhang Rui
On Thu, 2007-11-15 at 11:38 +0100, Frank Munsche wrote: > Hello, > > I've got a Sony Vaio SZ61 running gentoo, 2.6.22-gentoo-r9 . Although there > is > acpi - information available in /proc/acpi (e.g. battery, ac_adapter, > processor) I never get apci - events reported. > If I pull the ac - ca

Re: [PATCH 0/5][RFC] Physical PCI slot objects

2007-11-15 Thread Gary Hade
On Thu, Nov 15, 2007 at 10:36:13AM -0700, Alex Chiang wrote: < snip > > Ok, so all that said, after re-implementing my ACPI-PCI slot > driver, we get all the correct answers, but with the additional > appearance of slots 1 and 2 (which aren't hotpluggable): Yea, looks much better. Nice to see

Re: 2.6.24-rc2-mm1: undefined reference to `local_apic_timer_c2_ok'

2007-11-15 Thread Mariusz Kozlowski
Hello, > > local_apic_timer_c2_ok > > hmm, looks like you're missing CONFIG_X86_LOCAL_APIC > so does this go away when you add CONFIG_SMP > or CONFIG_X86_UP_APIC? Yes it does. In both cases. Regards, Mariusz - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the

Re: 2.6.24-rc2-mm1: undefined reference to `local_apic_timer_c2_ok'

2007-11-15 Thread Mariusz Kozlowski
Hello, Fails to build here: LD .tmp_vmlinux1 drivers/built-in.o: In function `acpi_timer_check_state': /home/sp3fxc/linux/linux-2.6.24-rc2-mm1/drivers/acpi/processor_idle.c:305: undefined reference to `local_apic_timer_c2_ok' make: *** [.tmp_vmlinux1] Error 1 Regards, Ma

[PATCH]

2007-11-15 Thread Roel Kluin
I have sent this patch before to lkml, but it appears it wasn't picked up. Also I have to admit this isn't tested. This is a patch against linus' tree. ACPI_MADT_ENABLED is defined 1(include/acpi/actbl1.h 501) lapic_flags: an u32 of struct acpi_madt_local_sapic (include/acpi/actbl1.h 467) -- '

Re: 2.6.24-rc2-mm1: undefined reference to `local_apic_timer_c2_ok'

2007-11-15 Thread Len Brown
On Thursday 15 November 2007 17:25, Mariusz Kozlowski wrote: > local_apic_timer_c2_ok hmm, looks like you're missing CONFIG_X86_LOCAL_APIC so does this go away when you add CONFIG_SMP or CONFIG_X86_UP_APIC? - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a me

Re: [PATCH with title] priority fix in acpi_map_lsapic() arch/ia64/kernel/acpi.c

2007-11-15 Thread Roel Kluin
As above should have been its title. Roel Kluin wrote: > I have sent this patch before to lkml, but it appears it wasn't picked up. > Also > I have to admit this isn't tested. This is a patch against linus' tree. > > ACPI_MADT_ENABLED is defined 1(include/acpi/actbl1.h 501) > lapic_flags: an

Re: [PATCH 0/5][RFC] Physical PCI slot objects

2007-11-15 Thread Alex Chiang
Hi Greg, Matt, * Greg KH <[EMAIL PROTECTED]>: > On Wed, Nov 14, 2007 at 02:42:21PM -0700, Alex Chiang wrote: > > * Greg KH <[EMAIL PROTECTED]>: > > > On Wed, Nov 14, 2007 at 10:37:08AM -0700, Bjorn Helgaas wrote: > > > > > > > > So I agree that the firmware kit has a clever hack that works > > >

[PATCH] ACPI: EC: Workaround for optimized controllers

2007-11-15 Thread Alexey Starikovskiy
Some controllers fail to send confirmation GPE after address write. Detect this and don't expect such confirmation in future. This is a generalization of previous workaround (66c5f4e7367b0085652931b2f3366de29e7ff5ec), which did only read address. Reference: http://bugzilla.kernel.org/show_bug.cgi

[PATCH] ACPI: EC: Don't init EC early if it has no _INI

2007-11-15 Thread Alexey Starikovskiy
Option to init EC early inserted to handle #8598 ASUS problem, introduced several others. EC driver in this particular case has fake _INI method, not present on other machines, which don't need or break from this workaround, so lets use its presence as a flag for early init. Reference: http://bug

Re: [PATCH 01/15] ACPI: thinkpad-acpi: refactor hotkey_get and hotkey_set

2007-11-15 Thread Len Brown
> This patch: a nit to prove that I read this before dumping it into my test branch... the "perfect patch" never refers to itself as a patch in its check-in comments -- since by the time it is checked in, it is sort of self-evident it is a patch:-) http://www.zip.com.au/~akpm/linux/patches/stuf

Re: [PATCH 2/5] Construct one fakephp slot per pci slot

2007-11-15 Thread Alex Chiang
* Rolf Eike Beer <[EMAIL PROTECTED]>: > Am Mittwoch, 14. November 2007 schrieb Alex Chiang: > > * Matthew Wilcox <[EMAIL PROTECTED]>: > > > On Wed, Nov 14, 2007 at 12:37:29PM -0700, Alex Chiang > > > > Register one slot per slot, rather than one slot per > > > > function. Change the name of the sl

Re: [PATCH 0/5][RFC] Physical PCI slot objects

2007-11-15 Thread Alex Chiang
Hi Gary, [I'm gonna take the points in your mail a little out of order] > No, acpiphp should (and did before your changes) register all > hotplug capable slots. All 6 slots (2 PCI-X, 4 PCIe) in that > system are hotplug capable. Emptyness shouldn't matter. If > the empty slots are not register

Re: no acpi events generated at all Sony Vaio SZ61

2007-11-15 Thread Alexey Starikovskiy
Do you ACPI_PROC_EVENTS set in your config? Frank Munsche wrote: Hello, I've got a Sony Vaio SZ61 running gentoo, 2.6.22-gentoo-r9 . Although there is acpi - information available in /proc/acpi (e.g. battery, ac_adapter, processor) I never get apci - events reported. If I pull the ac - cable

Re: [PATCH 2/5] Construct one fakephp slot per pci slot

2007-11-15 Thread Rolf Eike Beer
Am Mittwoch, 14. November 2007 schrieb Alex Chiang: > * Matthew Wilcox <[EMAIL PROTECTED]>: > > On Wed, Nov 14, 2007 at 12:37:29PM -0700, Alex Chiang wrote: > > > Register one slot per slot, rather than one slot per function. > > > Change the name of the slot to fake%d instead of the pci address. >

no acpi events generated at all Sony Vaio SZ61

2007-11-15 Thread Frank Munsche
Hello, I've got a Sony Vaio SZ61 running gentoo, 2.6.22-gentoo-r9 . Although there is acpi - information available in /proc/acpi (e.g. battery, ac_adapter, processor) I never get apci - events reported. If I pull the ac - cable, it is recognized and the processors freq. gets modified by cpufre

[PATCH] ACPI: Disable all GPEs before re-enable interrupts

2007-11-15 Thread Zhao Yakui
Subject: ACPI: Disable all GPEs before re-enable interrupts. From: Zhao Yakui <[EMAIL PROTECTED]> Some wakeup gpes have no handler. If system is waked up by such GPE like a USB hotplug, sometimes it will cause a lot of errors reporting that the GPE has no handler . Of course acpi_leave_sleep_stat

[PATCH_5/7] ACPI: Throttling control uses T-states returned by _TSS when _TSS exists

2007-11-15 Thread Zhao Yakui
Subject: ACPI : Throttling control uses T-states returned by _TSS when _TSS exists >From : Zhao Yakui <[EMAIL PROTECTED]> If _TSS exists, throttling control will use the T-states returned by _TSS. Otherwise the calculated T-states from FADT.duty_width are used. When TSS is used , the access widt

[PATCH_4/7] ACPI: Change the function interface for throttling control via PTC

2007-11-15 Thread Zhao Yakui
Subject: ACPI : Change the function interface for throttling control via PTC >From : Zhao Yakui <[EMAIL PROTECTED]> Change the function interface for throttling control via PTC. The following functions are concerned: acpi_read_throttling_status() acpi_write_throttling_state() acpi_get_throttling_v

[PATCH_3/7] ACPI: Not use calculated T-states from FADT.duty_width when _TSS exists

2007-11-15 Thread Zhao Yakui
Subject: ACPI : Not use calculated T-states from FADT.duty_width when _TSS exists >From : Zhao Yakui <[EMAIL PROTECTED]> If _TSS exists, it will return supported T-states. It doesn't make sense to use calculated T-states from FADT.duty_width. Signed-off-by: Zhao Yakui <[EMAIL PROTECTED]> Signed

[PATCH_6/7] ACPI: Init PDC before getting throttling info

2007-11-15 Thread Zhao Yakui
Subject: ACPI : Init PDC before getting throttling info >From : Zhao Yakui <[EMAIL PROTECTED]> The throttling info should be obtained after PDC is initialized. Otherwise the cpus maybe use the different PTC control/status register when the system supports the TSS throttling via ACPI MSR. One uses

[PATCH_7/7] ACPI: Add MSR support for T-States

2007-11-15 Thread Zhao Yakui
Subject: ACPI : Add MSR support for T-States >From : Zhao Yakui <[EMAIL PROTECTED]> Add throttling control via MSR when T-states uses the FixHW Control/ Status registers. Signed-off-by: Zhao Yakui <[EMAIL PROTECTED]> Signed-off-by: Li Shaohua <[EMAIL PROTECTED]> --- arch/x86/kernel/acpi/process

[PATCH_2/7] ACPI: Modify the ACPI I/O Access width

2007-11-15 Thread Zhao Yakui
Subject: ACPI : Modify the ACPI I/O Access width >From : Zhao Yakui <[EMAIL PROTECTED]> When the argument width is not the multiple of eight, the acpi I/O access will fail. Modify the acpi I/O access width to the multiple of eight. Signed-off-by: Zhao Yakui <[EMAIL PROTECTED]> Signed-off-by: Li

[PATCH_1/7] ACPI: Add the _TPC throttling limit for TSS

2007-11-15 Thread Zhao Yakui
Subject: ACPI :Add the _TPC throttling limit for TSS >From : Zhao Yakui <[EMAIL PROTECTED]> When Tstate limit change notification is received, OSPM should evaluate the _TPC object and change the current TState according to the new limit. Signed-off-by: Zhao Yakui <[EMAIL PROTECTED]> Signed-off-

[PATCH_2/7] [ACPI]: Modify the ACPI I/O Access width

2007-11-15 Thread Zhao Yakui
Subject: ACPI : Modify the ACPI I/O Access width >From : Zhao Yakui <[EMAIL PROTECTED]> When the argument width is not the multiple of eight, the acpi I/O access will fail. Modify the acpi I/O access width to the multiple of eight. Signed-off-by: Zhao Yakui <[EMAIL PROTECTED]> Signed-off-by: Li

[Patch_3/7] ACPI: Not use calculated T-states from FADT.duty_width when _TSS exists

2007-11-15 Thread Zhao Yakui
Subject: ACPI : Not use calculated T-states from FADT.duty_width when _TSS exists >From : Zhao Yakui <[EMAIL PROTECTED]> If _TSS exists, it will return supported T-states. It doesn't make sense to use calculated T-states from FADT.duty_width. Signed-off-by: Zhao Yakui <[EMAIL PROTECTED]> Signed

[Patch_5/7 ] [ACPI]:Throttling control uses T-states returned by _TSS when _TSS exists

2007-11-15 Thread Zhao Yakui
Subject: ACPI : Throttling control uses T-states returned by _TSS when _TSS exists >From : Zhao Yakui <[EMAIL PROTECTED]> If _TSS exists, throttling control will use the T-states returned by _TSS. Otherwise the calculated T-states from FADT.duty_width are used. When TSS is used , the access widt

[Patch_4/7] [ACPI]:Change the function interface for throttling control via PTC

2007-11-15 Thread Zhao Yakui
Subject: ACPI : Change the function interface for throttling control via PTC >From : Zhao Yakui <[EMAIL PROTECTED]> Change the function interface for throttling control via PTC. The following functions are concerned: acpi_read_throttling_status() acpi_write_throttling_state() acpi_get_throttling_v