From: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Aniruddha Banerjee
<aniruddhab-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Marc Zyngier <marc.zyngier-5wv7dgnIgG8@public.gmane.org>
Cc: "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Alexander Van Brunt
<avanbrunt-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 1/1] arm64: tegra: fix PPI interrupt flag
Date: Mon, 3 Apr 2017 13:55:23 +0100 [thread overview]
Message-ID: <6c64238f-a462-9e05-2f04-e989c16553c6@nvidia.com> (raw)
In-Reply-To: <7fad40fbcaa94c1ea46328e78b46443b-7W72rfoJkVlxWE4FnwvcdlaTQe2KTcn/@public.gmane.org>
Adding Marc ...
On 03/04/17 12:19, Aniruddha Banerjee wrote:
> The interrupt flag for PPI should not be set to any value, since the
> register is read-only. Fix the flags for the PPI interrupts to
> IRQ_TYPE_NONE, so that there is no write to the read-only register.
If the below matches the h/w default, does this really cause a problem?
Note, we will not attempt to write the type if it matches the current
programmed type.
I had thought that the in DT file, the type for the PPI should align
with the h/w default in the case where it cannot be written. However, I
guess this is not explicitly stated anywhere I have found, but at the
same time the binding doc for the arm,gic.txt does not list
"IRQ_TYPE_NONE" as an option.
Marc, what are your thoughts?
> Signed-off-by: Aniruddha Banerjee <aniruddhab-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> ---
> arch/arm64/boot/dts/nvidia/tegra132.dtsi | 8 ++++----
> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 8 ++++----
> arch/arm64/boot/dts/nvidia/tegra210.dtsi | 8 ++++----
> 3 files changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/nvidia/tegra132.dtsi b/arch/arm64/boot/dts/nvidia/tegra132.dtsi
> index 3f3a46a4bd01..219fb3c6a273 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra132.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra132.dtsi
> @@ -1093,13 +1093,13 @@
> timer {
> compatible = "arm,armv7-timer";
> interrupts = <GIC_PPI 13
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>,
> <GIC_PPI 14
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>,
> <GIC_PPI 11
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>,
> <GIC_PPI 10
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>;
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>;
> interrupt-parent = <&gic>;
> };
> };
> diff --git a/arch/arm64/boot/dts/nvidia/tegra186.dtsi b/arch/arm64/boot/dts/nvidia/tegra186.dtsi
> index 62fa85ae0271..e602299f7694 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra186.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra186.dtsi
> @@ -390,13 +390,13 @@
> timer {
> compatible = "arm,armv8-timer";
> interrupts = <GIC_PPI 13
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>,
> <GIC_PPI 14
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>,
> <GIC_PPI 11
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>,
> <GIC_PPI 10
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>;
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>;
> interrupt-parent = <&gic>;
> };
> };
> diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
> index 2f832df29da8..6f3060b40a40 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
> @@ -1214,13 +1214,13 @@
> timer {
> compatible = "arm,armv8-timer";
> interrupts = <GIC_PPI 13
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>,
> <GIC_PPI 14
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>,
> <GIC_PPI 11
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>,
> <GIC_PPI 10
> - (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>;
> + (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_NONE)>;
> interrupt-parent = <&gic>;
> };
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2017-04-03 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 11:19 [PATCH 1/1] arm64: tegra: fix PPI interrupt flag Aniruddha Banerjee
[not found] ` <7fad40fbcaa94c1ea46328e78b46443b-7W72rfoJkVlxWE4FnwvcdlaTQe2KTcn/@public.gmane.org>
2017-04-03 12:55 ` Jon Hunter [this message]
[not found] ` <6c64238f-a462-9e05-2f04-e989c16553c6-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-04-03 13:11 ` Marc Zyngier
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=6c64238f-a462-9e05-2f04-e989c16553c6@nvidia.com \
--to=jonathanh-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=aniruddhab-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=avanbrunt-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marc.zyngier-5wv7dgnIgG8@public.gmane.org \
--cc=treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox