From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
Adam Williamson <awilliam@redhat.com>
Cc: linux-acpi@vger.kernel.org, "Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: No power management on Bay Trail tablet (Dell Venue 8 Pro)
Date: Mon, 02 Dec 2013 14:18:31 +0100 [thread overview]
Message-ID: <529C88A7.3090103@intel.com> (raw)
In-Reply-To: <20131202131822.GK2281@intel.com>
+Rui
On 12/2/2013 2:18 PM, Mika Westerberg wrote:
> +Rafael
>
> On Sat, Nov 30, 2013 at 01:56:33PM -0800, Adam Williamson wrote:
>> Hi, folks. I recently bought a Dell Venue 8 Pro -
>> a Bay Trail / Valley View-based Intel tablet - to try and get Fedora
>> running on it. Among the many things I'm currently fighting :), there
>> doesn't appear to be any power management going on at all. 'upower -d'
>> is pretty much empty, doesn't acknowledge the existence of a battery.
> It looks like there is an I2C operation region that the AML code uses to
> handle the battery specific things:
>
> Scope (_SB.I2C1)
> {
> Name (UMPC, ResourceTemplate ()
> {
> I2cSerialBus (0x0048, ControllerInitiated, 0x000186A0,
> AddressingMode7Bit, "\\_SB.I2C1",
> 0x00, ResourceConsumer, ,
> )
> })
> Name (AVBL, Zero)
> Method (_REG, 2, NotSerialized) // _REG: Region Availability
> {
> If (LEqual (Arg0, 0x09))
> {
> Store (Arg1, AVBL)
> }
> }
>
> OperationRegion (DVUM, GenericSerialBus, Zero, 0x0100)
> ...
>
> Unfortunately this is not supported in Linux yet.
next prev parent reply other threads:[~2013-12-02 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1385848593.2566.35.camel@adam.happyassassin.net>
2013-12-02 13:18 ` No power management on Bay Trail tablet (Dell Venue 8 Pro) Mika Westerberg
2013-12-02 13:18 ` Rafael J. Wysocki [this message]
2013-12-02 13:41 ` Zhang, Rui
2013-12-02 13:55 ` Mika Westerberg
2013-12-02 22:35 ` Adam Williamson
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=529C88A7.3090103@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=awilliam@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rui.zhang@intel.com \
/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