From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: rockchip: fix PPI misconfiguration on Cortex-A9 socs
Date: Wed, 22 Mar 2017 13:01:30 +0100 [thread overview]
Message-ID: <1510641.DEbmyROnA9@phil> (raw)
In-Reply-To: <20170321231428.23802-1-heiko@sntech.de>
Am Mittwoch, 22. M?rz 2017, 00:14:28 CET schrieb Heiko Stuebner:
> According to [0] pointed out by Marc Zyngier in a report about a
> similar error message, PPIs 11 and 13 are edge triggered on
> Cortex-A9 socs including the rk3066 and rk3188 which currently
> mark them as level triggered.
>
> Until some time ago the gic did not care but commit 992345a58e0c
> ("irqchip/gic: WARN if setting the interrupt type for a PPI fails")
> introduced a warning for that case.
>
> Fix the warning on these socs by describing the interrupts correctly
> and also using the binding constants for easier reading in the future.
>
> [0] http://infocenter.arm.com/help/topic/com.arm.doc.ddi0407f/CCHEIGIC.html
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
applied for 4.12
prev parent reply other threads:[~2017-03-22 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 23:14 [PATCH] ARM: dts: rockchip: fix PPI misconfiguration on Cortex-A9 socs Heiko Stuebner
2017-03-22 12:01 ` Heiko Stuebner [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=1510641.DEbmyROnA9@phil \
--to=heiko@sntech.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox