From: Prarit Bhargava <prarit@redhat.com>
To: Alessandro Zummo <a.zummo@towertech.it>
Cc: John Stultz <john.stultz@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"x86@kernel.org" <x86@kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
David Vrabel <david.vrabel@citrix.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andi Kleen <ak@linux.intel.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>
Subject: Re: [RFE PATCH 2/2] rtc, add write functionality to sysfs
Date: Sun, 24 Feb 2013 12:03:01 -0500 [thread overview]
Message-ID: <512A47C5.3010500@redhat.com> (raw)
In-Reply-To: <B22B05C4-B8D2-44B9-971B-37913DE59EF6@towertech.it>
On 02/23/2013 06:11 PM, Alessandro Zummo wrote:
> On 22/feb/2013, at 22:05, John Stultz <john.stultz@linaro.org> wrote:
>
>> On 02/22/2013 12:55 PM, Prarit Bhargava wrote:
>>>
>>> On 02/22/2013 03:43 PM, John Stultz wrote:
>>>> On 02/14/2013 09:02 AM, Prarit Bhargava wrote:
>>>>> /sys/class/rtc/rtcX/date and /sys/class/rtc/rtcX/time currently have
>>>>> read-only access. This patch introduces write functionality which will
>>>>> set the rtc time.
>>>>>
>>>>> Usage: echo YYYY-MM-DD > /sys/class/rtc/rtcX/date
>>>>> echo HH:MM:SS > /sys/class/rtc/rtcX/time
>>>> Why do we want to add a new interface here?
>>> John,
>>>
>>> I'm not adding a new interface. The current date/time interface only handles
>>> read and I'm introducing write.
>>>
>>
>> Right, but what benefit does that provide?
>> (I'm not saying there isn't any, its just not clear from your patch why this is a good thing.)
>>
Sorry John, I misunderstood your question.
>> Also CC'ing Alessandro for his input.
>
> I'd like to keep the interfaces as simple as possible but I'm open to improvements if there are good use cases.
>
AFAICT there is no way for me to "test" or use the write from userspace.
hwclock uses the SET_TIME ioctl, which is a different code path AFAICT.
I'd like to be at least able to test this stuff when we make changes to it so I
think having write functionality for date & time is worthwhile.
For me, I'm using these to heavily test ntp and ntpdate over system reboots.
OOC, Alessandro, why is the date & time split into two fields?
P.
next prev parent reply other threads:[~2013-02-24 17:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 17:02 [RFE PATCH 0/2] x86, rtc, ntp, Enable full rtc synchronization Prarit Bhargava
2013-02-14 17:02 ` [RFE PATCH 1/2] x86, rtc, ntp, Do full rtc synchronization with ntp Prarit Bhargava
2013-02-22 20:42 ` John Stultz
2013-02-24 17:12 ` Prarit Bhargava
2013-02-25 15:04 ` Alessandro Zummo
2013-02-14 17:02 ` [RFE PATCH 2/2] rtc, add write functionality to sysfs Prarit Bhargava
2013-02-22 20:43 ` John Stultz
2013-02-22 20:55 ` Prarit Bhargava
2013-02-22 21:05 ` John Stultz
2013-02-23 23:11 ` Alessandro Zummo
2013-02-24 17:03 ` Prarit Bhargava [this message]
2013-02-25 14:58 ` Alessandro Zummo
2013-02-28 14:50 ` Prarit Bhargava
2013-02-28 18:51 ` John Stultz
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=512A47C5.3010500@redhat.com \
--to=prarit@redhat.com \
--cc=a.zummo@towertech.it \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=david.vrabel@citrix.com \
--cc=john.stultz@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=rtc-linux@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 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).