From: David Brownell <david-b@pacbell.net>
To: Kim Phillips <kim.phillips@freescale.com>
Cc: Olof Johansson <olof@lixom.net>,
galak@kernel.crashing.org, trini@kernel.crashing.org,
linuxppc-dev@ozlabs.org, paulus@samba.org,
Scott Wood <scottwood@freescale.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] generic RTC support for PPC
Date: Tue, 30 Jan 2007 11:55:46 -0800 [thread overview]
Message-ID: <200701301155.48128.david-b@pacbell.net> (raw)
In-Reply-To: <20070130132527.0ee3e9ea.kim.phillips@freescale.com>
On Tuesday 30 January 2007 11:25 am, Kim Phillips wrote:
>
> For the MDS boards, which use the ds1374, I'd rather fix the problem properly
> and add a ds1374 driver to the RTC class. While Scott Wood (cc'd) has already
> done the port, I believe his patches are pending some patches by David Brownell.
I can't imagine what such patches would be, unless maybe you're referring to
I2C framework updates that make it follow the driver model and support platform
specific data, like an RTC alarm's IRQ number? Those will take some time.
Just submit a normal I2C driver for that RTC, and any IRQ capability can be
added later. (Or as a board-specific patch, which seems to be the normal
solution for I2C, though they won't go upstream.)
- Dave
prev parent reply other threads:[~2007-01-30 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070125073754.GA10004@lixom.net>
[not found] ` <20070130051736.GH28746@smtp.west.cox.net>
[not found] ` <0747B3CD-F875-4A28-8199-1A7FF3666301@kernel.crashing.org>
[not found] ` <20070130160340.GA25443@lixom.net>
2007-01-30 19:25 ` [PATCH] generic RTC support for PPC Kim Phillips
2007-01-30 19:55 ` David Brownell [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=200701301155.48128.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=galak@kernel.crashing.org \
--cc=kim.phillips@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=trini@kernel.crashing.org \
/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