From: Alexander Mezin <mezin.alexander@gmail.com>
To: Lan Tianyu <lantianyu1986@gmail.com>
Cc: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 1/2] ACPI / AC: Notify when state changes in get_ac_property
Date: Mon, 10 Feb 2014 09:16:59 +0700 [thread overview]
Message-ID: <CADnvcf+7T8qDeRhwbwhmja9N1HeAzfF_oDSBpnUX59NTCRmkAg@mail.gmail.com> (raw)
In-Reply-To: <CAOLK0pxeQN5gtr1qckdp+Y2Mbi8yih2U1_hQFedm18K4Mzw6_A@mail.gmail.com>
2014-02-10 8:29 GMT+07:00 Lan Tianyu <lantianyu1986@gmail.com>:
> 2014-02-08 Alexander Mezin <mezin.alexander@gmail.com>:
>> 2014-02-08 13:33 GMT+07:00 Lan Tianyu <lantianyu1986@gmail.com>:
> Hi:
> What's the benefit of the second patch without this patch?
> So far, bios sends the ACPI notify event of power change to AC driver and
> the driver would change status and send uevent. That seems enough.
Without second patch AC adapter's status isn't updated on my laptop.
AC status updates only if I run "acpi -a". I usually automated this
with acpid.
On my laptop only battery notifications are working fine.
With second patch (and without first) everything works as it should.
next prev parent reply other threads:[~2014-02-10 2:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 19:28 [PATCH 1/2] ACPI / AC: Notify when state changes in get_ac_property Alexander Mezin
2014-02-07 19:28 ` [PATCH 2/2] ACPI / battery: check AC adapter's state when battery state changes Alexander Mezin
2014-02-08 6:33 ` [PATCH 1/2] ACPI / AC: Notify when state changes in get_ac_property Lan Tianyu
2014-02-08 8:33 ` Alexander Mezin
2014-02-10 1:29 ` Lan Tianyu
2014-02-10 2:16 ` Alexander Mezin [this message]
2014-02-10 2:27 ` Lan Tianyu
2014-02-10 2:34 ` Lan Tianyu
2014-02-10 2:47 ` Alexander Mezin
2014-02-10 3:15 ` Lan Tianyu
2014-02-10 18:34 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=CADnvcf+7T8qDeRhwbwhmja9N1HeAzfF_oDSBpnUX59NTCRmkAg@mail.gmail.com \
--to=mezin.alexander@gmail.com \
--cc=lantianyu1986@gmail.com \
--cc=linux-acpi@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.