From: Rajath Shashidhara <rajaths@cs.utexas.edu>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: Looking for issues/features for my first contribution
Date: Thu, 7 Nov 2019 20:39:47 -0600 [thread overview]
Message-ID: <f300806f-ced2-5926-40ff-4cdd29c5078e@cs.utexas.edu> (raw)
In-Reply-To: <CAL1e-=j8K+FKj=4pTd8HKkL-D=F+9hY+5bF4ibM8WE+Sp+pk=Q@mail.gmail.com>
On 07-11-2019 07:33, Aleksandar Markovic wrote:
>
> I did a quick Google search on datasheets of existing RTC
> implemtations, and the result is:
>
> DS1338: https://datasheets.maximintegrated.com/en/ds/DS1338-DS1338Z.pdf
> M41T80: https://www.st.com/resource/en/datasheet/m41t80.pdf
> M48T59: http://www.elektronikjk.pl/elementy_czynne/IC/M48T59V.pdf
> MC146818: https://www.nxp.com/docs/en/data-sheet/MC146818.pdf
> PL031: http://infocenter.arm.com/help/topic/com.arm.doc.ddi0224c/real_time_clock_pl031_r1p3_technical_reference_manual_DDI0224C.pdf
> TWL92230: https://datasheet.octopart.com/TWL92230C-Texas-Instruments-datasheet-150321.pdf
> Zynq RTC: https://www.xilinx.com/support/documentation/user_guides/ug1085-zynq-ultrascale-trm.pdf
> (chapter 7)
I have a few questions about this:
[a] Is there any particular reason that you picked DS3231 ? Linux kernel
has drivers for DS3232/34 only [1]. I did read the datasheets of both
3232 & 3231 and found that they are quite similar except for the 236
bytes of SRAM support found only in 3232.
[b] As per the datasheet, DS3231 has a built-in temperature sensor.
Temperature can be read from a dedicated register. There can be two
approaches to emulating this: (1) Return a constant temperature value on
every read (2) Throw a not-supported exception/warning. What is the qemu
convention for handling such features ?
[c] DS3231 also has programmable square-wave output + 32 KHz output pin.
M41T80 chip also supports this feature. However, qemu does not support
emulation of these features [2]. Do I take the same approach ?
Thanks!
Rajath Shashidhara
References:
[1]
https://elixir.bootlin.com/linux/v5.4-rc6/source/drivers/rtc/rtc-ds3232.c
[2]
https://git.qemu.org/?p=qemu.git;a=blob;f=hw/rtc/m41t80.c;h=914ecac8f4db418633d6daf92608cb50f6b89052;hb=HEAD
next prev parent reply other threads:[~2019-11-08 2:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 23:50 Looking for issues/features for my first contribution Rajath Shashidhara
2019-11-07 10:37 ` Aleksandar Markovic
2019-11-07 13:33 ` Aleksandar Markovic
2019-11-07 18:49 ` Rajath Shashidhara
2019-11-08 2:39 ` Rajath Shashidhara [this message]
2019-11-08 9:08 ` Alex Bennée
2019-11-08 13:05 ` Richard Henderson
2019-11-08 19:31 ` Aleksandar Markovic
2019-11-09 16:01 ` Peter Maydell
2019-11-09 21:08 ` Aleksandar Markovic
2019-11-10 14:33 ` Peter Maydell
2019-11-08 19:36 ` Aleksandar Markovic
2019-11-08 21:54 ` BALATON Zoltan
2019-11-09 19:46 ` Aleksandar Markovic
2019-11-09 21:33 ` Rajath Shashidhara
2019-11-09 23:55 ` Aleksandar Markovic
2019-11-07 11:18 ` Alex Bennée
2019-11-07 13:54 ` Stefan Hajnoczi
2019-11-07 18:51 ` Rajath Shashidhara
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=f300806f-ced2-5926-40ff-4cdd29c5078e@cs.utexas.edu \
--to=rajaths@cs.utexas.edu \
--cc=aleksandar.m.mail@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).