From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC] ARM: omap2: fix lack of timer interrupts on CPU1 after hotplug
Date: Thu, 7 Feb 2019 07:51:39 -0800 [thread overview]
Message-ID: <20190207155139.GC5720@atomide.com> (raw)
In-Reply-To: <20190207134548.43yyk3wsadwvcmd6@shell.armlinux.org.uk>
* Russell King - ARM Linux admin <linux@armlinux.org.uk> [190207 13:46]:
> On Wed, Dec 12, 2018 at 10:57:41AM -0800, Tony Lindgren wrote:
> > * Tony Lindgren <tony@atomide.com> [181212 17:53]:
> > > * Russell King <rmk+kernel@armlinux.org.uk> [181212 11:49]:
> > > > We call tick_broadcast_enter() in omap_enter_idle_coupled(), which one
> > > > would expect would take care of the issue, but internally this only
> > > > deals with one-shot local timers - tick_broadcast_enable() on the other
> > > > hand only deals with periodic local timers. So, we need to call both.
> > >
> > > This works just fine for me for NO_HZ and cpuidle:
> > >
> > > Tested-by: Tony Lindgren <tony@atomide.com>
> >
> > And also works for me without NO_HZ too FYI.
>
> Hi Tony,
>
> Could you pick this patch up and submit for 5.0-rc please?
Oh sorry. I thought you had already merged it since I added
my Tested-by. Hmm I guess I need to start adding also an
Acked-by to signal it's OK to pick some misc patches.
Anyways, applying into omap-for-v5.0/fixes-v2.
Thanks,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-07 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 11:49 [PATCH RFC] ARM: omap2: fix lack of timer interrupts on CPU1 after hotplug Russell King
2018-12-12 17:53 ` Tony Lindgren
2018-12-12 18:57 ` Tony Lindgren
2019-02-07 13:45 ` Russell King - ARM Linux admin
2019-02-07 15:51 ` Tony Lindgren [this message]
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=20190207155139.GC5720@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).