From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: marcus.wolf@wolf-entwicklungen.de
Cc: a.zummo@towertech.it, havasi@efr.de, linux-rtc@vger.kernel.org,
b.spranger@linutronix.de
Subject: Re: RTC Epson Toyocom RX-8025T
Date: Mon, 5 Aug 2019 15:05:26 +0200 [thread overview]
Message-ID: <20190805130526.GD3600@piout.net> (raw)
In-Reply-To: <20190727084806.7DF892CE0139@dd39320.kasserver.com>
Hi,
On 27/07/2019 10:48:06+0200, marcus.wolf@wolf-entwicklungen.de wrote:
> 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?
I think that what you have is actually a RX-8801SA. Can you check that the
register layout is the same? The datasheet is available here:
https://support.epson.biz/td/api/doc_check.php?dl=app_RX-8801SA&lang=en
> On which base you'd like to see the patches? Head of mainline, last stable
> (5.2.2), or ....?
>
v5.3-rc1 or rtc-next.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next parent reply other threads:[~2019-08-05 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190727084806.7DF892CE0139@dd39320.kasserver.com>
2019-08-05 13:05 ` Alexandre Belloni [this message]
2019-08-05 13:16 ` RTC Epson Toyocom RX-8025T Alexandre Belloni
2019-08-06 12:21 ` Marcus Wolf
2019-07-27 9:00 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=20190805130526.GD3600@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=b.spranger@linutronix.de \
--cc=havasi@efr.de \
--cc=linux-rtc@vger.kernel.org \
--cc=marcus.wolf@wolf-entwicklungen.de \
/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