From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Sivansh Gupta <sivansh.gupta@oss.qualcomm.com>
Cc: Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
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: Wed, 4 Nov 2026 08:29:40 +0100 [thread overview]
Message-ID: <a56ef682-c28b-42f4-b23e-25bf7d7879c2@oss.qualcomm.com> (raw)
In-Reply-To: <179377342626.494575.14471451763190105361.b4-reply@b4>
On 11/4/26 7:23 AM, Sivansh Gupta wrote:
> On 2026-11-02 16:56 +0100, Konrad Dybcio wrote:
>> On 10/13/26 2:32 PM, Sivansh Gupta wrote:
>>> On 2026-09-30 11:55 +0200, Konrad Dybcio wrote:
>>>> On 9/28/26 7:29 AM, 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.
>>>>>
>>>>> 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);
>>>>
>>>> This still retains the writel() later on
>>>
>>> This is intentional, currently the existing mbox client(s) assume 32 bits
>>> writes instead of 64 bits, changing to 64 bits here would require all
>>> mbox clients to be updated to send 64 bits.
>>> Currently there is only 1 upstream client (arm_scmi).
>>>
>>>>> + u64 val = readq(cpucp->rx_base + APSS_CPUCP_RX_MBOX_CMD(i));
>>>>
>>>> This will alter the indices of the mailbox channels, but it's ""fine""
>>>> because it's always zero for the existing platforms..
>>>>
>>>> Konrad
>>>
>>> I am unsure what you mean here. The channel registers are spaced 8 bytes
>>> apart. In the old code, we used to read each channel's upper 32 bits
>>> (channel base + 4 bytes), in the new code we will be reading the entire
>>> 8 bytes.
>>> If this is not what you meant, please let me know!
>>
>> You're right, please remove the leftover define
>
> Hey, APSS_CPUCP_MBOX_CMD_OFF is intentionally used in
> qcom_cpucp_mbox_send_data as it is still using writel instead of writeq,
> as we discussed.
>
> Also, I have since learned that this patch has already been picked up!
>
> Cheers, Sivansh
Ok, all is well that ends well
Konrad
prev parent reply other threads:[~2026-11-04 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 5:29 Sivansh Gupta
2026-09-29 9:25 ` Sibi Sankar
2026-09-30 9:55 ` Konrad Dybcio
2026-10-13 12:32 ` Sivansh Gupta
2026-10-28 9:50 ` Sivansh Gupta
2026-11-02 15:56 ` Konrad Dybcio
2026-11-04 6:23 ` Sivansh Gupta
2026-11-04 7:29 ` Konrad Dybcio [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=a56ef682-c28b-42f4-b23e-25bf7d7879c2@oss.qualcomm.com \
--to=konrad.dybcio@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=sibi.sankar@oss.qualcomm.com \
--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®