From: Alexander Wilhelm <alexander.wilhelm@westermo.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] soc: qcom: fix endianness for QMI header
Date: Fri, 23 May 2025 07:57:50 +0200 [thread overview]
Message-ID: <aDAOXo/ujOcefs04@FUE-ALEWI-WINX> (raw)
In-Reply-To: <vf7fb7jxxwy25wzow4pbzvh26xqd7hkx4edqmcts2tzoyrnxqs@u3lev7ergjb2>
Am Thu, May 22, 2025 at 10:09:13PM +0300 schrieb Dmitry Baryshkov:
> On Thu, May 22, 2025 at 04:35:30PM +0200, Alexander Wilhelm wrote:
> > The members of QMI header have to be swapped on big endian platforms. Use
> > __le16 types instead of u16 ones.
> >
> > Signed-off-by: Alexander Wilhelm <alexander.wilhelm@westermo.com>
> > ---
> > drivers/soc/qcom/qmi_encdec.c | 6 +++---
> > drivers/soc/qcom/qmi_interface.c | 6 +++---
> > include/linux/soc/qcom/qmi.h | 6 +++---
> > 3 files changed, 9 insertions(+), 9 deletions(-)
>
> Just out of curiosity, is there a usecase for running QMI helpers on BE
> platforms?
I'm not familiar with modems, but the wireless drivers ath11k and ath12k use the
QMI helpers while transferring the firmware and boardfile to the module. As an
example here is the log by probing ath12k device on big endian without a patch:
ath12k_pci 0001:01:00.0: BAR 0: assigned [mem 0xc00000000-0xc001fffff 64bit]
ath12k_pci 0001:01:00.0: MSI vectors: 1
ath12k_pci 0001:01:00.0: Hardware name: qcn9274 hw2.0
ath12k_pci 0001:01:00.0: FW Ind register request failed, result: 256, err: 512
ath12k_pci 0001:01:00.0: qmi failed to send FW indication QMI:-22
Similar behavior is seen with ath11k drivers.
Best regards
Alexander Wilhelm
next prev parent reply other threads:[~2025-05-23 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 14:35 [PATCH v2 0/2] soc: qcom: QMI helpers supports for big endian Alexander Wilhelm
2025-05-22 14:35 ` [PATCH v2 1/2] soc: qcom: QMI encoding/decoding " Alexander Wilhelm
2025-05-23 8:34 ` Dmitry Baryshkov
2025-05-22 14:35 ` [PATCH v2 2/2] soc: qcom: fix endianness for QMI header Alexander Wilhelm
2025-05-22 19:09 ` Dmitry Baryshkov
2025-05-23 5:57 ` Alexander Wilhelm [this message]
2025-05-23 8:32 ` Dmitry Baryshkov
2025-05-23 8:34 ` Dmitry Baryshkov
2025-06-17 21:31 ` [PATCH v2 0/2] soc: qcom: QMI helpers supports for big endian Bjorn Andersson
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=aDAOXo/ujOcefs04@FUE-ALEWI-WINX \
--to=alexander.wilhelm@westermo.com \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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