linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2/7] arm64: arch_timer: add dt binding for hisilicon-161010101 erratum
Date: Tue, 31 Jan 2017 12:19:51 +0000	[thread overview]
Message-ID: <1485865196-12742-3-git-send-email-mark.rutland@arm.com> (raw)
In-Reply-To: <1485865196-12742-1-git-send-email-mark.rutland@arm.com>

From: Ding Tianhong <dingtianhong@huawei.com>

This erratum describes a bug in logic outside the core, so MIDR can't be
used to identify its presence, and reading an SoC-specific revision
register from common arch timer code would be awkward.  So, describe it
in the device tree.

Signed-off-by: Ding Tianhong <dingtianhong@huawei.com>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
---
 Documentation/devicetree/bindings/arm/arch_timer.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/devicetree/bindings/arm/arch_timer.txt b/Documentation/devicetree/bindings/arm/arch_timer.txt
index ad440a2..e926aea 100644
--- a/Documentation/devicetree/bindings/arm/arch_timer.txt
+++ b/Documentation/devicetree/bindings/arm/arch_timer.txt
@@ -31,6 +31,12 @@ to deliver its interrupts via SPIs.
   This also affects writes to the tval register, due to the implicit
   counter read.
 
+- hisilicon,erratum-161010101 : A boolean property. Indicates the
+  presence of Hisilicon erratum 161010101, which says that reading the
+  counters is unreliable in some cases, and reads may return a value 32
+  beyond the correct value. This also affects writes to the tval
+  registers, due to the implicit counter read.
+
 ** Optional properties:
 
 - arm,cpu-registers-not-fw-configured : Firmware does not initialize
-- 
1.9.1

  parent reply	other threads:[~2017-01-31 12:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 12:19 [PATCH 0/7] arm64: arch_timer: work around Hisilicon erratum 161010101 Mark Rutland
2017-01-31 12:19 ` [PATCH 1/7] arm64: docs: widen silicon-errata kconfig column Mark Rutland
2017-01-31 12:19 ` Mark Rutland [this message]
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-3-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).