[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAMRc=Md=QY-HdA0Tdpd3rh1pma8cCtdde0mv91TtG0ML8Ej_pQ@mail.gmail.com>
Date: Tue, 4 Mar 2025 14:53:34 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Unnathi Chalicheemala <unnathi.chalicheemala@....qualcomm.com>
Cc: Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konradybcio@...nel.org>,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@....qualcomm.com, Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Prasad Sodagudi <prasad.sodagudi@....qualcomm.com>,
Satya Durga Srinivasu Prabhala <quic_satyap@...cinc.com>, Trilok Soni <quic_tsoni@...cinc.com>
Subject: Re: [PATCH v5 1/2] firmware: qcom_scm: Add API to get waitqueue IRQ info
On Fri, Feb 28, 2025 at 6:40 AM Unnathi Chalicheemala
<unnathi.chalicheemala@....qualcomm.com> wrote:
>
> 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
> defined fill_irq_fwspec_params(). This Linux IRQ number is then supplied
> to the threaded_irq call.
>
> Signed-off-by: Unnathi Chalicheemala <unnathi.chalicheemala@....qualcomm.com>
> ---
Reviewed-by: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Powered by blists - more mailing lists