V4.0.x fails to create /dev/rtc0 on Winbook TW100 when CONFIG_PINCTRL_BAYTRAIL is set, bisected to commit 7486341

V4.0.x fails to create /dev/rtc0 on Winbook TW100 when CONFIG_PINCTRL_BAYTRAIL is set, bisected to commit 7486341

[Larry Finger]

[-- 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 --]

Re: 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]

On 7/11/2015 10:59 AM, Larry Finger wrote:
> 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:

in "hardware reduced mode" (e.g. tablets) on Baytrail the RTC is not actually enabled/initialized by the firmware; talking to it may appear to work but it's really not
a good idea (and breaks things likes suspend/resume etc).

Re: 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]

On 7/11/2015 11:21 AM, Arjan van de Ven wrote:
> On 7/11/2015 10:59 AM, Larry Finger wrote:
>> 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:
>
> in "hardware reduced mode" (e.g. tablets) on Baytrail the RTC is not actually enabled/initialized by the firmware; talking to it may appear to work but it's really not
> a good idea (and breaks things likes suspend/resume etc).

(or in other words, many of the legacy PC things are not supposed to be there)

what did you want to use rtc0 for?

Re: 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]

On 7/11/2015 11:26 AM, Porteus Kiosk wrote:
> Hello Arjan,
>
> We need it for setting up the time in the hardware clock through the 'hwclock' command.
>
> Thank you.


hmm thinking about it after coffee... there is an RTC that can be exposed to userspace.
hrmpf. Wonder why its not there for you