Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: rtc-linux@googlegroups.com, linux-mips@linux-mips.org,
	a.zummo@towertech.it, ralf@linux-mips.org
Subject: Re: [PATCH] M48T35: new RTC driver
Date: Mon, 4 Aug 2008 09:49:09 +0200	[thread overview]
Message-ID: <20080804074909.GA5760@alpha.franken.de> (raw)
In-Reply-To: <20080804.105151.213759441.nemoto@toshiba-tops.co.jp>

On Mon, Aug 04, 2008 at 10:51:51AM +0900, Atsushi Nemoto wrote:
> On Sun,  3 Aug 2008 19:41:40 +0200 (CEST), Thomas Bogendoerfer <tsbogend@alpha.franken.de> wrote:
> > This driver replaces the broken ip27-rtc driver in drivers/char and
> > gives back RTC support for SGI IP27 machines.
> ...
> > +config RTC_DRV_M48T35
> > +	tristate "ST M48T35"
> > +	depends on SGI_IP27
> 
> Is this driver really IP27 specific?  Let's make drivers generic as
> possible.

ok, will change that.

> > +	if ((hrs >= 24) || (min >= 60) || (sec >= 60))
> > +		return -EINVAL;
> 
> rtc_valid_tm() can be used?

good idea.

> > +	priv->baseaddr = res->start;
> > +	priv->reg = (struct m48t35_rtc __iomem *)res->start;
> 
> It seems priv->baseaddr is a physical address and priv->reg is a
> virtual address.  ioremap() is not needed?

I've misued res->start to pass the pointer, which was used by the old
rtc driver. I'll switch over to pass a physical address and add ioremap
code.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2008-08-04  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03 17:41 [PATCH] M48T35: new RTC driver Thomas Bogendoerfer
2008-08-04  1:51 ` Atsushi Nemoto
2008-08-04  7:49   ` Thomas Bogendoerfer [this message]

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=20080804074909.GA5760@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=a.zummo@towertech.it \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --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