Date: Wed, 28 Dec 2005 02:01:55 +0100
From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: linux-kernel@vger.kernel.org
Subject: [RFC] RTC subsystem, interrupt handling
Message-ID: <20051228020155.319f591e@inspiron>
Organization: Tower Technologies
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1320
Lines: 51


 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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/