public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Jan Kardell <jan.kardell@telliq.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
	rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
	Vincent Donnefort <vdonnefort@gmail.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: rtc: NXP pcf8563 vs Haoyu hym8563
Date: Mon, 27 Oct 2014 16:41:34 +0100	[thread overview]
Message-ID: <2860269.ao8SIdITjk@diego> (raw)
In-Reply-To: <544E59C3.7010309@telliq.com>

Hi Jan,

Am Montag, 27. Oktober 2014, 15:42:11 schrieb Jan Kardell:
> Hi,
> 
> Erlier this year the hym8563 driver was added to the kernel. When I compared
> the datasheets of the NXP pcf8563 (that I use) and the Haoyu hym8563 I
> cannot
> find any significantdifferences between the two chips. Now is using
> different
> drivers for the two similar (or identical?) chips:
> a) A mistake
> b) A feature
> c) Me beeing stupid?

option A - a mistake

At the time I didn't check existing drivers for one with a compatible 
interface - wrongly thinking different vendors wouldn't use the same 
interfaces.

I learned from this and am not making this mistake again [0] :-), but haven't 
had the time so far to consolidate the two rtc drivers back into one.


> The difference between the drivers is handling of century and that the
> hym8563
> driver support the clock output that both chips have.

Feel free to consolidate them if you have time to spare - alternativly I 
hopefully also will have time for this some time in the future.


Heiko


[0] https://lkml.org/lkml/2014/9/14/178

      reply	other threads:[~2014-10-27 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 14:42 rtc: NXP pcf8563 vs Haoyu hym8563 Jan Kardell
2014-10-27 15:41 ` Heiko Stübner [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=2860269.ao8SIdITjk@diego \
    --to=heiko@sntech.de \
    --cc=a.zummo@towertech.it \
    --cc=dan.carpenter@oracle.com \
    --cc=jan.kardell@telliq.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtc-linux@googlegroups.com \
    --cc=vdonnefort@gmail.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