public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: LKML <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Li Aubrey <aubrey.li@linux.intel.com>,
	Ingo Molnar <mingo@kernel.org>
Cc: Porteus Kiosk <porteus.kiosk@gmail.com>,
	Bastien Nocera <hadess@hadess.net>,
	Avi Weiss <aviw@benchmarkmerchantsolutions.com>,
	Benny Silberstein <bennys@benchmarkmerchantsolutions.com>
Subject: V4.0.x fails to create /dev/rtc0 on Winbook TW100 when CONFIG_PINCTRL_BAYTRAIL is set, bisected to commit 7486341
Date: Sat, 11 Jul 2015 12:59:38 -0500	[thread overview]
Message-ID: <55A1598A.5040903@lwfinger.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]

On a Winbook TW100 BayTrail tablet, kernel 4.0 and later do not create /dev/rtc0 
when CONFIG_PINCTRL_BAYTRAIL is set in the configuration. Removing this option 
from the config creates a real-time clock; however, it is no longer possible to 
get the tablet to sleep using the power button. Only complete shutdown works.

This problem was bisected to the following commit:

commit 7486341a98f26857f383aec88ffa10950087c3a1
Author: Li, Aubrey <aubrey.li@linux.intel.com>
Date:   Wed Mar 11 16:09:00 2015 +0800

     x86/platform, acpi: Bypass legacy PIC and PIT in ACPI hardware reduced mode

     On a platform in ACPI Hardware-reduced mode, the legacy PIC and
     PIT may not be initialized even though they may be present in
     silicon. Touching these legacy components causes unexpected
     results on the system.

     On the Bay Trail-T(ASUS-T100) platform, touching these legacy
     components blocks platform hardware low idle power state(S0ix)
     during system suspend. So we should bypass them in ACPI hardware
     reduced mode.

     Suggested-by: Arjan van de Ven <arjan@linux.intel.com>
     Signed-off-by: Li Aubrey <aubrey.li@linux.intel.com>
     Cc: <alan@linux.intel.com>
     Cc: Alan Cox <alan@linux.intel.com>
     Cc: H. Peter Anvin <hpa@linux.intel.com>
     Cc: Len Brown <len.brown@intel.com>
     Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
     Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
     Link: http://lkml.kernel.org/r/54FFF81C.20703@linux.intel.com
     Signed-off-by: Ingo Molnar <mingo@kernel.org>

The commit message says that this change was needed for the ASUS-T100 tablet. It 
appears that not all BayTrail systems are the same.

The complete dmesg output is at http://pastebin.com/x9gFKci2 and the 
configuration file is attached.

Thanks,

Larry



[-- Attachment #2: .config --]
[-- Type: application/x-config, Size: 109642 bytes --]

             reply	other threads:[~2015-07-11 17:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11 17:59 Larry Finger [this message]
2015-07-11 18:21 ` V4.0.x fails to create /dev/rtc0 on Winbook TW100 when CONFIG_PINCTRL_BAYTRAIL is set, bisected to commit 7486341 Arjan van de Ven
2015-07-11 18:22   ` Arjan van de Ven
     [not found]     ` <CANC45uWh5-jYLqoFgvfynC0n7t31fae1gp2DUn-bwky24trAPg@mail.gmail.com>
2015-07-11 18:35       ` Arjan van de Ven

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=55A1598A.5040903@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=arjan@linux.intel.com \
    --cc=aubrey.li@linux.intel.com \
    --cc=aviw@benchmarkmerchantsolutions.com \
    --cc=bennys@benchmarkmerchantsolutions.com \
    --cc=hadess@hadess.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=porteus.kiosk@gmail.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