Noemi Alvarez | 29 Jul 10:23 2014
Picon

Hello


I want to keep up with you with hope for friendship if you are interested.
If you don't mind i will like you to write me back. I am waiting to read
from you, because i have something important and urgent to discuss with
you. I will also send some of my beautiful photos to you.

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hanjun Guo | 29 Jul 05:27 2014

[PATCH] ACPI / processor: Make it possible to get local x2apic id via _MAT

Logical processors with APIC ID values of 255 and greater are
required to have a Processor Device object and must convey the
processor's APIC information to OSPM using the Processor Local
X2APIC structure, but not until ACPI 5.1, X2APIC structure was
not supported in _MAT method.

_MAT is needed for CPU hotplug and system with more than 255
CPUs will definitely need X2APIC structure, so add its support
in map_mat_entry() to make it possible to get local x2apic id
via _MAT based on ACPI 5.1.

Signed-off-by: Hanjun Guo <hanjun.guo <at> linaro.org>
---
 drivers/acpi/processor_core.c |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/acpi/processor_core.c b/drivers/acpi/processor_core.c
index 00f48d1..e32321c 100644
--- a/drivers/acpi/processor_core.c
+++ b/drivers/acpi/processor_core.c
 <at>  <at>  -129,6 +129,8  <at>  <at>  static int map_mat_entry(acpi_handle handle, int type, u32 acpi_id)
 		map_lapic_id(header, acpi_id, &apic_id);
 	} else if (header->type == ACPI_MADT_TYPE_LOCAL_SAPIC) {
 		map_lsapic_id(header, type, acpi_id, &apic_id);
+	} else if (header->type == ACPI_MADT_TYPE_LOCAL_X2APIC) {
+		map_x2apic_id(header, type, acpi_id, &apic_id);
 	}

 exit:
--

-- 
(Continue reading)

John Marsden | 28 Jul 22:52 2014
Picon

PROBLEM: [Toshiba Portege Z835] Brightness control lost after suspend

[1.] One line summary of the problem
[Toshiba Portege Z835] Brightness control lost after suspend

[2.] Full description of the problem/report:
Using a Toshiba Portege Z835 computer I expect brightness of my LCD
screen to remain the same and be controllable after waking from
suspend. Afer suspend it doesn't remain the same and isn't
controllable.

What happens:

Brightness controls fully working after initial boot, both through
function keys and system settings applet.

After putting computer into suspend and then re-awakening the LCD
screen comes up with different brightness in actual appearance but
settings still show the brightness as set at suspend time. Controls
for brightness have become ineffective - they slide the brightness bar
along but make no difference to the actual brightness of the screen.
The brightness of the LCD on re-awakening appears to be at lowest
setting if running on battery or machine has been idle for some time.
The key problem is that it cannot be changed back to desired
brightness without a complete system re-start.

This occurs both on my Toshiba Portege Z835-ST6N03 and my wife's
Toshiba Protege Z835-ST8305

[3.] Keywords (i.e., modules, networking, kernel):

[4.] Kernel version (from /proc/version):
(Continue reading)

Hans de Goede | 28 Jul 17:37 2014
Picon

[PATCH] acpi-video: Add video.use_native_backlight=1 for HP EliteBook 2014 series

Hi,

Not sure how long we want to keep maintaining the video.use_native_backlight=1
whitelist now that it is the default in 3.16 .

But I've written this patch to add to the Fedora 3.15 kernel, so I thought
I might as well submit it upstream.

Regards,

Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

weiyj_lk | 28 Jul 15:22 2014

[PATCH -next] ACPI / battery: remove duplicated include from battery.c

From: Wei Yongjun <yongjun_wei <at> trendmicro.com.cn>

Remove duplicated include.

Signed-off-by: Wei Yongjun <yongjun_wei <at> trendmicro.com.cn>
---
 drivers/acpi/battery.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/acpi/battery.c b/drivers/acpi/battery.c
index 130f513..48bcf38 100644
--- a/drivers/acpi/battery.c
+++ b/drivers/acpi/battery.c
 <at>  <at>  -35,7 +35,6  <at>  <at> 
 #include <linux/delay.h>
 #include <linux/slab.h>
 #include <linux/suspend.h>
-#include <linux/delay.h>
 #include <asm/unaligned.h>

 #ifdef CONFIG_ACPI_PROCFS_POWER

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Chen, Gong | 28 Jul 08:50 2014
Picon

two minor update patches for RAS

[PATCH 1/2] APEI, GHES: Cleanup unnecessary function for lock-less
[PATCH 2/2] RAS, HWPOISON: Fix wrong error recovery status

These two patches are trivial fixes for APEI and HWPOISON.
Send them together to avoid fragments.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Tomasz Nowicki | 24 Jul 17:51 2014

[RFC] ACPI: Add GPIO-signaled event simulator.

GPIO signaled events is quite new thing in Linux kernel.
AFAIK, there are not many board which can take advantage of it.
However, GPIO events are very useful feature during work on ACPI
subsystems.

This commit emulates GPIO h/w behaviour and consists on read/write
operation to debugfs file. GPIO device instance is still required in DSDT
table along with _AEI resources and event methods.

