From: Mark Rutland <mark.rutland@arm.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
Cc: marc.zyngier@arm.com, will.deacon@arm.com,
linux-arm-kernel@lists.infradead.org, linuxarm@huawei.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
john.garry@huawei.com, guohanjun@huawei.com
Subject: Re: [RFC 4/4] irqchip, gicv3-its: Add HiSilicon acpi based erratum data.
Date: Tue, 24 Jan 2017 14:00:20 +0000 [thread overview]
Message-ID: <20170124140019.GC7572@leverpostej> (raw)
In-Reply-To: <58875C45.50108@huawei.com>
On Tue, Jan 24, 2017 at 01:53:09PM +0000, Shameerali Kolothum Thodi wrote:
> This enables the acpi based workaround for HiSilicon erratum 161010801.
>
> Signed-off-by: shameer <shameerali.kolothum.thodi@huawei.com>
> ---
> drivers/irqchip/irq-gic-v3-its.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
> index 9fa12b7..d0f5099 100644
> --- a/drivers/irqchip/irq-gic-v3-its.c
> +++ b/drivers/irqchip/irq-gic-v3-its.c
> @@ -1868,7 +1868,10 @@ struct acpi_madt_its_quirks {
>
> /*Upadate as per the board OEM ID and TABLE ID*/
> struct acpi_madt_its_quirks acpi_its_quirks[] __initdata = {
> -
> +#ifdef CONFIG_HISILICON_ERRATUM_161010801
> + {"HISI ", "HIP06 ", 0, 0, "hisilicon,erratum-161010801"},
> + {"HISI ", "HIP07 ", 0, 0, "hisilicon,erratum-161010801"},
> +#endif
> };
Similarly to the arch timer patch, NAK to bodging ACPI match data to DT
property names.
Thanks,
Mark.
prev parent reply other threads:[~2017-01-24 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <588626A5.7090603@huawei.com>
2017-01-24 13:53 ` [RFC 4/4] irqchip, gicv3-its: Add HiSilicon acpi based erratum data Shameerali Kolothum Thodi
2017-01-24 14:00 ` Mark Rutland [this message]
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=20170124140019.GC7572@leverpostej \
--to=mark.rutland@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=guohanjun@huawei.com \
--cc=john.garry@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=marc.zyngier@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--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).