2015-07-11 17:59:42

by Larry Finger

[permalink] [raw]
Subject: V4.0.x fails to create /dev/rtc0 on Winbook TW100 when CONFIG_PINCTRL_BAYTRAIL is set, bisected to commit 7486341

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 <[email protected]>
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 <[email protected]>
Signed-off-by: Li Aubrey <[email protected]>
Cc: <[email protected]>
Cc: Alan Cox <[email protected]>
Cc: H. Peter Anvin <[email protected]>
Cc: Len Brown <[email protected]>
Cc: Rafael J. Wysocki <[email protected]>
Cc: Rafael J. Wysocki <[email protected]>
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>

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



Attachments:
.config (107.07 kB)

2015-07-11 18:21:10

by Arjan van de Ven

[permalink] [raw]
Subject: Re: V4.0.x fails to create /dev/rtc0 on Winbook TW100 when CONFIG_PINCTRL_BAYTRAIL is set, bisected to commit 7486341

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).


2015-07-11 18:22:36

by Arjan van de Ven

[permalink] [raw]
Subject: Re: V4.0.x fails to create /dev/rtc0 on Winbook TW100 when CONFIG_PINCTRL_BAYTRAIL is set, bisected to commit 7486341

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?

2015-07-11 18:35:40

by Arjan van de Ven

[permalink] [raw]
Subject: Re: V4.0.x fails to create /dev/rtc0 on Winbook TW100 when CONFIG_PINCTRL_BAYTRAIL is set, bisected to commit 7486341

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