From: Rick Niles <niles@rickniles.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Sub jiffy delay?
Date: Thu, 24 Nov 2005 10:11:53 -0500 [thread overview]
Message-ID: <4385D839.7000005@rickniles.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0511231646100.20759@chaos.analogic.com>
Well, I think the best answer for a distribution kernel without making a
any patches or rebuilding anything is to use the "register_rtc()" hook
in the rtc driver. I tried it and it works really well. This way my
device driver can drop into a Fedora system without the user having to
rebuild anything (other than my driver).
If I want to get fancy I could check to see if IRQ 8 is taken and use
it directly if it's not, i.e. the RTC driver isn't loaded. If IRQ 8 is
taken, check for the RTC driver and then use that via register_rtc().
In the unlikely event that IRQ 8 is taken and it's not by the RTC
driver, then I guess the user's out of luck.
Thanks for all the suggestions, they've all been good, but I'm trying
avoid steep requirements on usage of this driver.
Rick Niles.
prev parent reply other threads:[~2005-11-24 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 20:39 Sub jiffy delay? Rick Niles
2005-11-23 20:50 ` Lennart Sorensen
2005-11-23 21:20 ` Steven Rostedt
2005-11-23 22:07 ` linux-os (Dick Johnson)
2005-11-24 15:11 ` Rick Niles [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=4385D839.7000005@rickniles.com \
--to=niles@rickniles.com \
--cc=linux-kernel@vger.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