From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Guo Ren <guoren@linux.alibaba.com>,
Xu Kai <xukai@nationalchip.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sasha Levin <sashal@kernel.org>,
linux-csky@vger.kernel.org
Subject: [PATCH AUTOSEL 5.4 01/18] clocksource/drivers/timer-gx6605s: Fixup counter reload
Date: Mon, 28 Sep 2020 21:30:47 -0400 [thread overview]
Message-ID: <20200929013105.2406634-1-sashal@kernel.org> (raw)
From: Guo Ren <guoren@linux.alibaba.com>
[ Upstream commit bc6717d55d07110d8f3c6d31ec2af50c11b07091 ]
When the timer counts to the upper limit, an overflow interrupt is
generated, and the count is reset with the value in the TIME_INI
register. But the software expects to start counting from 0 when
the count overflows, so it forces TIME_INI to 0 to solve the
potential interrupt storm problem.
Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
Tested-by: Xu Kai <xukai@nationalchip.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/1597735877-71115-1-git-send-email-guoren@kernel.org
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
drivers/clocksource/timer-gx6605s.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clocksource/timer-gx6605s.c b/drivers/clocksource/timer-gx6605s.c
index 80d0939d040b5..8d386adbe8009 100644
--- a/drivers/clocksource/timer-gx6605s.c
+++ b/drivers/clocksource/timer-gx6605s.c
@@ -28,6 +28,7 @@ static irqreturn_t gx6605s_timer_interrupt(int irq, void *dev)
void __iomem *base = timer_of_base(to_timer_of(ce));
writel_relaxed(GX6605S_STATUS_CLR, base + TIMER_STATUS);
+ writel_relaxed(0, base + TIMER_INI);
ce->event_handler(ce);
--
2.25.1
next reply other threads:[~2020-09-29 1:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 1:30 Sasha Levin [this message]
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 02/18] libbpf: Remove arch-specific include path in Makefile Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 03/18] drivers/net/wan/hdlc_fr: Add needed_headroom for PVC devices Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 04/18] drm/sun4i: mixer: Extend regmap max_register Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 05/18] net: dec: de2104x: Increase receive ring size for Tulip Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 06/18] rndis_host: increase sleep time in the query-response loop Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 07/18] nvme-core: get/put ctrl and transport module in nvme_dev_open/release() Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 08/18] regmap: debugfs: Fix handling of name string for debugfs init delays Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 09/18] fuse: fix the ->direct_IO() treatment of iov_iter Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 10/18] drivers/net/wan/lapbether: Make skb->protocol consistent with the header Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 11/18] drivers/net/wan/hdlc: Set skb->protocol before transmitting Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 12/18] mac80211: Fix radiotap header channel flag for 6GHz band Sasha Levin
2020-09-29 1:30 ` [PATCH AUTOSEL 5.4 13/18] mac80211: do not allow bigger VHT MPDUs than the hardware supports Sasha Levin
2020-09-29 1:31 ` [PATCH AUTOSEL 5.4 14/18] tracing: Make the space reserved for the pid wider Sasha Levin
2020-09-29 1:31 ` [PATCH AUTOSEL 5.4 15/18] tools/io_uring: fix compile breakage Sasha Levin
2020-09-29 1:31 ` [PATCH AUTOSEL 5.4 16/18] spi: fsl-espi: Only process interrupts for expected events Sasha Levin
2020-09-29 1:31 ` [PATCH AUTOSEL 5.4 17/18] nvme-pci: fix NULL req in completion handler Sasha Levin
2020-09-29 1:31 ` [PATCH AUTOSEL 5.4 18/18] nvme-fc: fail new connections to a deleted host or remote port Sasha Levin
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=20200929013105.2406634-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=xukai@nationalchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®