From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Frank Rowand <frowand.list@gmail.com>
Cc: "Ivan T. Ivanov" <iivanov@mm-sol.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 1/3] ARM: dts: qcom: Add SPMI PMIC Arbiter nodes for APQ8084 and MSM8974
Date: Fri, 31 Aug 2018 16:01:25 -0700 [thread overview]
Message-ID: <20180831230125.GU2523@minitux> (raw)
In-Reply-To: <550311ad-8f93-3e80-9706-1321482b8c19@gmail.com>
On Fri 31 Aug 15:46 PDT 2018, Frank Rowand wrote:
> > + spmi_bus: spmi@fc4cf000 {
> > + compatible = "qcom,spmi-pmic-arb";
> > + reg-names = "core", "intr", "cnfg";
> > + reg = <0xfc4cf000 0x1000>,
> > + <0xfc4cb000 0x1000>,
> > + <0xfc4ca000 0x1000>;
> > + interrupt-names = "periph_irq";
>
> > + interrupts = <0 190 0>;
>
> The final value in this interrupts property means IRQ_TYPE_NONE.
>
> A WARN_ON() was added early this year to complain about use of
> IRQ_TYPE_NONE: 83a86fbb5b56 "irqchip/gic: Loudly complain about
> the use of IRQ_TYPE_NONE", resulting in many warnings spewing
> forth when I boot an APQ8074 Dragonboard. I am trying to
> determine whether the warning is overly aggressive, or whether
> the IRQ TYPE is incorrectly specified for the spmi node.
>
> The interrupt-parent for the spmi node is intc: interrupt-controller@f9000000,
> which has compatible = "qcom,msm-qgic2". I do not know the architecture
> or implementation of this interrupt controller. Is an IRQ_TYPE_NONE
> valid in this case, or should a specific type be provided?
>
No, IRQ_TYPE_NONE isn't valid and the WARN_ON() is reasonable.
Please change it to IRQ_TYPE_LEVEL_HIGH. And while you're at it, replace
the first 0 with GIC_SPI.
If you have more of these warnings you can most likely look at e.g.
msm8916 (arm64) to find the right flags.
Regards,
Bjorn
next prev parent reply other threads:[~2018-08-31 23:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 12:17 [PATCH 0/3] Add initial DT support for Qualcomm SPMI PMIC devices Ivan T. Ivanov
[not found] ` <1422965880-11047-1-git-send-email-iivanov-NEYub+7Iv8PQT0dZR+AlfA@public.gmane.org>
2015-02-03 12:17 ` [PATCH 1/3] ARM: dts: qcom: Add SPMI PMIC Arbiter nodes for APQ8084 and MSM8974 Ivan T. Ivanov
2018-08-31 22:46 ` Frank Rowand
2018-08-31 22:50 ` Frank Rowand
2018-08-31 23:01 ` Bjorn Andersson [this message]
2018-09-01 0:05 ` Frank Rowand
2015-02-03 20:38 ` [PATCH 0/3] Add initial DT support for Qualcomm SPMI PMIC devices Bjorn Andersson
2015-02-10 7:17 ` Ivan T. Ivanov
2015-02-03 12:17 ` [PATCH 2/3] ARM: dts: qcom: Add 8x74 chipset SPMI PMIC's nodes Ivan T. Ivanov
2015-02-03 12:18 ` [PATCH 3/3] ARM: dts: qcom: Add APQ8084 " Ivan T. Ivanov
2015-02-10 21:58 ` [PATCH 0/3] Add initial DT support for Qualcomm SPMI PMIC devices Andy Gross
2015-02-20 0:49 ` Stephen Boyd
[not found] ` <54E6848C.1090405-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-02-26 16:25 ` Ivan T. Ivanov
2015-03-03 8:19 ` Stephen Boyd
2015-03-04 10:31 ` Ivan T. Ivanov
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=20180831230125.GU2523@minitux \
--to=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=galak@codeaurora.org \
--cc=iivanov@mm-sol.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).