public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Laurent Pinchart
	<laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>
Cc: a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org,
	i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org,
	rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	Rod Whitby <rod-wR+KslBqWDsXC2x5gXVKYQ@public.gmane.org>
Subject: Re: PCF8563 doesn't pass validation check
Date: Wed, 2 Jul 2008 13:10:20 +0200	[thread overview]
Message-ID: <20080702131020.28e1979a@hyperion.delvare> (raw)
In-Reply-To: <200807021134.59668.laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>

Hi Laurent,

On Wed, 2 Jul 2008 11:34:55 +0200, Laurent Pinchart wrote:
> I'm having issues with the PCF8563 RTC chip.
> 
> The Linux driver tries to validate the chip by checking if the
> BCD-coded time and date registers contain valid values.
> 
> When a low voltage condition is detected, the registers are not
> guaranteed to contain valid values. Experimentation showed that
> while the seconds, minutes, hours and day of the week registers
> didn't cause any issue, the months register could get out of the
> 01-12 range.
> 
> Has anyone experienced the same issue ?

This issue sounds familiar, I think Alessandro mentioned it to me a few
weeks ago in private already.

> Would it be acceptable to remove the months register check ?

I think you should convert rtc-pcf8563 to a new-style i2c driver. Then
the whole validation function becomes pointless and you can delete it.
I guess that the PCF8563 chip is used in embedded designs with platform
code to instantiate the I2C devices as needed, so it should work fine.
Apparently some IXP4xx platforms already expect rtc-pcf8563 to be a
new-style i2c driver... I'm curious if some ARM people have already
converted the driver. Rod?

> I've contacted NXP to get more information about what the chip
> guarantees and what it doesn't. I haven't had any answer yet but
> I expect them to tell me there is no guarantee at all.

-- 
Jean Delvare

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

  parent reply	other threads:[~2008-07-02 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02  9:34 PCF8563 doesn't pass validation check Laurent Pinchart
     [not found] ` <200807021134.59668.laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>
2008-07-02 11:10   ` Jean Delvare [this message]
     [not found]     ` <20080702131020.28e1979a-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-07-02 11:17       ` Laurent Pinchart
     [not found]         ` <200807021317.50944.laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org>
2008-07-02 11:25           ` Jean Delvare
2008-07-02 11:21       ` Rod Whitby

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=20080702131020.28e1979a@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=a.zummo-BfzFCNDTiLLj+vYz1yj4TQ@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=laurentp-BSmb2szPELAwsLKNixborgC/G2K4zDHf@public.gmane.org \
    --cc=rod-wR+KslBqWDsXC2x5gXVKYQ@public.gmane.org \
    --cc=rtc-linux-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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