All of lore.kernel.org
 help / color / mirror / Atom feed
From: rvinson@mvista.com (Randy Vinson)
To: Kumar Gala <kumar.gala@freescale.com>
Cc: Greg KH <greg@kroah.com>,
	sensors@stimpy.netroedge.com, linuxppc-embedded@ozlabs.org
Subject: [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374
Date: Sat, 04 Jun 2005 07:59:29 +0000	[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


WARNING: multiple messages have this Message-ID (diff)
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

  reply	other threads:[~2005-06-04  7:59 UTC|newest]

Thread overview: 20+ 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-04  7:59 ` [lm-sensors] [PATCH 1/2] Add support for Maxim/Dallas DS1374 Randy Vinson
2005-06-03 21:41 ` [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Kumar Gala
2005-06-04  7:59   ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Kumar Gala
2005-06-03 22:05   ` Randy Vinson [this message]
2005-06-04  7:59     ` Randy Vinson
2005-06-03 21:43 ` [PATCH 2/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Randy Vinson
2005-06-04  7:59   ` [lm-sensors] [PATCH 2/2] Add support for Maxim/Dallas DS1374 Randy Vinson
2005-06-03 21:46 ` [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Eugene Surovegin
2005-06-04  7:59   ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Eugene Surovegin
2005-06-03 22:17   ` [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Randy Vinson
2005-06-04  7:59     ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Randy Vinson
2005-06-09 17:25     ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Jean Delvare
2005-06-09 19:26       ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas Jean Delvare
2005-06-09 19:06       ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Mark A. Greer
2005-06-09 21:07         ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Mark A. Greer
2005-06-09 19:29         ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Jean Delvare
2005-06-09 21:30           ` [lm-sensors] Re: [PATCH 1/2] Add support for Maxim/Dallas Jean Delvare
2005-06-09 18:21 ` [lm-sensors] [PATCH 1/2] Add support for Maxim/Dallas DS1374 Real-Time Clock Chip Jean Delvare
2005-06-09 20:21   ` [lm-sensors] [PATCH 1/2] Add support for Maxim/Dallas DS1374 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.com \
    --cc=greg@kroah.com \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=sensors@stimpy.netroedge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.