From: Randy Vinson <rvinson@mvista•com>
To: Kumar Gala <kumar.gala@freescale•com>
Cc: Greg KH <greg@kroah•com>,
sensors@stimpy•netroedge.com, linuxppc-embedded@ozlabs•org
Subject: Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip
Date: Fri, 03 Jun 2005 15:05:18 -0700 [thread overview]
Message-ID: <42A0D41E.6000608@mvista.com> (raw)
In-Reply-To: <5e2620f079e946d884175372dbf7e37e@freescale.com>
Kumar Gala wrote:
> Randy,
>
> I was planning on cloning the DS1337 driver once all of the latest
> patches for it got into Linus's tree.
I haven't seen any patches for the DS1337, but I admit that I wasn't
looking very hard.
Not sure if you looked at it,
> but when I was looking at RTC on 8349 the DS1337 seemed similar. Not
> sure if we can unify the DS1337 driver such that can also support the
> DS1374.
I looked at the DS1337 driver, but that chip uses individual registers
for the various time bits, whereas the DS1374 uses a 32-bit seconds
count spread across 4 registers. I wasn't convinced that I could find a
reliable way to differenciate between the 2 types at run time since they
use the same I2C address (0x68). So, I choose to create a new driver to
keep it simple. If there is a reliable way to handle both types in the
same driver, I'll drop my DS1374-specific driver.
>
> (Also, I'll wait on acceptance of the driver before pushing the board
> code).
Agreed.
Randy Vinson
next prev parent reply other threads:[~2005-06-03 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 21:36 [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Randy Vinson
2005-06-03 21:41 ` Kumar Gala
2005-06-03 22:05 ` Randy Vinson [this message]
2005-06-03 21:43 ` [PATCH 2/2] " Randy Vinson
2005-06-03 21:46 ` [PATCH 1/2] " Eugene Surovegin
2005-06-03 22:17 ` Randy Vinson
2005-06-09 17:25 ` [lm-sensors] " Jean Delvare
2005-06-09 19:06 ` Mark A. Greer
2005-06-09 19:29 ` Jean Delvare
2005-06-09 18:21 ` [lm-sensors] " Jean Delvare
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=42A0D41E.6000608@mvista.com \
--to=rvinson@mvista$(echo .)com \
--cc=greg@kroah$(echo .)com \
--cc=kumar.gala@freescale$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
--cc=sensors@stimpy$(echo .)netroedge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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