* [PATCH] rtc: hctosys: do not treat lack of RTC device as error
@ 2015-02-21 14:51 Floris Bos
0 siblings, 0 replies; only message in thread
From: Floris Bos @ 2015-02-21 14:51 UTC (permalink / raw)
To: a.zummo; +Cc: rtc-linux, linux-kernel, Floris Bos
When using device trees on the ARM platform, it is not certain
at compile time whether or not the system will have a RTC.
If one enables CONFIG_HCTOSYS just in case the system booted has
a RTC, and it turns out not to be, this will result in a big fat
"unable to open rtc device" error being printed to console, even
when "quiet" is set in the kernel cmdline.
Fix this by outputting the message with loglevel info instead.
Signed-off-by: Floris Bos <bos@je-eigen-domein.nl>
---
drivers/rtc/hctosys.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/hctosys.c b/drivers/rtc/hctosys.c
index 6c719f2..fb4251d 100644
--- a/drivers/rtc/hctosys.c
+++ b/drivers/rtc/hctosys.c
@@ -32,7 +32,7 @@ static int __init rtc_hctosys(void)
struct rtc_device *rtc = rtc_class_open(CONFIG_RTC_HCTOSYS_DEVICE);
if (rtc == NULL) {
- pr_err("%s: unable to open rtc device (%s)\n",
+ pr_info("%s: unable to open rtc device (%s)\n",
__FILE__, CONFIG_RTC_HCTOSYS_DEVICE);
goto err_open;
}
--
1.9.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2015-02-21 15:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-21 14:51 [PATCH] rtc: hctosys: do not treat lack of RTC device as error Floris Bos
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).