From: Alexander Wilhelm <alexander.wilhelm@westermo.com>
To: Jeff Johnson <jjohnson@kernel.org>
Cc: ath12k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: ath12k: hal_reo_dest_ring on PowerPC?
Date: Mon, 14 Jul 2025 11:57:39 +0200 [thread overview]
Message-ID: <aHTUk+80g6QV1vWA@FUE-ALEWI-WINX> (raw)
Hello devs,
I'm trying to bring up the ath12k driver on big endian PPC platform. Currently
I'm stuck and need your help.
In the function _ath12k_dp_rx_process_ inside _dp_rx.c_ the _desc_va_ is
extraced as the following:
desc_va = ((u64)le32_to_cpu(desc->buf_va_hi) << 32 |
le32_to_cpu(desc->buf_va_lo));
desc_info = (struct ath12k_rx_desc_info *)((unsigned long)desc_va);
As you can see the _buf_va_hi_ and _buf_va_lo_ are swapped on big endian since
the data type is __le32. However that swap leads to kernel panic on my machine.
The entire _struct hal_reo_dest_ring_ consists only of little endian member
values and it seems to be correct. Therefore I assume the values are already set
wrong earlier, but I cannot find a place in a source code where they are set.
Can someone explain to me how and where those values are set, so I can fix the
problem?
Best regards
Alexander Wilhelm
reply other threads:[~2025-07-14 12:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aHTUk+80g6QV1vWA@FUE-ALEWI-WINX \
--to=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