public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v9 0/4] arm64: arch_timer: Add workaround for hisilicon-161010101 erratum
Date: Mon, 23 Jan 2017 10:39:58 +0000	[thread overview]
Message-ID: <20170123103958.GC4622@arm.com> (raw)
In-Reply-To: <20170120150428.GC22152@leverpostej>

On Fri, Jan 20, 2017 at 03:04:28PM +0000, Mark Rutland wrote:
> On Thu, Jan 19, 2017 at 09:35:12PM +0800, Ding Tianhong wrote:
> > Ding Tianhong (4):
> >   arm64: arch_timer: Add device tree binding for hisilicon-161010101
> >     erratum
> >   arm64: arch_timer: Introduce a generic erratum handing mechanism for
> >     fsl-a008585
> >   arm64: arch_timer: Work around Erratum Hisilicon-161010101
> >   arm64: arch timer: Add timer erratum property for Hip05-d02 and
> >     Hip06-d03
> > 
> >  Documentation/admin-guide/kernel-parameters.txt    |   9 --
> >  Documentation/arm64/silicon-errata.txt             |  43 +++---
> >  .../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                        |  18 +++
> >  drivers/clocksource/arm_arch_timer.c               | 150 +++++++++++++++------
> >  8 files changed, 171 insertions(+), 95 deletions(-)
> 
> I've picked these up (with a few local cleanups), given that some local
> testing, and pushed the result to a branch [1] on my git repo.
> 
> There are likely to be clashes with the arm64 tree (e.g. for
> silicon-errata.txt), and we're also likely to have more arch timer
> updates shortly for the GTDT stuff, so I think the best bet is for both
> arm64 and the clocksource tree to pull that branch for v4.11.
> 
> Alternatively, we could take this all through the arm64 tree, if the
> clocksource maintainers are happy with that.

Fine by me, but I'd need at least Daniel's ack before taking these.

Will

  parent reply	other threads:[~2017-01-23 10:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 13:35 [PATCH v9 0/4] arm64: arch_timer: Add workaround for hisilicon-161010101 erratum Ding Tianhong
2017-01-19 13:35 ` [PATCH v9 1/4] arm64: arch_timer: Add device tree binding " Ding Tianhong
2017-01-19 13:35 ` [PATCH v9 2/4] arm64: arch_timer: Introduce a generic erratum handing mechanism for fsl-a008585 Ding Tianhong
2017-01-30 21:59   ` Daniel Lezcano
2017-01-19 13:35 ` [PATCH v9 3/4] arm64: arch_timer: Work around Erratum Hisilicon-161010101 Ding Tianhong
2017-01-30 23:17   ` Daniel Lezcano
2017-01-19 13:35 ` [PATCH v9 4/4] arm64: arch timer: Add timer erratum property for Hip05-d02 and Hip06-d03 Ding Tianhong
2017-01-19 13:49 ` [PATCH v9 0/4] arm64: arch_timer: Add workaround for hisilicon-161010101 erratum Marc Zyngier
2017-01-20  1:22   ` Ding Tianhong
2017-01-20 15:04 ` Mark Rutland
2017-01-22  7:59   ` Hanjun Guo
2017-01-23 10:31     ` Mark Rutland
2017-01-23  7:36   ` Ding Tianhong
2017-01-23  8:43     ` Marc Zyngier
2017-01-23 10:39   ` Will Deacon [this message]
2017-01-23 22:40     ` Daniel Lezcano
2017-01-24 15:08 ` Daniel Lezcano
2017-01-24 15:27   ` Marc Zyngier
2017-01-24 16:35     ` Daniel Lezcano
2017-01-30 15:52       ` Mark Rutland
2017-01-30 21:54         ` Daniel Lezcano
2017-01-31 12:14           ` 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=20170123103958.GC4622@arm.com \
    --to=will.deacon@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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