From: Mark Zhan <rongkai.zhan@windriver.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: a.zummo@towertech.it, rtc-linux@googlegroups.com,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Add the support of ST M48T59 RTC chip in rtc-class driver subsystem
Date: Tue, 12 Jun 2007 21:59:36 +0800 [thread overview]
Message-ID: <1181656776.3975.16.camel@mark> (raw)
In-Reply-To: <20070611121145.GA11297@iram.es>
Hi Gabriel,
On Mon, 2007-06-11 at 14:11 +0200, Gabriel Paubert wrote:
....
> There are other boards which have exactly the same chip, but use
> a very different (uglier) access method: using ISA 2 I/O ports
> (0x74 and 0x75) to write the address and another port (0x77) to
> read/write the data.
>
> Besides that, these boards also use the NVRAM part which means that
> a spinlock must be used to serialize between RTC and NVRAM access.
>
> I have no idea whether the drivers should be shared or two
> different drivers should be written... But if there are two
> different drivers, there should be a way to distinguish them
> (different config name, different module names, and some
> explanation in the config help text).
>
I will rework this driver to add a platform data structure which enables
the platform to provide the platform specific access method.
For the NVRAM issue, I have no idea how other boards access the NVRAM.
So could you provide me more information?
> > +
> > +static unsigned char * m48t59_vbase = NULL;
> > +static unsigned int m48t59_irq = -1;
>
> Shouldn't it be NO_IRQ (here and in several other places) ?
>
Yeah, agree. I will modify it.
Thanks your comment.
Best Regards
Mark Zhan
next prev parent reply other threads:[~2007-06-12 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 7:56 [PATCH] Add the support of ST M48T59 RTC chip in rtc-class driver subsystem Mark Zhan
2007-06-11 11:25 ` [rtc-linux] " Alessandro Zummo
2007-06-11 12:11 ` Gabriel Paubert
2007-06-12 13:59 ` Mark Zhan [this message]
2007-06-12 14:12 ` Mark Zhan
2007-06-19 12:29 ` Alessandro Zummo
2007-06-14 10:32 ` Gabriel Paubert
2007-06-11 14:35 ` Milton Miller
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=1181656776.3975.16.camel@mark \
--to=rongkai.zhan@windriver.com \
--cc=a.zummo@towertech.it \
--cc=linuxppc-dev@ozlabs.org \
--cc=paubert@iram.es \
--cc=rtc-linux@googlegroups.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;
as well as URLs for NNTP newsgroup(s).