From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: linux-kernel@vger.kernel.org
Subject: [RFC] RTC subsystem, interrupt handling
Date: Wed, 28 Dec 2005 02:01:55 +0100 [thread overview]
Message-ID: <20051228020155.319f591e@inspiron> (raw)
No patches this time :)
just a few questions... the original RTC driver
supports user programmable interrupts
via rtc_register/rtc_control/rtc_unregister.
The only user in the kernel is the sound core.
My RTC subsystem doesn't support this behaviour yet,
so I was thinking about the best way to add it.
Current code assumes there's only one rtc in the system
while the new one must have a way to find a specific one.
Would something like that be acceptable:
struct class_device *rtc_open(char *name)
{
struct class_device *class_dev = NULL,
*class_dev_tmp;
down(&rtc_class->sem);
list_for_each_entry(class_dev_tmp, &rtc_class->children, node) {
if (strncmp(class_dev_tmp->class_id, name, BUS_ID_SIZE) == 0) {
class_dev = class_dev_tmp;
break;
}
}
up(&rtc_class->sem);
return class_dev;
}
?
--
Best regards,
Alessandro Zummo,
Tower Technologies - Turin, Italy
http://www.towertech.it
reply other threads:[~2005-12-28 1:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051228020155.319f591e@inspiron \
--to=alessandro.zummo@towertech.it \
--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