From: alexandre.belloni at bootlin.com (Alexandre Belloni)
Subject: about selftests/rtc test related stuff
Date: Fri, 24 May 2019 00:52:19 +0200 [thread overview]
Message-ID: <20190523225219.GZ3274@piout.net> (raw)
In-Reply-To: <CAG=yYwmrE30nROqn63oAkXN9BCqfmo4T7+QPN-H3mSGG9dLU4A@mail.gmail.com>
On 24/05/2019 02:36:42+0530, Jeffrin Thalakkottoor wrote:
> On Thu, May 23, 2019 at 11:17 PM Alexandre Belloni
> <alexandre.belloni at bootlin.com> wrote:
> > Your user probably doesn't have access to the rtc device file.
> anyway thanks related
> Following is the result with sudo....
> ------------------------x--------------------------------------x----------------------------
> $sudo ./rtctest
> [sudo] password for jeffrin:
> [==========] Running 7 tests from 2 test cases.
> [ RUN ] rtc.date_read
> rtctest.c:49:rtc.date_read:Current RTC date/time is 23/05/2019 20:49:49.
> [ OK ] rtc.date_read
> [ RUN ] rtc.uie_read
> [ OK ] rtc.uie_read
> [ RUN ] rtc.uie_select
> [ OK ] rtc.uie_select
> [ RUN ] rtc.alarm_alm_set
> rtctest.c:137:rtc.alarm_alm_set:Alarm time now set to 20:49:58.
> rtctest.c:156:rtc.alarm_alm_set:data: 1a0
> [ OK ] rtc.alarm_alm_set
> [ RUN ] rtc.alarm_wkalm_set
> rtctest.c:195:rtc.alarm_wkalm_set:Alarm time now set to 23/05/2019 20:50:01.
> [ OK ] rtc.alarm_wkalm_set
> [ RUN ] rtc.alarm_alm_set_minute
> rtctest.c:239:rtc.alarm_alm_set_minute:Alarm time now set to 20:51:00.
> Alarm clock
> $rtctest.c:258:rtc.alarm_alm_set_minute:data: 1a0
>
I just sent a fix for that timeout issue.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: alexandre.belloni@bootlin.com (Alexandre Belloni)
Subject: about selftests/rtc test related stuff
Date: Fri, 24 May 2019 00:52:19 +0200 [thread overview]
Message-ID: <20190523225219.GZ3274@piout.net> (raw)
Message-ID: <20190523225219.GaiFKrZ0wIn2IgQHmWSgvd7hRDQ1aaDEc3zesAyehyw@z> (raw)
In-Reply-To: <CAG=yYwmrE30nROqn63oAkXN9BCqfmo4T7+QPN-H3mSGG9dLU4A@mail.gmail.com>
On 24/05/2019 02:36:42+0530, Jeffrin Thalakkottoor wrote:
> On Thu, May 23, 2019 at 11:17 PM Alexandre Belloni
> <alexandre.belloni@bootlin.com> wrote:
> > Your user probably doesn't have access to the rtc device file.
> anyway thanks related
> Following is the result with sudo....
> ------------------------x--------------------------------------x----------------------------
> $sudo ./rtctest
> [sudo] password for jeffrin:
> [==========] Running 7 tests from 2 test cases.
> [ RUN ] rtc.date_read
> rtctest.c:49:rtc.date_read:Current RTC date/time is 23/05/2019 20:49:49.
> [ OK ] rtc.date_read
> [ RUN ] rtc.uie_read
> [ OK ] rtc.uie_read
> [ RUN ] rtc.uie_select
> [ OK ] rtc.uie_select
> [ RUN ] rtc.alarm_alm_set
> rtctest.c:137:rtc.alarm_alm_set:Alarm time now set to 20:49:58.
> rtctest.c:156:rtc.alarm_alm_set:data: 1a0
> [ OK ] rtc.alarm_alm_set
> [ RUN ] rtc.alarm_wkalm_set
> rtctest.c:195:rtc.alarm_wkalm_set:Alarm time now set to 23/05/2019 20:50:01.
> [ OK ] rtc.alarm_wkalm_set
> [ RUN ] rtc.alarm_alm_set_minute
> rtctest.c:239:rtc.alarm_alm_set_minute:Alarm time now set to 20:51:00.
> Alarm clock
> $rtctest.c:258:rtc.alarm_alm_set_minute:data: 1a0
>
I just sent a fix for that timeout issue.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
Cc: a.zummo@towertech.it, Shuah Khan <shuah@kernel.org>,
linux-rtc@vger.kernel.org, linux-kselftest@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: about selftests/rtc test related stuff
Date: Fri, 24 May 2019 00:52:19 +0200 [thread overview]
Message-ID: <20190523225219.GZ3274@piout.net> (raw)
In-Reply-To: <CAG=yYwmrE30nROqn63oAkXN9BCqfmo4T7+QPN-H3mSGG9dLU4A@mail.gmail.com>
On 24/05/2019 02:36:42+0530, Jeffrin Thalakkottoor wrote:
> On Thu, May 23, 2019 at 11:17 PM Alexandre Belloni
> <alexandre.belloni@bootlin.com> wrote:
> > Your user probably doesn't have access to the rtc device file.
> anyway thanks related
> Following is the result with sudo....
> ------------------------x--------------------------------------x----------------------------
> $sudo ./rtctest
> [sudo] password for jeffrin:
> [==========] Running 7 tests from 2 test cases.
> [ RUN ] rtc.date_read
> rtctest.c:49:rtc.date_read:Current RTC date/time is 23/05/2019 20:49:49.
> [ OK ] rtc.date_read
> [ RUN ] rtc.uie_read
> [ OK ] rtc.uie_read
> [ RUN ] rtc.uie_select
> [ OK ] rtc.uie_select
> [ RUN ] rtc.alarm_alm_set
> rtctest.c:137:rtc.alarm_alm_set:Alarm time now set to 20:49:58.
> rtctest.c:156:rtc.alarm_alm_set:data: 1a0
> [ OK ] rtc.alarm_alm_set
> [ RUN ] rtc.alarm_wkalm_set
> rtctest.c:195:rtc.alarm_wkalm_set:Alarm time now set to 23/05/2019 20:50:01.
> [ OK ] rtc.alarm_wkalm_set
> [ RUN ] rtc.alarm_alm_set_minute
> rtctest.c:239:rtc.alarm_alm_set_minute:Alarm time now set to 20:51:00.
> Alarm clock
> $rtctest.c:258:rtc.alarm_alm_set_minute:data: 1a0
>
I just sent a fix for that timeout issue.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-23 22:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 16:59 about selftests/rtc test related stuff Jeffrin Thalakkottoor
2019-05-23 17:47 ` alexandre.belloni
2019-05-23 17:47 ` Alexandre Belloni
2019-05-23 17:47 ` Alexandre Belloni
2019-05-23 21:06 ` jeffrin
2019-05-23 21:06 ` Jeffrin Thalakkottoor
2019-05-23 21:06 ` Jeffrin Thalakkottoor
2019-05-23 22:52 ` alexandre.belloni [this message]
2019-05-23 22:52 ` Alexandre Belloni
2019-05-23 22:52 ` Alexandre Belloni
2019-05-24 13:53 ` jeffrin
2019-05-24 13:53 ` Jeffrin Thalakkottoor
2019-05-24 13:53 ` Jeffrin Thalakkottoor
2019-05-24 17:04 ` alexandre.belloni
2019-05-24 17:04 ` Alexandre Belloni
2019-05-24 17:04 ` Alexandre Belloni
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=20190523225219.GZ3274@piout.net \
--to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.