From: Florian Fainelli <f.fainelli@gmail.com>
To: Jon Mason <jon.mason@broadcom.com>,
Hauke Mehrtens <hauke@hauke-m.de>,
zajec5@gmail.com
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/3] ARM: dts: BCM5301X: Correct GIC_PPI interrupt flags
Date: Sun, 5 Mar 2017 17:11:32 -0800 [thread overview]
Message-ID: <01eb66cb-0359-2f58-511b-acaaf62be828@gmail.com> (raw)
In-Reply-To: <1488500494-20622-2-git-send-email-jon.mason@broadcom.com>
On 03/02/2017 04:21 PM, Jon Mason wrote:
> GIC_PPI flags were misconfigured for the timers, resulting in errors
> like:
> [ 0.000000] GIC: PPI11 is secure or misconfigured
>
> Changing them to being edge triggered corrects the issue
>
> Suggested-by: Rafał Miłecki <rafal@milecki.pl>
> Signed-off-by: Jon Mason <jon.mason@broadcom.com>
> Fixes: d27509f1 ("ARM: BCM5301X: add dts files for BCM4708 SoC")
Applied, thanks!
--
Florian
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] ARM: dts: BCM5301X: Correct GIC_PPI interrupt flags
Date: Sun, 5 Mar 2017 17:11:32 -0800 [thread overview]
Message-ID: <01eb66cb-0359-2f58-511b-acaaf62be828@gmail.com> (raw)
In-Reply-To: <1488500494-20622-2-git-send-email-jon.mason@broadcom.com>
On 03/02/2017 04:21 PM, Jon Mason wrote:
> GIC_PPI flags were misconfigured for the timers, resulting in errors
> like:
> [ 0.000000] GIC: PPI11 is secure or misconfigured
>
> Changing them to being edge triggered corrects the issue
>
> Suggested-by: Rafa? Mi?ecki <rafal@milecki.pl>
> Signed-off-by: Jon Mason <jon.mason@broadcom.com>
> Fixes: d27509f1 ("ARM: BCM5301X: add dts files for BCM4708 SoC")
Applied, thanks!
--
Florian
next prev parent reply other threads:[~2017-03-06 1:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 0:21 [PATCH v2 0/3] ARM: dts: BCM5301X: GIC_PPI bug, TWD WD and i2c Support Jon Mason
2017-03-03 0:21 ` Jon Mason
2017-03-03 0:21 ` Jon Mason
2017-03-03 0:21 ` [PATCH v2 1/3] ARM: dts: BCM5301X: Correct GIC_PPI interrupt flags Jon Mason
2017-03-03 0:21 ` Jon Mason
2017-03-03 0:21 ` Jon Mason
2017-03-06 1:11 ` Florian Fainelli [this message]
2017-03-06 1:11 ` Florian Fainelli
2017-03-03 0:21 ` [PATCH v2 2/3] ARM: dts: bcm5301x: Add TWD WD Support to DT Jon Mason
2017-03-03 0:21 ` Jon Mason
2017-03-03 0:21 ` Jon Mason
2017-03-03 0:21 ` [PATCH v2 3/3] ARM: dts: bcm5301x: Add I2C support to the DT Jon Mason
2017-03-03 0:21 ` Jon Mason
2017-03-03 0:21 ` Jon Mason
2017-03-06 1:13 ` Florian Fainelli
2017-03-06 1:13 ` Florian Fainelli
2017-03-06 1:13 ` Florian Fainelli
2017-03-06 15:12 ` Jon Mason
2017-03-06 15:12 ` Jon Mason
2017-03-06 15:12 ` Jon Mason
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=01eb66cb-0359-2f58-511b-acaaf62be828@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=jon.mason@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=zajec5@gmail.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 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.