From: Matej Laitl <strohel@gmail.com>
To: Alexey Starikovskiy <aystarik@gmail.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ACPI: use select POWER_SUPPLY for AC, BATTERY and SBS (was: [2.624-rc1 regression] lost battery information)
Date: Fri, 26 Oct 2007 23:05:14 +0200 [thread overview]
Message-ID: <200710262305.15495.strohel@gmail.com> (raw)
In-Reply-To: <47221C67.9050502@gmail.com>
Alexey Starikovskiy wrote:
> ACPI: use select POWER_SUPPLY for AC, BATTERY and SBS
>
> From: Alexey Starikovskiy <astarikovskiy@suse.de>
>
> POWER_SUPPLY is needed for AC, battery, and SBS sysfs support.
> Use 'select' instead of 'depends on', as it is will not be selected
> by anything else, leading to confusion.
>
> Signed-off-by: Alexey Starikovskiy <astarikovskiy@suse.de>
> ---
>
> drivers/acpi/Kconfig | 8 +++++---
> 1 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
> index 5d0e26a..ecd87d7 100644
> --- a/drivers/acpi/Kconfig
> +++ b/drivers/acpi/Kconfig
> @@ -88,7 +88,8 @@ config ACPI_PROC_EVENT
>
> config ACPI_AC
> tristate "AC Adapter"
> - depends on X86 && POWER_SUPPLY
> + depends on X86
> + select POWER_SUPPLY
> default y
> help
> This driver adds support for the AC Adapter object, which
> indicates @@ -97,7 +98,8 @@ config ACPI_AC
>
> config ACPI_BATTERY
> tristate "Battery"
> - depends on X86 && POWER_SUPPLY
> + depends on X86
> + select POWER_SUPPLY
> default y
> help
> This driver adds support for battery information through
> @@ -352,7 +354,7 @@ config ACPI_HOTPLUG_MEMORY
> config ACPI_SBS
> tristate "Smart Battery System"
> depends on X86
> - depends on POWER_SUPPLY
> + select POWER_SUPPLY
> help
> This driver adds support for the Smart Battery System, another
> type of access to battery information, found on some laptops.
I'd love if this got merged, as I also lost my battery information by
not-enabling POWER_SUPPLY (which looks like something unrelated to ACPI). (I
know "select" is evil, but this use-case is appropriate, IMO)
Matej
prev parent reply other threads:[~2007-10-26 21:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 16:24 [2.624-rc1 regression] lost battery information Andrey Borzenkov
2007-10-26 16:44 ` Frans Pop
2007-10-26 16:57 ` Alexey Starikovskiy
2007-10-26 17:20 ` Andrey Borzenkov
2007-10-26 18:00 ` Frans Pop
2007-10-26 18:12 ` Alexey Starikovskiy
2007-10-26 18:15 ` Andrey Borzenkov
2007-10-26 18:32 ` Alexey Starikovskiy
2007-10-26 20:57 ` Frans Pop
2007-10-26 21:07 ` Alexey Starikovskiy
2007-10-27 7:22 ` Andrey Borzenkov
2007-10-27 13:45 ` Alexey Starikovskiy
2007-10-27 14:55 ` Andrey Borzenkov
2007-10-27 15:20 ` Alexey Starikovskiy
2007-10-27 16:16 ` Frans Pop
2007-10-27 16:49 ` Andrey Borzenkov
2007-10-27 16:59 ` Alexey Starikovskiy
2007-10-26 21:05 ` Matej Laitl [this message]
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=200710262305.15495.strohel@gmail.com \
--to=strohel@gmail.com \
--cc=arvidjaar@mail.ru \
--cc=aystarik@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox