From: Mark Rutland <mark.rutland@arm.com>
To: daniel.lezcano@linaro.org
Cc: catalin.marinas@arm.com, dingtianhong@huawei.com,
mark.rutland@arm.com, will.deacon@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: [PATCH 0/7] arm64: arch_timer: work around Hisilicon erratum 161010101
Date: Tue, 31 Jan 2017 12:19:49 +0000 [thread overview]
Message-ID: <1485865196-12742-1-git-send-email-mark.rutland@arm.com> (raw)
Hi,
These patches are a rework of Ding's v9 series [1], addessing some issues with
code style and the commit logs.
Daniel, are you happy to take a look over these?
Catalin, Will, to minimise conflict with the Falkor erratum workaround, I've
added a preparatory patch that simply widens the silicon-errata kconfig column,
which should be queued before either patch.
Would you be happy with that patch going via both the arm64 tree and the
clocksource tree? We need it via the latter for the Hisilicon erratum 161010101
documentation, unless we split the documentation from the code.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2017-January/481089.html
Ding Tianhong (6):
arm64: arch_timer: add dt binding for hisilicon-161010101 erratum
arm64: arm_arch_timer: remove fsl-a008585 parameter
arm64: arch_timer: introduce generic errata handling infrastructure
arm64: arch_timer: work around Hisilicon erratum 161010101
arm64: arch_timer: document Hisilicon erratum 161010101
arm64: arch timer: Add timer erratum property for Hip05-d02 and
Hip06-d03
Mark Rutland (1):
arm64: docs: widen silicon-errata kconfig column
Documentation/admin-guide/kernel-parameters.txt | 9 --
Documentation/arm64/silicon-errata.txt | 44 +++---
.../devicetree/bindings/arm/arch_timer.txt | 6 +
arch/arm64/boot/dts/hisilicon/hip05.dtsi | 1 +
arch/arm64/boot/dts/hisilicon/hip06.dtsi | 1 +
arch/arm64/include/asm/arch_timer.h | 38 ++----
drivers/clocksource/Kconfig | 14 ++
drivers/clocksource/arm_arch_timer.c | 151 +++++++++++++++------
8 files changed, 168 insertions(+), 96 deletions(-)
--
1.9.1
next reply other threads:[~2017-01-31 12:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 12:19 Mark Rutland [this message]
2017-01-31 12:19 ` [PATCH 1/7] arm64: docs: widen silicon-errata kconfig column Mark Rutland
2017-01-31 12:19 ` [PATCH 2/7] arm64: arch_timer: add dt binding for hisilicon-161010101 erratum Mark Rutland
2017-01-31 12:19 ` [PATCH 3/7] arm64: arm_arch_timer: remove fsl-a008585 parameter Mark Rutland
2017-02-01 10:08 ` Daniel Lezcano
2017-01-31 12:19 ` [PATCH 4/7] arm64: arch_timer: introduce generic errata handling infrastructure Mark Rutland
2017-02-01 10:14 ` Daniel Lezcano
2017-02-01 10:14 ` Daniel Lezcano
2017-01-31 12:19 ` [PATCH 5/7] arm64: arch_timer: work around Hisilicon erratum 161010101 Mark Rutland
2017-02-02 18:39 ` Mark Rutland
2017-02-02 19:21 ` Daniel Lezcano
2017-01-31 12:19 ` [PATCH 6/7] arm64: arch_timer: document " Mark Rutland
2017-01-31 14:29 ` Will Deacon
2017-01-31 12:19 ` [PATCH 7/7] arm64: arch timer: Add timer erratum property for Hip05-d02 and Hip06-d03 Mark Rutland
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=1485865196-12742-1-git-send-email-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=dingtianhong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).