public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Alexander Wilhelm <alexander.wilhelm@westermo.com>,
	Jeff Johnson <jjohnson@kernel.org>
Cc: ath12k@lists.infradead.org, linux-wireless@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: ath12k: REO status on PPC does not work
Date: Tue, 19 Aug 2025 14:38:38 +0800	[thread overview]
Message-ID: <d6f0b64f-1764-41cd-a7c5-fb34d034ace2@oss.qualcomm.com> (raw)
In-Reply-To: <aJ7sDOoWmf4jLpjo@FUE-ALEWI-WINX>



On 8/15/2025 4:13 PM, Alexander Wilhelm wrote:
> Hello devs,
> 
> I'm currently working on getting the 'ath12k' driver running on a big endian
> PowerPC platform and have encountered the following issue.
> 
> In the function 'ath12k_dp_rx_process_reo_status', the REO status is determined
> by inspecting memory that the hardware has previously written via DMA.
> Specifically, during the call to 'ath12k_hal_srng_access_begin', the driver
> reads the value of 'hp_addr' for the destination ring (in my case, always with
> ID 21). On the big endian platform, this value is consistently 0, which prevents
> the REO status from being updated.

This does not seem an endian issue to me, because either of them we should get a value
other than 0.

> 
> Interestingly, DMA read/write accesses work fine for other rings, just not for
> this one. What makes the REO status ring so special? I couldn’t find anything in
> the initialization routine that would explain the difference.
> 
> Could anyone give me a hint on what I should be looking for?
> 
> 
What hardware are you using? WCN7850 or QCN9274?

> Best regards
> Alexander Wilhelm
>



  parent reply	other threads:[~2025-08-19  6:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15  8:13 ath12k: REO status on PPC does not work Alexander Wilhelm
2025-08-15  9:55 ` Sebastian Gottschall
2025-08-15 10:26   ` Alexander Wilhelm
2025-08-15 10:50     ` Sebastian Gottschall
2025-08-15 12:00       ` Alexander Wilhelm
2025-08-19  6:38 ` Baochen Qiang [this message]
2025-08-19  6:59   ` Alexander Wilhelm
2025-08-19  7:26     ` Baochen Qiang
2025-08-19  8:10       ` Alexander Wilhelm
2025-08-19  9:21         ` Vasanthakumar Thiagarajan
2025-08-21  6:54           ` 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=d6f0b64f-1764-41cd-a7c5-fb34d034ace2@oss.qualcomm.com \
    --to=baochen.qiang@oss.qualcomm.com \
    --cc=alexander.wilhelm@westermo.com \
    --cc=ath12k@lists.infradead.org \
    --cc=jjohnson@kernel.org \
    --cc=linux-kernel@vger.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