public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Lan Tianyu <tianyu.lan@intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Alexander Mezin <mezin.alexander@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2] ACPI / battery: trigger rechecking of AC adapter state when battery state changes.
Date: Fri, 07 Mar 2014 11:43:10 +0800	[thread overview]
Message-ID: <5319404E.10509@intel.com> (raw)
In-Reply-To: <1820321.2G4Ojtj5V1@vostro.rjw.lan>

On 03/06/2014 09:15 PM, Rafael J. Wysocki wrote:
> On Sunday, March 02, 2014 06:02:39 PM Alexander Mezin wrote:
>> On HP Pavilion dv6-6179er there are no notifications when AC adapter
>> is plugged/unplugged.
>>
>> Output of acpi_listen, adapter is unplugged and then plugged in back:
>>
>> battery PNP0C0A:00 00000001 00000001
>> battery PNP0C0A:00 00000080 00000001
>>   PNP0C14:00 00000080 00000000
>> processor LNXCPU:00 00000082 00000000
>> battery PNP0C0A:00 00000000 00000001
>> battery PNP0C0A:00 00000080 00000001
>>   PNP0C14:00 00000080 00000000
>> processor LNXCPU:00 00000082 00000000
>> battery PNP0C0A:00 00000080 00000001
>>
>> The only way to trigger the notification is to read "online"
>> property in sysfs (/sys/class/power_supply/AC/online).
>>
>> This patch triggers the notification by calling get_property for
>> every mains power supply.
>>
>> Output of acpi_listen with this patch applied:
>>
>> battery PNP0C0A:00 00000001 00000001
>> battery PNP0C0A:00 00000080 00000001
>>   PNP0C14:00 00000080 00000000
>> ac_adapter ACPI0003:00 00000000 00000000
>> processor LNXCPU:00 00000082 00000000
>> battery PNP0C0A:00 00000000 00000001
>> battery PNP0C0A:00 00000080 00000001
>>   PNP0C14:00 00000080 00000000
>> ac_adapter ACPI0003:00 00000000 00000001
>> processor LNXCPU:00 00000082 00000000
>> battery PNP0C0A:00 00000080 00000001
>>
>> I'm using this patch for about a month, and didn't notice any
>> problems. I've tested it on top of both 3.13.5 and 3.14-rc4.
>>
>> Signed-off-by: Alexander Mezin <mezin.alexander@gmail.com>
>
> Tiany, do you have any more comments here?
>

Sorry for later response due to be busy on other things.

Hi Alexander:

 From the DSDT table, _Q08 is in change of notifying AC driver.
So you can check "/sys/firmware/acpi/interrupts/gpe08". Whether the 
count increases or not during plugging or unplugging AC.

According the description, the _Q08 wasn't triggered.

 >> The only way to trigger the notification is to read "online"
 >> property in sysfs (/sys/class/power_supply/AC/online).

The AC status is read and _PSR() is invoked during "online" file is 
accessed.

_PSR() compares EC AC status with previous stored value and notify AC 
driver if these values are not equal. This is why there is AC event 
after accessing "online" sysfs interface.

Method (_PSR, 0, NotSerialized)  // _PSR: Power Source
{
     Store (ACP, Local0)
     If (^^PCI0.LPCB.EC.ECOK)
     {
         Store (^^PCI0.LPCB.EC.ADP, Local0)
         If (LNotEqual (Local0, ACP))
         {
             FLPA ()
         }
     }
	.....
}


Method (FLPA, 0, NotSerialized)
{
     If (ACP)
     {
         Store (Zero, ACP)
     }
     Else
     {
         Store (One, ACP)
     }

     Notify (AC, Zero)
}


>>
>> ---
>>   v2: more verbose description
>>
>>   drivers/acpi/battery.c | 22 ++++++++++++++++++++++
>>   1 file changed, 22 insertions(+)
>>
>> diff --git a/drivers/acpi/battery.c b/drivers/acpi/battery.c
>> index 797a693..fb548f0 100644
>> --- a/drivers/acpi/battery.c
>> +++ b/drivers/acpi/battery.c
>> @@ -671,9 +671,22 @@ static void acpi_battery_quirks(struct acpi_battery *battery)
>>   	}
>>   }
>>
>> +static int acpi_battery_check_ac_state(struct device *dev, void *unused)
>> +{
>> +	struct power_supply *ps = dev_get_drvdata(dev);
>> +	union power_supply_propval temp;
>> +
>> +	if (ps->type != POWER_SUPPLY_TYPE_MAINS)
>> +		return 0;
>> +
>> +	ps->get_property(ps, POWER_SUPPLY_PROP_ONLINE, &temp);
>> +	return 0;
>> +}
>> +
>>   static int acpi_battery_update(struct acpi_battery *battery)
>>   {
>>   	int result, old_present = acpi_battery_present(battery);
>> +	int old_state = battery->state;
>>   	result = acpi_battery_get_status(battery);
>>   	if (result)
>>   		return result;
>> @@ -696,6 +709,15 @@ static int acpi_battery_update(struct acpi_battery *battery)
>>   	}
>>   	result = acpi_battery_get_state(battery);
>>   	acpi_battery_quirks(battery);
>> +	if (old_state != battery->state)
>> +		/*
>> +		 * Some BIOSes don't send notifications when AC adapter
>> +		 * is plugged or unplugged.
>> +		 * If battery changes its state, this could indicate that
>> +		 * AC adapter's state has changed too.
>> +		 */
>> +		class_for_each_device(power_supply_class, NULL, NULL,
>> +				      &acpi_battery_check_ac_state);

I think you can use acpi_notifier_call_chain() here and register acpi 
notifier in the AC driver. When get the Battery change event, call 
acpi_ac_get_state(ac). From my view, this is more general than traverse 
all power supply device and call AC's get_property() callback in battery 
driver.

>>   	return result;
>>   }
>>
>>
>


-- 
Best Regards
Tianyu Lan

  reply	other threads:[~2014-03-07  3:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02 11:02 [PATCH v2] ACPI / battery: trigger rechecking of AC adapter state when battery state changes Alexander Mezin
2014-03-06 13:15 ` Rafael J. Wysocki
2014-03-07  3:43   ` Lan Tianyu [this message]
2014-03-08  5:45     ` Alexander Mezin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5319404E.10509@intel.com \
    --to=tianyu.lan@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mezin.alexander@gmail.com \
    --cc=rjw@rjwysocki.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox