From: Sai Prakash Ranjan <quic_saipraka@quicinc.com>
To: Parikshit Pareek <quic_ppareek@quicinc.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Rajendra Nayak <quic_rjendra@quicinc.com>,
Prasanna Kumar <quic_kprasan@quicinc.com>,
<linux-arm-msm@vger.kernel.org>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
Johan Hovold <johan@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: dts: qcom: sc8280xp: fix apps_smmu irq
Date: Fri, 15 Jul 2022 13:38:58 +0530 [thread overview]
Message-ID: <2faae901-0539-2467-5984-fa476a94968c@quicinc.com> (raw)
In-Reply-To: <27007c45-1dbb-2c35-b1a8-eb2b2a6c9512@quicinc.com>
On 7/14/2022 12:47 PM, Sai Prakash Ranjan wrote:
> Hi Parikshit,
>
> On 7/12/2022 7:30 PM, Parikshit Pareek wrote:
>> Wrong values have been introduced for interrupts property. Fix those
>> ones, and correct the mapping of context banks to irq number.
>>
>> Fixes: 152d1faf1e2f ("arm64: dts: qcom: add SC8280XP platform")
>> Signed-off-by: Parikshit Pareek <quic_ppareek@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/sc8280xp.dtsi | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
>> index 7945cbb57bb4..1276a833251e 100644
>> --- a/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sc8280xp.dtsi
>> @@ -1580,7 +1580,6 @@
>> <GIC_SPI 412 IRQ_TYPE_LEVEL_HIGH>,
>> <GIC_SPI 421 IRQ_TYPE_LEVEL_HIGH>,
>> <GIC_SPI 706 IRQ_TYPE_LEVEL_HIGH>,
>> - <GIC_SPI 424 IRQ_TYPE_LEVEL_HIGH>,
>> <GIC_SPI 423 IRQ_TYPE_LEVEL_HIGH>,
>> <GIC_SPI 424 IRQ_TYPE_LEVEL_HIGH>,
>> <GIC_SPI 425 IRQ_TYPE_LEVEL_HIGH>,
>> @@ -1591,6 +1590,7 @@
>> <GIC_SPI 693 IRQ_TYPE_LEVEL_HIGH>,
>> <GIC_SPI 694 IRQ_TYPE_LEVEL_HIGH>,
>> <GIC_SPI 695 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 696 IRQ_TYPE_LEVEL_HIGH>,
>> <GIC_SPI 410 IRQ_TYPE_LEVEL_HIGH>,
>> <GIC_SPI 411 IRQ_TYPE_LEVEL_HIGH>,
>> <GIC_SPI 420 IRQ_TYPE_LEVEL_HIGH>,
>
> Cross checking with the IP doc, 696 is not the only one missing, couple of other interrupts are also missing, below is the list.
>
> Interrupt 689 and 706 are not present in the IP doc, remove it.
> Interrupts 696, 697, 716, 913 are missing, I see this patch adds 696, add 697 as well.
> Interrupt 890 is not a context interrupt, remove it.
>
>
Checking offline with Parikshit, looks like adding all these entries results in interrupt selftest failures.
So for now, we can just have the original patch merged till these failures are debugged further with internal teams.
Thanks,
Sai
prev parent reply other threads:[~2022-07-15 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220712140009.20765-1-quic_ppareek@quicinc.com>
2022-07-14 7:17 ` Sai Prakash Ranjan
2022-07-15 8:08 ` Sai Prakash Ranjan [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=2faae901-0539-2467-5984-fa476a94968c@quicinc.com \
--to=quic_saipraka@quicinc.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=johan@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_kprasan@quicinc.com \
--cc=quic_ppareek@quicinc.com \
--cc=quic_rjendra@quicinc.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
all inboxes | Powered by JetHome®