From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: "Mike Frysinger" <vapier.adi@gmail.com>
Cc: "David Brownell" <david-b@pacbell.net>,
akpm@linux-foundation.org, bryan.wu@analog.com,
mm-commits@vger.kernel.org, a.zummo@towertech.it,
"Paul Mundt" <lethal@linux-sh.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: + blackfin-on-chip-rtc-controller-driver.patch added to -mm tree
Date: Thu, 1 Mar 2007 20:50:16 +0100 [thread overview]
Message-ID: <20070301205016.078c3b32@inspiron> (raw)
In-Reply-To: <8bd0f97a0703011106j7cb3664dx190686b0251cd1fa@mail.gmail.com>
On Thu, 1 Mar 2007 14:06:49 -0500
"Mike Frysinger" <vapier.adi@gmail.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
next prev parent reply other threads:[~2007-03-01 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703010848.l218me3e008819@shell0.pdx.osdl.net>
[not found] ` <200703011039.32876.david-b@pacbell.net>
2007-03-01 19:06 ` Mike Frysinger
2007-03-01 19:50 ` Alessandro Zummo [this message]
2007-03-01 21:35 ` David Brownell
2007-03-01 21:56 ` Mike Frysinger
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=20070301205016.078c3b32@inspiron \
--to=alessandro.zummo@towertech.it \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=david-b@pacbell.net \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=vapier.adi@gmail.com \
/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
all inboxes | Powered by JetHome®