From: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
To: Sivansh Gupta <sivansh.gupta@oss.qualcomm.com>
Cc: Jassi Brar <jassisinghbrar@gmail.com>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mailbox: qcom-cpucp: read mbox hardware register using readq()
Date: Tue, 29 Sep 2026 14:55:17 +0530 [thread overview]
Message-ID: <138bbe2f-2871-4541-80c9-c7867e1b1481@oss.qualcomm.com> (raw)
In-Reply-To: <20260928052940.688105-1-sivansh.gupta@oss.qualcomm.com>
On 9/28/26 10:59, Sivansh Gupta wrote:
> Mailbox hardware registers are 64 bit wide, but the interrupt handler
> currently reads only 32 bits with readl() at offset 0x4 (upper 32
> bits). This returns an incorrect value, while reading using readq()
> returns the expected value.
>
> Use readq() to access the 64 bit register and pass the expected value
> to the mailbox client.
Mailbox hardware registers are 64 bit wide, but the interrupt handler
currently reads only 32 bits with readl() at offset 0x4 (upper 32
bits). This results in a masked out value being passed on to the mailbox
clients.
Fix this by using readq instead and pass on the correct value to the
mailbox clients.
^^ seems more appropriate with these minor nits fixed.
Reviewed-by: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
>
> Fixes: 0e2a9a03106c ("mailbox: Add support for QTI CPUCP mailbox controller")
> Signed-off-by: Sivansh Gupta <sivansh.gupta@oss.qualcomm.com>
> ---
> v3:
> - Removed references to an out of tree driver to focus on the incorrect
> value returned by readl()
> https://lore.kernel.org/all/93ce8588-7500-45da-9b9a-424c202590cf@oss.qualcomm.com/#t
>
> v2:
> - Expanded the commit message to explain why this change is required.
>
> drivers/mailbox/qcom-cpucp-mbox.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/mailbox/qcom-cpucp-mbox.c b/drivers/mailbox/qcom-cpucp-mbox.c
> index 862e45e8fbd5..0b584d9aad6c 100644
> --- a/drivers/mailbox/qcom-cpucp-mbox.c
> +++ b/drivers/mailbox/qcom-cpucp-mbox.c
> @@ -61,7 +61,7 @@ static irqreturn_t qcom_cpucp_mbox_irq_fn(int irq, void *data)
> status = readq(cpucp->rx_base + APSS_CPUCP_RX_MBOX_STAT);
>
> for_each_set_bit(i, (unsigned long *)&status, cpucp->mbox.num_chans) {
> - u32 val = readl(cpucp->rx_base + APSS_CPUCP_RX_MBOX_CMD(i) + APSS_CPUCP_MBOX_CMD_OFF);
> + u64 val = readq(cpucp->rx_base + APSS_CPUCP_RX_MBOX_CMD(i));
> struct mbox_chan *chan = &cpucp->chans[i];
> unsigned long flags;
>
next prev parent reply other threads:[~2026-09-29 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 5:29 Sivansh Gupta
2026-09-29 9:25 ` Sibi Sankar [this message]
2026-09-30 9:55 ` Konrad Dybcio
2026-10-13 12:32 ` Sivansh Gupta
2026-10-28 9:50 ` Sivansh Gupta
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=138bbe2f-2871-4541-80c9-c7867e1b1481@oss.qualcomm.com \
--to=sibi.sankar@oss.qualcomm.com \
--cc=jassisinghbrar@gmail.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sivansh.gupta@oss.qualcomm.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®