From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Arnd Bergmann <arnd@kernel.org>,
Jassi Brar <jassisinghbrar@gmail.com>,
Sibi Sankar <quic_sibis@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mailbox: qcom-cpucp: fix 64BIT dependency
Date: Fri, 19 Jul 2024 12:04:16 +0200 [thread overview]
Message-ID: <a3381f68-35e6-42b2-9628-e0da44374f53@linaro.org> (raw)
In-Reply-To: <20240719100247.4012087-1-arnd@kernel.org>
On 19.07.2024 12:02 PM, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> This newly added driver fails compile testing on 32-bit architectures
> because it relies on 64-bit MMIO register access:
>
> drivers/mailbox/qcom-cpucp-mbox.c: In function 'qcom_cpucp_mbox_irq_fn':
> drivers/mailbox/qcom-cpucp-mbox.c:54:18: error: implicit declaration of function 'readq'; did you mean 'readb'? [-Wimplicit-function-declaration]
> 54 | status = readq(cpucp->rx_base + APSS_CPUCP_RX_MBOX_STAT);
> | ^~~~~
> | readb
> drivers/mailbox/qcom-cpucp-mbox.c:65:17: error: implicit declaration of function 'writeq'; did you mean 'writeb'? [-Wimplicit-function-declaration]
> 65 | writeq(BIT(i), cpucp->rx_base + APSS_CPUCP_RX_MBOX_CLEAR);
> | ^~~~~~
> | writeb
>
> Change the Kconfig dependency to disallow that configuration as well.
>
> Fixes: 0e2a9a03106c ("mailbox: Add support for QTI CPUCP mailbox controller")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
Thanks
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Konrad
next prev parent reply other threads:[~2024-07-19 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 10:02 [PATCH] mailbox: qcom-cpucp: fix 64BIT dependency Arnd Bergmann
2024-07-19 10:04 ` Konrad Dybcio [this message]
2024-07-25 9:25 ` Sibi Sankar
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=a3381f68-35e6-42b2-9628-e0da44374f53@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_sibis@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.