All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miodrag Dinic <Miodrag.Dinic@syrmia.com>
To: Huacai Chen <chenhuacai@gmail.com>,
	Alessandro Zummo <a.zummo@towertech.it>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: "linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
	Fuxin Zhang <zhangfx@lemote.com>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Aleksandar Markovic <Aleksandar.Markovic@syrmia.com>,
	Petar Jovanovic <petar.jovanovic@syrmia.com>
Subject: RE: [PATCH] rtc: goldfish: Enable interrupt in set_alarm() when necessary
Date: Thu, 9 Jul 2020 10:30:36 +0000	[thread overview]
Message-ID: <VI1PR0301MB6655A9BB3411D384F045A5FE94640@VI1PR0301MB6655.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <CAAhV-H77Qm91qhvLiTTMYkEZd7NLFZa5KD0mDrHsiSrtxT7wpQ@mail.gmail.com>

Hi Huacai,

Yes, this is my new address. However I haven't been involved in kernel/QEMU community for a while now.
The patch itself looks OK to me, if you made sure the RTC device emulation on the QEMU side is now also inspecting the TIMER_IRQ_ENABLED setting.

OK I see now that you have committed upstream to QEMU the Goldfish RTC device, good job with that.
https://github.com/qemu/qemu/blame/971b2a1e5b1a8cc8f597ac5d7016908f9fa880de/hw/rtc/goldfish_rtc.c

You can add my "reviewed-by".

Glad to see that the "goldfish" project is still alive out there.

Kind regards,
Miodrag

-----Original Message-----
From: Huacai Chen <chenhuacai@gmail.com> 
Sent: Thursday, July 9, 2020 11:40 AM
To: Alessandro Zummo <a.zummo@towertech.it>; Alexandre Belloni <alexandre.belloni@bootlin.com>; Miodrag Dinic <Miodrag.Dinic@syrmia.com>
Cc: linux-rtc@vger.kernel.org; Fuxin Zhang <zhangfx@lemote.com>; Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH] rtc: goldfish: Enable interrupt in set_alarm() when necessary

Hi, Midorag,

Maybe miodrag.dinic@syrmia.com is your new email address? Please review this patch.
And Alessandro, Alexandre, could you please help to review this patch?

Huacai

On Fri, Jul 3, 2020 at 11:00 AM Huacai Chen <chenhuacai@gmail.com> wrote:
>
> Ping?
>
> On Sat, Jun 20, 2020 at 8:03 PM Huacai Chen <chenhc@lemote.com> wrote:
> >
> > When use goldfish rtc, the "hwclock" command fails with "select() to 
> > /dev/rtc to wait for clock tick timed out". This is because "hwclock"
> > need the set_alarm() hook to enable interrupt when alrm->enabled is 
> > true. This operation is missing in goldfish rtc (but other rtc 
> > drivers, such as cmos rtc, enable interrupt here), so add it.
> >
> > Signed-off-by: Huacai Chen <chenhc@lemote.com>
> > Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> > ---
> >  drivers/rtc/rtc-goldfish.c | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/rtc/rtc-goldfish.c b/drivers/rtc/rtc-goldfish.c 
> > index 1a3420e..d5083b0 100644
> > --- a/drivers/rtc/rtc-goldfish.c
> > +++ b/drivers/rtc/rtc-goldfish.c
> > @@ -73,6 +73,7 @@ static int goldfish_rtc_set_alarm(struct device *dev,
> >                 rtc_alarm64 = rtc_tm_to_time64(&alrm->time) * NSEC_PER_SEC;
> >                 writel((rtc_alarm64 >> 32), base + TIMER_ALARM_HIGH);
> >                 writel(rtc_alarm64, base + TIMER_ALARM_LOW);
> > +               writel(1, base + TIMER_IRQ_ENABLED);
> >         } else {
> >                 /*
> >                  * if this function was called with enabled=0
> > --
> > 2.7.0
> >

  reply	other threads:[~2020-07-09 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20 12:04 [PATCH] rtc: goldfish: Enable interrupt in set_alarm() when necessary Huacai Chen
2020-07-03  3:00 ` Huacai Chen
2020-07-09  9:39   ` Huacai Chen
2020-07-09 10:30     ` Miodrag Dinic [this message]
2020-07-16  9:16 ` Alexandre Belloni

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=VI1PR0301MB6655A9BB3411D384F045A5FE94640@VI1PR0301MB6655.eurprd03.prod.outlook.com \
    --to=miodrag.dinic@syrmia.com \
    --cc=Aleksandar.Markovic@syrmia.com \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=chenhuacai@gmail.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-rtc@vger.kernel.org \
    --cc=petar.jovanovic@syrmia.com \
    --cc=zhangfx@lemote.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.