Linux RTC
 help / color / mirror / Atom feed
From: marcus.wolf@wolf-entwicklungen.de
To: linux-rtc@vger.kernel.org
Subject: RTC Epson Toyocom RX-8025T
Date: Sat, 27 Jul 2019 11:00:23 +0200 (CEST)	[thread overview]
Message-ID: <20190727090023.ABF132CE0139@dd39320.kasserver.com> (raw)

Hello Alessandro, hello Alexandre,

in a product of a customer of mine, the RX-8025T real time clock from Epson Toyocom is used.

My customer would like me to integrate the driver for this clock to mainline of the kernel.

At the moment, we have a seperate implementation, basing on the implemenattion of the existing RX-8025 driver.

Although the rtc of my customer has almost the same "name" as the one, the current driver is available for (just last letter differs), it works quite different. So for example I compared the registerset of the two clocks.Only 5 of 16 registers are identical, 3 are very similar, but the other 8 are completely different. Also the functionality is quite different. Of course first of all, both are clocks, but all aditional features are not identical. The already supported SA type has two alarms - a day and a week alarm. The tyoe of my customer (t) just has one alarm, that can be switched to day and to week mode. In adition it has a timer and an 8bit RAM cell. In addition the protocol how to adress the registers on I2C is different....

Would you like me to propose you the support for the RX-8025T as a separate implementation - aka new driver?
On which base you'd like to see the patches? Head of mainline, last stable (5.2.2), or ....?

Thanks a lot,

Marcus Wolf

Wolf-Entwicklungen
Helene-Lange-Weg 23
80637 München


             reply	other threads:[~2019-07-27  9:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27  9:00 marcus.wolf [this message]
     [not found] <20190727084806.7DF892CE0139@dd39320.kasserver.com>
2019-08-05 13:05 ` RTC Epson Toyocom RX-8025T Alexandre Belloni
2019-08-05 13:16   ` Alexandre Belloni
2019-08-06 12:21     ` Marcus Wolf

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=20190727090023.ABF132CE0139@dd39320.kasserver.com \
    --to=marcus.wolf@wolf-entwicklungen.de \
    --cc=linux-rtc@vger.kernel.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