[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251217170035.mo4m4jxvzqvql7rc@hu-mojha-hyd.qualcomm.com>
Date: Wed, 17 Dec 2025 22:30:35 +0530
From: Mukesh Ojha <mukesh.ojha@....qualcomm.com>
To: Shivendra Pratap <shivendra.pratap@....qualcomm.com>
Cc: Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>,
Bartosz Golaszewski <brgl@...ev.pl>, linux-arm-msm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Unnathi Chalicheemala <unnathi.chalicheemala@....qualcomm.com>,
Bartosz Golaszewski <brgl@...nel.org>
Subject: Re: [PATCH v11 1/3] firmware: qcom_scm: Add API to get waitqueue IRQ
info
On Wed, Dec 17, 2025 at 08:04:19PM +0530, Shivendra Pratap wrote:
> From: Unnathi Chalicheemala <unnathi.chalicheemala@....qualcomm.com>
>
> Bootloader and firmware for SM8650 and older chipsets expect node
> name as "qcom_scm", in order to patch the wait queue IRQ information.
> However, DeviceTree uses node name "scm" and this mismatch prevents
> firmware from correctly identifying waitqueue IRQ information. Waitqueue
> IRQ is used for signaling between secure and non-secure worlds.
>
> To resolve this, introduce qcom_scm_get_waitq_irq() that'll get the
> hardware IRQ number to be used from firmware instead of relying on data
> provided by devicetree, thereby bypassing the DeviceTree node name
> mismatch.
>
> This hardware IRQ number is converted to a Linux IRQ number using newly
> qcom_scm_fill_irq_fwspec_params(). This Linux IRQ number is then
> supplied to the threaded_irq call.
>
> Reviewed-by: Bartosz Golaszewski <brgl@...nel.org>
> Signed-off-by: Unnathi Chalicheemala <unnathi.chalicheemala@....qualcomm.com>
> Signed-off-by: Shivendra Pratap <shivendra.pratap@....qualcomm.com>
Reviewed-by: Mukesh Ojha <mukesh.ojha@....qualcomm.com>
--
-Mukesh Ojha
Powered by blists - more mailing lists