From: Anup Patel <anup@brainfault.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"open list:RISC-V" <qemu-riscv@nongnu.org>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
Bastian Koppelmann <kbastian@mail.uni-paderborn.de>,
Anup Patel <Anup.Patel@wdc.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Atish Patra <Atish.Patra@wdc.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
Alistair Francis <alistair23@gmail.com>
Subject: Re: [PATCH v5 0/2] RTC support for QEMU RISC-V virt machine
Date: Sun, 3 Nov 2019 12:42:38 +0530 [thread overview]
Message-ID: <CAAhSdy1MZPaNhHxR345bu4HOtDndd5eZWJp2eTwJSym+9NjD+w@mail.gmail.com> (raw)
In-Reply-To: <mhng-111ec6b3-0e63-4f94-a1ed-8ddcd354b943@palmer-si-x1c4>
On Sat, Nov 2, 2019 at 4:44 AM Palmer Dabbelt <palmer@dabbelt.com> wrote:
>
> On Fri, 01 Nov 2019 08:40:24 PDT (-0700), anup@brainfault.org wrote:
> > On Tue, Oct 29, 2019 at 6:55 PM Alistair Francis <alistair23@gmail.com> wrote:
> >>
> >> On Fri, Oct 25, 2019 at 6:28 AM Anup Patel <Anup.Patel@wdc.com> wrote:
> >> >
> >> > This series adds RTC device to QEMU RISC-V virt machine. We have
> >> > selected Goldfish RTC device model for this. It's a pretty simple
> >> > synthetic device with few MMIO registers and no dependency external
> >> > clock. The driver for Goldfish RTC is already available in Linux so
> >> > we just need to enable it in Kconfig for RISCV and also update Linux
> >> > defconfigs.
> >> >
> >> > We have tested this series with Linux-5.4-rc4 plus defconfig changes
> >> > available in 'goldfish_rtc_v2' branch of:
> >> > https://github.com/avpatel/linux.git
> >>
> >> @Peter Maydell this has been reviewed, do you mind taking this in you
> >> next PR? I don't see a maintainer for hw/rtc.
> >
> > It would be great if this series can be taken for QEMU-4.2
>
> It doesn't look like there's anyone who maintains hw/rtc, so maybe that's why
> this has been going slowly? I'd happy to PR it, but I don't really have the
> bandwidth to sign up to maintain more stuff right now.
No problem, I will maintain Goldfish RTC emulation until someone else
is willing to maintain it.
Regards,
Anup
>
> >
> > Regards,
> > Anup
> >
> >>
> >> Alistair
> >>
> >> >
> >> > Changes since v4:
> >> > - Fixed typo in trace event usage
> >> > - Moved goldfish_rtc.h to correct location
> >> >
> >> > Changes since v3:
> >> > - Address all nit comments from Alistair
> >> >
> >> > Changes since v2:
> >> > - Rebased on RTC code refactoring
> >> >
> >> > Changes since v1:
> >> > - Implemented VMState save/restore callbacks
> >> >
> >> > Anup Patel (2):
> >> > hw: rtc: Add Goldfish RTC device
> >> > riscv: virt: Use Goldfish RTC device
> >> >
> >> > hw/riscv/Kconfig | 1 +
> >> > hw/riscv/virt.c | 15 ++
> >> > hw/rtc/Kconfig | 3 +
> >> > hw/rtc/Makefile.objs | 1 +
> >> > hw/rtc/goldfish_rtc.c | 288 ++++++++++++++++++++++++++++++++++
> >> > hw/rtc/trace-events | 4 +
> >> > include/hw/riscv/virt.h | 2 +
> >> > include/hw/rtc/goldfish_rtc.h | 46 ++++++
> >> > 8 files changed, 360 insertions(+)
> >> > create mode 100644 hw/rtc/goldfish_rtc.c
> >> > create mode 100644 include/hw/rtc/goldfish_rtc.h
> >> >
> >> > --
> >> > 2.17.1
> >> >
next prev parent reply other threads:[~2019-11-03 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 4:28 [PATCH v5 0/2] RTC support for QEMU RISC-V virt machine Anup Patel
2019-10-25 4:28 ` [PATCH v5 1/2] hw: rtc: Add Goldfish RTC device Anup Patel
2019-10-29 13:22 ` Alistair Francis
2019-10-25 4:28 ` [PATCH v5 2/2] riscv: virt: Use " Anup Patel
2019-10-29 13:24 ` [PATCH v5 0/2] RTC support for QEMU RISC-V virt machine Alistair Francis
2019-11-01 15:40 ` Anup Patel
2019-11-01 23:14 ` Palmer Dabbelt
2019-11-03 7:12 ` Anup Patel [this message]
2019-11-04 22:35 ` Alistair Francis
2019-11-02 10:37 ` Peter Maydell
2019-11-04 22:38 ` Alistair Francis
2019-11-05 18:43 ` Palmer Dabbelt
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=CAAhSdy1MZPaNhHxR345bu4HOtDndd5eZWJp2eTwJSym+9NjD+w@mail.gmail.com \
--to=anup@brainfault.org \
--cc=Alistair.Francis@wdc.com \
--cc=Anup.Patel@wdc.com \
--cc=Atish.Patra@wdc.com \
--cc=alistair23@gmail.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=palmer@dabbelt.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).