diff options
author | Kevin Hilman <khilman@ti.com> | 2012-10-10 15:54:06 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-10-11 08:50:16 +0900 |
commit | 8dc0839510ed4a7c594386ef58446b014fb4c27a (patch) | |
tree | dbea8fdf8d42f59c920e29224644c6ad9c83ac6b /include/linux/memcontrol.h | |
parent | fdb8d561e6fb8538e320554b991ed183b19ddc83 (diff) | |
download | talos-obmc-linux-8dc0839510ed4a7c594386ef58446b014fb4c27a.tar.gz talos-obmc-linux-8dc0839510ed4a7c594386ef58446b014fb4c27a.zip |
rtc: kconfig: fix RTC_INTF defaults connected to RTC_CLASS
Commit 6b8029fab641 ("rtc: kconfig: remove unnecessary dependencies")
removed various 'depends on RTC_CLASS' dependencies but also removed a
few 'default RTC_CLASS' statements, which actually changed default
behavior.
This resulted in the various RTC interfaces (sysfs, proc, dev) all being
disabled by default, even when RTC_CLASS is enabled:
# CONFIG_RTC_INTF_SYSFS is not set
# CONFIG_RTC_INTF_PROC is not set
# CONFIG_RTC_INTF_DEV is not set
which is different from previous behavior (all of these where enabled.)
To fix, add back the 'default RTC_CLASS' statments to each of the
RTC_INTF_* options.
I noticed this because some RTC tests started failing on my TI OMAP
platforms because /dev/rtc0 was not present anymore, even though the
driver was present and RTC_CLASS was enabled.
Signed-off-by: Kevin Hilman <khilman@ti.com>
Acked-by: Venu Byravarasu <vbyravarasu@nvidia.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/memcontrol.h')
0 files changed, 0 insertions, 0 deletions