[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070301205016.078c3b32@inspiron>
Date: Thu, 1 Mar 2007 20:50:16 +0100
From: Alessandro Zummo <alessandro.zummo@...ertech.it>
To: "Mike Frysinger" <vapier.adi@...il.com>
Cc: "David Brownell" <david-b@...bell.net>, akpm@...ux-foundation.org,
bryan.wu@...log.com, mm-commits@...r.kernel.org,
a.zummo@...ertech.it, "Paul Mundt" <lethal@...ux-sh.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: + blackfin-on-chip-rtc-controller-driver.patch added to -mm
tree
On Thu, 1 Mar 2007 14:06:49 -0500
"Mike Frysinger" <vapier.adi@...il.com> wrote:
> > It's unclear why you
> > chose to report "pending" (irq issued but not yet acked) since
> > that's uselessly transient state on non-polled hardwre. (That
> > flag definition came from EFI, a polled firmware RTC.)
>
> because other drivers do ? there is no documentation here that covers
> what exactly the read_alarm function in the rtc_class_ops is supposed
> to do which leaves it up to people looking at other drivers
there has been a bit of confusion on this topic. I think it's
now the time to exactly define what should happen with
alarms and how they should be reported back to the class.
I'm usually inclined to agree with David on that particular topic :)
other than that, I would like to remove the /proc interface in the
future, so users are advised not to count on it and device
authors to not add properties.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists