From: Cong Zhang <quic_congzhan@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <quic_pkondeti@quicinc.com>, <quic_aiquny@quicinc.com>,
<kernel@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: Correct IRQ number of EL2 non-secure physical timer
Date: Thu, 5 Dec 2024 18:24:04 +0800 [thread overview]
Message-ID: <dadfe8f3-8592-4884-8206-a37cb856143a@quicinc.com> (raw)
In-Reply-To: <42e3293d-a7dd-4b39-8e36-45b1f31f8b01@kernel.org>
On 11/27/2024 5:37 PM, Krzysztof Kozlowski wrote:
> On 27/11/2024 10:32, Cong Zhang wrote:
>> The INTID of EL2 non-secure physical timer is 26. In linux, the IRQ
>> number has a fixed 16 offset for PPIs. Therefore, the linux IRQ number
>> of EL2 non-secure physical timer should be 10 (26 - 16).
>>
>> Signed-off-by: Cong Zhang <quic_congzhan@quicinc.com>
>> ---
>> The EL2 non-secure physical timer is utilized during kernel bootup in
>> EL2 mode with KVM enabled. This patch has been verified on the QCS8300
>> platform with KVM enabled. Given that the dependency patch has already
>> been reviewed, I am uncertain whether it is preferable to submit this
>> fix as a new patch or to combine it with the dependency patch. I would
>> appreciate your suggestions on this patch.
>> ---
>> arch/arm64/boot/dts/qcom/qcs8300.dtsi | 2 +-
> This was not merged. Do not post fixes to things which are still patches
> on mailing list.
>
> Best regards,
> Krzysztof
Thanks for your suggestion. The patches for qcs8300 are update
https://lore.kernel.org/all/20241128-qcs8300_initial_dtsi-v3-3-26aa8a164914@quicinc.com/.
I will update this patch to fix sdx75 platform which is already merged.
--
Thanks,
Cong Zhang
prev parent reply other threads:[~2024-12-05 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 9:32 Cong Zhang
2024-11-27 9:37 ` Krzysztof Kozlowski
2024-12-05 10:24 ` Cong Zhang [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=dadfe8f3-8592-4884-8206-a37cb856143a@quicinc.com \
--to=quic_congzhan@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_aiquny@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=robh@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
all inboxes | Powered by JetHome®