From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] rtc: add support for Freescale SNVS RTC
Date: Fri, 13 Apr 2012 22:18:43 +0200 [thread overview]
Message-ID: <20120413201843.GF20478@pengutronix.de> (raw)
In-Reply-To: <4F88515A.2020805@linaro.org>
On Sat, Apr 14, 2012 at 12:16:26AM +0800, Ying-Chun Liu (PaulLiu) wrote:
> >
> > I haven't completely understood this, and will need more study.
> >
>
> Hi Shawn,
>
> About the above ioctl() related blocks. I think it is used by some user
> space libs that requires accurate time (47BIT TIME). And it have to be
> sure that the time continuously flowing so the apps wants to be notified
> that the rtc is changed dramatically by the set command.
>
> I'm guessing that it might be related to the Multimedia binary libs. A/V
> sync or something like that. But I don't have those source code. Please
> make sure those libs are not using it.
>
> I also see other Freescale RTC driver implement the same function. For
> example:
> http://tinyurl.com/cnp93jv
> So I guess it might be a common ioctl that Freescale uses somewhere.
>
> So my plan is to split the IOR to a header file. And keep the rest as is.
'think', 'might' and 'something like that' are the wrong words to
convince anybody that these ioctls are needed. So unless you find real
usecases and also can convince us that it's not possible to reach your
goal using either the existing ioctls or an additional common (non fsl
specific) ioctl please just drop them.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2012-04-13 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 13:04 [PATCH] rtc: add support for Freescale SNVS RTC Ying-Chun Liu (PaulLiu)
2012-03-22 15:11 ` Shawn Guo
2012-04-13 16:16 ` Ying-Chun Liu (PaulLiu)
2012-04-13 20:18 ` Sascha Hauer [this message]
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=20120413201843.GF20478@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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).