From: dingtianhong@huawei.com (Ding Tianhong)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/4] arm64: arch_timer: Add device tree binding for A-008585 erratum
Date: Thu, 8 Sep 2016 19:46:34 +0800 [thread overview]
Message-ID: <57D14F9A.2050007@huawei.com> (raw)
In-Reply-To: <e69db8b1-5fe2-ed0a-b073-de3efdd854d2@suse.com>
Ping
On 2016/8/25 19:04, Matthias Brugger wrote:
> Hi all,
>
> On 07/07/16 09:46, Scott Wood wrote:
>> 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: Scott Wood <oss@buserror.net>
>> Acked-by: Rob Herring <robh@kernel.org>
>> ---
>
> As of today I wasn't able to find this series in linux-next. Was this series somehow forgotten? Scott maybe you can resend the patches adding the clocksource maintainer.
>
> Regards,
> Matthias
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Ding Tianhong <dingtianhong@huawei.com>
To: Matthias Brugger <mbrugger@suse.com>,
Scott Wood <oss@buserror.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>
Cc: devicetree@vger.kernel.org, stuart.yoder@nxp.com,
linux-arm-kernel@lists.infradead.org,
Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH v4 1/4] arm64: arch_timer: Add device tree binding for A-008585 erratum
Date: Thu, 8 Sep 2016 19:46:34 +0800 [thread overview]
Message-ID: <57D14F9A.2050007@huawei.com> (raw)
In-Reply-To: <e69db8b1-5fe2-ed0a-b073-de3efdd854d2@suse.com>
Ping
On 2016/8/25 19:04, Matthias Brugger wrote:
> Hi all,
>
> On 07/07/16 09:46, Scott Wood wrote:
>> 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: Scott Wood <oss@buserror.net>
>> Acked-by: Rob Herring <robh@kernel.org>
>> ---
>
> As of today I wasn't able to find this series in linux-next. Was this series somehow forgotten? Scott maybe you can resend the patches adding the clocksource maintainer.
>
> Regards,
> Matthias
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
>
next prev parent reply other threads:[~2016-09-08 11:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 7:46 [PATCH v4 1/4] arm64: arch_timer: Add device tree binding for A-008585 erratum Scott Wood
2016-07-07 7:46 ` Scott Wood
2016-07-07 7:46 ` [PATCH v4 2/4] arm64: dts: Add timer erratum property for LS2080A and LS1043A Scott Wood
2016-07-07 7:46 ` Scott Wood
2016-07-07 7:46 ` [PATCH v4 3/4] arm64: arch_timer: Work around QorIQ Erratum A-008585 Scott Wood
2016-07-07 7:46 ` Scott Wood
2016-08-26 12:40 ` Marc Zyngier
2016-08-26 12:40 ` Marc Zyngier
2016-09-09 1:08 ` Scott Wood
2016-09-09 1:08 ` Scott Wood
2016-09-09 6:53 ` Marc Zyngier
2016-09-09 6:53 ` Marc Zyngier
2016-09-09 5:20 ` Ding Tianhong
2016-09-09 5:20 ` Ding Tianhong
2016-09-09 7:06 ` Marc Zyngier
2016-09-09 7:06 ` Marc Zyngier
2016-07-07 7:46 ` [PATCH v4 4/4] arm/arm64: arch_timer: Use archdata to indicate vdso suitability Scott Wood
2016-07-07 7:46 ` Scott Wood
2016-07-07 15:18 ` Will Deacon
2016-07-07 15:18 ` Will Deacon
2016-08-25 11:04 ` [PATCH v4 1/4] arm64: arch_timer: Add device tree binding for A-008585 erratum Matthias Brugger
2016-08-25 11:04 ` Matthias Brugger
2016-09-08 11:46 ` Ding Tianhong [this message]
2016-09-08 11:46 ` Ding Tianhong
2016-09-08 12:07 ` Marc Zyngier
2016-09-08 12:07 ` Marc Zyngier
2016-09-08 12:31 ` Ding Tianhong
2016-09-08 12:31 ` Ding Tianhong
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=57D14F9A.2050007@huawei.com \
--to=dingtianhong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.