From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Alexander Wilhelm <alexander.wilhelm@westermo.com>,
Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org
Subject: Re: ath12k: big endian bringup
Date: Wed, 4 Jun 2025 10:30:40 -0700 [thread overview]
Message-ID: <ae1215c7-5ea6-447c-8c07-5667e13dae89@oss.qualcomm.com> (raw)
In-Reply-To: <aD8HK4Iagc99skN5@FUE-ALEWI-WINX>
On 6/3/2025 7:31 AM, Alexander Wilhelm wrote:
> Hello devs,
>
> I need help to bring up the QCN9274 with ath12k driver on big endian PowerPC
> platform. I've already found some issues and fixed the MHI start procedure [1]
> and QMI conversion [2]. Furthermore I added some endianness fixes on 'qmi.c'
> file and could successfully transfer the firmware and boardfile to the wireless
> module. But the firmware does not start properly.
>
> I'm trying to analyze the error and don't fully understand what is happening.
> While 'ath12k_htc_connect_service' I expect a successful response from
> 'ath12k_htc_send', but the connection then is timeout. It seems that I should
> receive a message with length of 20 and at least I get one. But then the driver
> remains endless in the 'ath12k_ce_recv_process_cb' and I always get a message of
> length 0 from the 'ath12k_hal_ce_dst_status_get_length' until RCU stall happens.
>
> More interesting is the 'CE_ATTR_BYTE_SWAP_DATA' from ath11k, that is still used
> in ath12k code, but HAL structures now are swapped in driver itself at the same
> time. Is that correct?
That does NOT sound correct.
What happens if you unconditionally keep the BYTE_SWAP flag disabled?
Note that to date the ath12k driver has not been tested internally on a big
endian host. But your message at least has folks talking about it now...
/jeff
next prev parent reply other threads:[~2025-06-04 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 14:31 ath12k: big endian bringup Alexander Wilhelm
2025-06-04 17:30 ` Jeff Johnson [this message]
2025-06-05 6:23 ` Alexander Wilhelm
2025-06-06 5:18 ` Vasanthakumar Thiagarajan
2025-06-06 7:36 ` Alexander Wilhelm
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=ae1215c7-5ea6-447c-8c07-5667e13dae89@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=alexander.wilhelm@westermo.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-wireless@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