Reading from file provides pin to GPIO device map e.g. :
$ cat /sys/kernel/debug/acpi/gpio_event
GPIO device name: /__SB.GPI0
Available GPIO pin map:
/__SB.GPI0 <-> pin 0x100

Based on that, user can trigger method corresponding to device pin number:
$ echo "/__SB.GPI0 0x100" > /sys/kernel/debug/acpi/gpio_event

Please, see Kconfig help and driver head section for more details
regarding tool usage.

Signed-off-by: Tomasz Nowicki <tomasz.nowicki <at> linaro.org>
---
 drivers/acpi/Kconfig        |  11 +++
 drivers/acpi/Makefile       |   1 +
 drivers/acpi/gpio_evt_emu.c | 207 ++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 219 insertions(+)
 create mode 100644 drivers/acpi/gpio_evt_emu.c

diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
(Continue reading)

Arjun Sreedharan | 22 Jul 21:13 2014
Picon

[PATCH] PNPACPI: check return value of pnpacpi_parse_allocated_resource() and pnpacpi_parse_resource_option_data()

Handle error condition since pnpacpi_parse_allocated_resource() and
pnpacpi_parse_resource_option_data() could return -EPERM.

Signed-off-by: Arjun Sreedharan <arjun024 <at> gmail.com>
---
 drivers/pnp/pnpacpi/core.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/drivers/pnp/pnpacpi/core.c b/drivers/pnp/pnpacpi/core.c
index b81448b..c3214e9 100644
--- a/drivers/pnp/pnpacpi/core.c
+++ b/drivers/pnp/pnpacpi/core.c
 <at>  <at>  -272,10 +272,14  <at>  <at>  static int __init pnpacpi_add_device(struct acpi_device *device)
 		strncpy(dev->name, acpi_device_bid(device), sizeof(dev->name));

 	if (dev->active)
-		pnpacpi_parse_allocated_resource(dev);
+		error = pnpacpi_parse_allocated_resource(dev);
+		if (error)
+			return error;

 	if (dev->capabilities & PNP_CONFIGURABLE)
-		pnpacpi_parse_resource_option_data(dev);
+		error = pnpacpi_parse_resource_option_data(dev);
+		if (error)
+			return error;

 	list_for_each_entry(id, &device->pnp.ids, list) {
 		if (!strcmp(id->id, pnpid))
--

-- 
(Continue reading)

Tomasz Nowicki | 22 Jul 11:20 2014

[PATCH v5 0/3] APEI: Make APEI architecture independent.

APEI is currently implemented so that it depends on x86 hardware.
The primary dependency is that GHES uses the x86 NMI for hardware
error notification and MCE for memory error handling. These patches
remove that dependency.

Other APEI features such as error reporting via external IRQ, error
serialization, or error injection, do not require changes to use them
on non-x86 architectures.

The following patch set eliminates the APEI Kconfig x86 dependency
by making these changes:
- treat NMI notification as GHES architecture - HAVE_ACPI_APEI_NMI
- group and wrap around #ifdef CONFIG_HAVE_ACPI_APEI_NMI code which
  is used only for NMI path
- identify architectural boxes and abstract it accordingly (tlb flush and MCE)
- rework ioremap for both IRQ and NMI context

NMI code is kept in ghes.c file since NMI and IRQ context are tightly coupled.

Note, these patches introduce no functional changes for x86. The NMI notification
feature is hard selected for x86. Architectures that want to use this
feature should also provide NMI code infrastructure.

V1->V2
- address Borislav's comment
- abstract arch-specific calls instead of wrapping into the #ifdef

V2->V3
- address Robert's comment
- disable ACPI_APEI_NMI selection so that it is hard selected by arch Kconfig
(Continue reading)

Anders Kaseorg | 22 Jul 06:32 2014
Picon

PROBLEM: Native backlight regressed from logarithmic to linear scale

[1.] One line summary of the problem:    

Native backlight regressed from logarithmic to linear scale

[2.] Full description of the problem/report:

With the new default of video.use_native_backlight=0 (commit 
v3.16-rc1~30^2~2^3), my Thinkpad T510 backlight has become very difficult 
to control near the low end of the scale.  The lowest setting now turns 
the backlight completely off, but the second-lowest setting is too bright.  
Meanwhile, the difference between the highest several settings is nearly 
imperceptible.

This happened because /sys/class/backlight/acpi_video0/brightness (which 
has now disappeared) used a different scale than 
/sys/class/intel_backlight/brightness; the relationship between 
acpi_video0 and intel_backlight was not linear.  I measured the exact 
relationship as follows:

acpi    intel
0       52
1       87
2       139
3       174
4       226
5       261
6       313
7       435
8       591
9       800
(Continue reading)

Rafael J. Wysocki | 19 Jul 22:36 2014
Picon

[PATCH 0/2] ACPI / PM: Make ACPI-based PCI wakeup work for the "freeze" sleep state

Hi,

As per the subject, this is to make ACPI-based PCI wakeup (such as WoL on some
systems among other things) work with the "freeze" sleep state.  For this
purpose ACPI wakeup GPEs need to be enabled for wakeup devices before
freeze_enter() is called and it is best to do that when configuring devices
for wakeup.

[1/2] Always enable wakeup GPEs when configuring devices for wakeup
[2/2] Rename one static function to avoid possible future confusion

Thanks!

--

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Gmane